Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "Move fuse-overlayfs to suggests" for Fedora 40 and older #2203

Conversation

debarshiray
Copy link
Member

@debarshiray debarshiray commented Oct 16, 2024

Fedora completely ignores Suggests by default [1]. So, listing anything as Suggests is as good as not mentioning it at all, unless it's intended for tools and users who specifically respect it.

Downgrading the dependency on fuse-overlayfs to Suggests can make it go missing from the user's system, and break old Toolbx containers [2].

This is a problem because when Fedora 40 was released, it included containers-common-0.58.0-2.fc40 [3,4], which still had:

  Recommends: fuse-overlayfs
  Requires: (fuse-overlayfs if fedora-release-identity-server)

The change to Suggests in Fedora commit 447945e59a01cb67 ("Move fuse-overlayfs to suggests") was made after that.

Such breaking changes are not meant for stable Fedora releases to avoid surprising users, and are best done in the next upcoming version [5]. This is particularly true for atomic Fedora variants like Silverblue, where the fuse-overlayfs RPM fell off the operating system image and had to be reinstated [6]. It could also happen to those using other Fedora variants, if, for example, they were trying to use a Kickstart for installation.

This reverts Fedora commit 447945e59a01cb6715ed2a21877d45bf0b91ef67 for Fedora 40 and older releases.

[1] https://docs.fedoraproject.org/en-US/packaging-guidelines/WeakDependencies/

[2] https://discussion.fedoraproject.org/t/rpm-ostree-update-breaks-toolbox-fedora-40

[3] See the f40 tag against containers-common-0.58.0-2.fc40:
https://koji.fedoraproject.org/koji/buildinfo?buildID=2423622

[4] The update with containers-common-0.58.0-2.fc40 was marked as stable
before Final Freeze started:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-a267e93f8c
https://fedorapeople.org/groups/schedule/f-40/f-40-key-tasks.html

[5] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/

[6] workstation-ostree-config commit c7f72d2cd5eea6b1
https://pagure.io/workstation-ostree-config/c/c7f72d2cd5eea6b1
https://pagure.io/workstation-ostree-config/pull-request/526

Fedora completely ignores Suggests by default [1].  So, listing anything
as Suggests is as good as not mentioning it at all, unless it's intended
for tools and users who specifically respect it.

Downgrading the dependency on fuse-overlayfs to Suggests can make it go
missing from the user's system, and break old Toolbx containers [2].

This is a problem because when Fedora 40 was released, it included
containers-common-0.58.0-2.fc40 [3,4], which still had:
  Recommends: fuse-overlayfs
  Requires: (fuse-overlayfs if fedora-release-identity-server)

The change to Suggests in Fedora commit 447945e59a01cb67 ("Move
fuse-overlayfs to suggests") was made after that.

Such breaking changes are not meant for stable Fedora releases to avoid
surprising users, and are best done in the next upcoming version [5].
This is particularly true for atomic Fedora variants like Silverblue,
where the fuse-overlayfs RPM fell off the operating system image and had
to be reinstated [6].  It could also happen to those using other Fedora
variants, if, for example, they were trying to use a Kickstart for
installation.

This reverts Fedora commit 447945e59a01cb6715ed2a21877d45bf0b91ef67 for
Fedora 40 and older releases.

[1] https://docs.fedoraproject.org/en-US/packaging-guidelines/WeakDependencies/

[2] https://discussion.fedoraproject.org/t/rpm-ostree-update-breaks-toolbox-fedora-40

[3] See the f40 tag against containers-common-0.58.0-2.fc40:
    https://koji.fedoraproject.org/koji/buildinfo?buildID=2423622

[4] The update with containers-common-0.58.0-2.fc40 was marked as stable
    before Final Freeze started:
    https://bodhi.fedoraproject.org/updates/FEDORA-2024-a267e93f8c
    https://fedorapeople.org/groups/schedule/f-40/f-40-key-tasks.html

[5] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/

[6] workstation-ostree-config commit c7f72d2cd5eea6b1
    https://pagure.io/workstation-ostree-config/c/c7f72d2cd5eea6b1
    https://pagure.io/workstation-ostree-config/pull-request/526

Signed-off-by: Debarshi Ray <[email protected]>
@debarshiray
Copy link
Member Author

debarshiray commented Oct 16, 2024

Copy link

Ephemeral COPR build failed. @containers/packit-build please check.

@debarshiray
Copy link
Member Author

Ephemeral COPR build failed. @containers/packit-build please check.

DNF is erroring out with:

Errors during downloading metadata for repository 'baseos':
  - Downloading successful, but checksum doesn't match. Calculated: dfa5ffd57355e78da61343ee795464b49b0a3e2b41a4af74aa22160bf548a80601422eda53232dab277d7aabc097dffd04037d9173a3e96e214d0063dd5fa79e(sha512)  Expected: f3765f12125ff6f09532cd5e74a0ab0bf0b275aa28794c1171b11ed247ed46fe60a7869d2ddc4658e31ac155632b4def908fd473050e6f68c32322212b921f62(sha512) 
Error: Failed to download metadata for repo 'baseos': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

@lsm5
Copy link
Member

lsm5 commented Oct 16, 2024

Ephemeral COPR build failed. @containers/packit-build please check.

DNF is erroring out with:

Errors during downloading metadata for repository 'baseos':
  - Downloading successful, but checksum doesn't match. Calculated: dfa5ffd57355e78da61343ee795464b49b0a3e2b41a4af74aa22160bf548a80601422eda53232dab277d7aabc097dffd04037d9173a3e96e214d0063dd5fa79e(sha512)  Expected: f3765f12125ff6f09532cd5e74a0ab0bf0b275aa28794c1171b11ed247ed46fe60a7869d2ddc4658e31ac155632b4def908fd473050e6f68c32322212b921f62(sha512) 
Error: Failed to download metadata for repo 'baseos': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

it's been fixed on centos, but mirror propagation may take a while. We can ignore that if need be.

Copy link
Member

@lsm5 lsm5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. This can be gotten rid of after Fedora 40 goes EOL.

@lsm5
Copy link
Member

lsm5 commented Oct 16, 2024

/packit rebuild-failed

@lsm5
Copy link
Member

lsm5 commented Oct 16, 2024

/lgtm
/hold

@debarshiray
Copy link
Member Author

Thanks for the review!

Ephemeral COPR build failed. @containers/packit-build please check.

DNF is erroring out with:

Errors during downloading metadata for repository 'baseos':
  - Downloading successful, but checksum doesn't match. Calculated: dfa5ffd57355e78da61343ee795464b49b0a3e2b41a4af74aa22160bf548a80601422eda53232dab277d7aabc097dffd04037d9173a3e96e214d0063dd5fa79e(sha512)  Expected: f3765f12125ff6f09532cd5e74a0ab0bf0b275aa28794c1171b11ed247ed46fe60a7869d2ddc4658e31ac155632b4def908fd473050e6f68c32322212b921f62(sha512) 
Error: Failed to download metadata for repo 'baseos': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

it's been fixed on centos, but mirror propagation may take a while. We can ignore that if need be.

What was the problem? I am just curious.

@lsm5
Copy link
Member

lsm5 commented Oct 16, 2024

Thanks for the review!

Ephemeral COPR build failed. @containers/packit-build please check.

DNF is erroring out with:

Errors during downloading metadata for repository 'baseos':
  - Downloading successful, but checksum doesn't match. Calculated: dfa5ffd57355e78da61343ee795464b49b0a3e2b41a4af74aa22160bf548a80601422eda53232dab277d7aabc097dffd04037d9173a3e96e214d0063dd5fa79e(sha512)  Expected: f3765f12125ff6f09532cd5e74a0ab0bf0b275aa28794c1171b11ed247ed46fe60a7869d2ddc4658e31ac155632b4def908fd473050e6f68c32322212b921f62(sha512) 
Error: Failed to download metadata for repo 'baseos': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

it's been fixed on centos, but mirror propagation may take a while. We can ignore that if need be.

What was the problem? I am just curious.

Looks like some metadata info went bad and got synced to all mirrors.

@lsm5
Copy link
Member

lsm5 commented Oct 16, 2024

/hold cancel

@Luap99 could you please slash-approve this?

Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Copy link
Contributor

openshift-ci bot commented Oct 16, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: debarshiray, lsm5, Luap99

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 8577f22 into containers:main Oct 16, 2024
9 of 16 checks passed
@debarshiray debarshiray deleted the wip/rishi/revert-fedora-f40-447945e59a01c branch October 16, 2024 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants