Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1876194
Summary: | rpm-ostree update fails in filesystem checkout | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Vadim Rutkovsky <vrutkovs> |
Component: | rpm-ostree | Assignee: | Jonathan Lebon <jlebon> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 32 | CC: | awilliam, dmach, dustymabe, ego.cordatus, extras-qa, feborges, igor.raits, jlebon, jmracek, jonathan, jrohel, juha.koskiniemi, kparal, lruzicka, mcermak, miabbott, mjw, ngompa13, nielsenb, packaging-team-maint, philip.wyett, pkratoch, pmatilai, pmoravco, pwhalen, rfairley, robatino, robertthomasfairley, sdodson, thiago.frmoraes, tpopela, travier, vmukhame, walters |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | AcceptedFreezeException | ||
Fixed In Version: | rpm-ostree-2020.5-1.fc33 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1838691 | Environment: | |
Last Closed: | 2020-09-21 20:48:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1838691 | ||
Bug Blocks: | 1766776 |
Description
Vadim Rutkovsky
2020-09-06 08:09:29 UTC
Workaround: ``` rpm-ostree reset ... rpm-ostree rebase fedora/33/x86_64/testing/silverblue ... reboot ``` That however has nuked my shell (zsh), so I had to create a new user to login and run the rebase If I understand it correctly, this got fixed in F33 (bug 1838691) but not in F32. So I'm removing the F33 proposed blocker. Right, this will cause issues in the f32 -> f33 rebase because f32 rpm-ostree doesn't understand the new rpmdb since it has old libsolv and old librpm, so systems with layered packages will fail to rebase. The fix for this would be to backport the libsolv patch *and* rpm 4.16 to f32 (but make the rpmdb migration still gate on upgrading to f33), but I don't see that happening (/cc Panu in case this came up already). We'll probably have to document this on the "Common F33 bugs" page and tell users with overlays to `rpm-ostree reset` first (see https://bugzilla.redhat.com/show_bug.cgi?id=1838691#c34). Yeah, unfortunately. We could also teach rpm-ostree how to do this itself with an extra reboot (or run the new base OS as a container, which is trickier; would work most of the time but introduces fun new failure modes with a particularly old kernel). Cross-linking: https://github.com/coreos/fedora-coreos-tracker/issues/609#issuecomment-688977962. Interesting to note for FCOS we could work around this relatively easily thanks to update barriers. "We could also teach rpm-ostree how to do this itself with an extra reboot" I'd really like it if we could do this, because as everyone knows, lots of people never read the docs... Hmm I'm leaning more and more towards making f33 use bdb by default for at least Silverblue and FCOS. This is fixed by https://bodhi.fedoraproject.org/updates/FEDORA-2020-0f1c4e8bae. Notice it's against f33 even though this bug is opened against f32. Once it enters the f33 repos, f33 Silverblue composes will use BDB again and rebases from f32 should work. This should probably get a freeze exception, then, because otherwise that won't go stable until after Beta release. Proposing as an FE so we can fix rebase from Silverblue 32 to 33, seems reasonable to fix that during freeze. FEDORA-2020-0f1c4e8bae has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-0f1c4e8bae FEDORA-2020-0f1c4e8bae has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-0f1c4e8bae` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-0f1c4e8bae See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. +5 votes in the ticket (https://pagure.io/fedora-qa/blocker-review/issue/65 ), setting accepted. Note it'd still be good to hear from pwhalen and/or pbrobinson to confirm this change is OK for IoT. (In reply to Adam Williamson from comment #12) > +5 votes in the ticket (https://pagure.io/fedora-qa/blocker-review/issue/65 > ), setting accepted. Note it'd still be good to hear from pwhalen and/or > pbrobinson to confirm this change is OK for IoT. No issues on IoT, +1 FEDORA-2020-0f1c4e8bae has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. Tried it today and I can't still successfully rebase to the F33 branch: 0 $ rpm-ostree rebase fedora/33/x86_64/silverblue 1 metadata, 0 content objects fetched; 592 B transferred in 3 seconds; 0 bytes content written Checking out tree 2d91e02... done Enabled rpm-md repositories: google-chrome fedora-cisco-openh264 google-chrome-beta fedora updates rpm-md repo 'google-chrome' (cached); generated: 2020-09-16T17:43:15Z rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2020-08-25T19:10:34Z rpm-md repo 'google-chrome-beta' (cached); generated: 2020-09-16T17:43:15Z rpm-md repo 'fedora' (cached); generated: 2020-09-20T10:51:30Z rpm-md repo 'updates' (cached); generated: 2018-02-20T19:18:14Z Importing rpm-md... done Resolving dependencies... done Will download: 427 packages (319,3 MB) Downloading from 'fedora'... done Importing packages... done Checking out packages... done error: Checkout filesystem-3.14-3.fc33.x86_64: opendir(local): No such file or directory I thought that the once the update gets into stable repos, then this will be resolved, but we are probably missing something else? ``` # ostree pull --commit-metadata-only fedora:fedora/33/x86_64/silverblue GPG: Verification enabled, found 1 signature: Signature made Mon 21 Sep 2020 04:05:40 AM EDT using RSA key ID 6C13026D12C944D0 Good signature from "Fedora <fedora-32-primary>" 2 metadata, 0 content objects fetched; 56 KiB transferred in 4 seconds; 0 bytes content written # ostree show fedora:fedora/33/x86_64/silverblue | grep Date: Date: 2020-09-21 08:05:26 +0000 # ``` The ostree commit needs to be regenerated. (In reply to Colin Walters from comment #16) > The ostree commit needs to be regenerated. Opened https://pagure.io/fedora-infrastructure/issue/9344 Thank you Colin! |