Refresh metadata cache after failed package installation #3348
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bajertom
requested review from
psss,
lukaszachy,
happz,
thrix and
janhavlin
as code owners
happz
reviewed
Nov 8, 2024
happz
reviewed
Nov 8, 2024
happz
reviewed
Nov 8, 2024
happz
reviewed
Nov 8, 2024
bajertom
force-pushed
the
tbajer-dnf-cache-error
branch
from
e6dbd1a
to
c736cd9
Compare
bajertom
force-pushed
the
tbajer-dnf-cache-error
branch
from
c736cd9
to
793ac8a
Compare
happz
added
area | package managers
happz
reviewed
Nov 19, 2024
tmt/steps/prepare/install.py
Outdated
| except Exception: | ||
| # Refresh cache in case of recent but not updated change do repodata | ||
| self.guest.package_manager.refresh_metadata() | ||
| self._install() |
There was a problem hiding this comment.
I wonder whether should capture the first exception as well - this way, the original one is lost, with all its data. How about something like this?
try:
self._install()
except Exception as exc1:
# We do not have any special handling for exceptions raised by the following code.
# Wrapping them with try/except gives us a chance to attach the original exception
# to whatever the code may raise, and therefore preserve the information attached
# to the original exception.
try:
# Refresh cache in case of recent but not updated change do repodata
self.guest.package_manager.refresh_metadata()
self._install()
except Exception as exc2:
raise exc2 from ex1There was a problem hiding this comment.
You're right, that seems like an unnecessary loss of data - better to catch them both. I used your code, if that's alright:)
|
/packit test |
| @@ -100,6 +100,12 @@ def _extra_options( | |||
|
|
|||
| return extra_options | |||
|
|
|||
| def refresh_metadata(self) -> CommandOutput: | |||
| script = ShellScript( | |||
| f'{self.command.to_script()} update ') | |||
There was a problem hiding this comment.
I don't think there is a command for this in rpm-ostree, you can use dnf update, but rpm-ostree update does not exist
actually you can do rpm-ostree upgrade --check
There was a problem hiding this comment.
I just checked on Fedora Silverblue and it does exist:
tom@fedora:~$ rpm -q rpm-ostree
rpm-ostree-2024.8-1.fc41.x86_64
tom@fedora:~$ rpm-ostree update
Receiving metadata objects: 1611/(estimating) 7.2 MB/s 447.6 MB 1614 metadata, 6089 content objects fetched; 446119 KiB transferred in 65 seconds; 883.1 MB content written
Receiving metadata objects: 1611/(estimating) 7.2 MB/s 447.6 MB... done
Staging deployment... done
However it made changes to the system:
Upgraded:
alsa-lib 1.2.12-2.fc41 -> 1.2.13-3.fc41
alsa-sof-firmware 2024.09-1.fc41 -> 2024.09.1-1.fc41
....
vim-data 2:9.1.825-1.fc41 -> 2:9.1.866-1.fc41
vim-minimal 2:9.1.825-1.fc41 -> 2:9.1.866-1.fc41
Removed:
perl-Mozilla-CA-20240730-1.fc41.noarch
Added:
opensc-libs-0.26.0-1.fc41.x86_64
Run "systemctl reboot" to start a reboot
So you're right, rpm-ostree upgrade --check is the way to go.
$ rpm-ostree upgrade --check
1 metadata, 0 content objects fetched; 592 B transferred in 1 seconds; 0 bytes content written
Note: --check and --preview may be unreliable. See https://github.com/coreos/rpm-ostree/issues/1579
AvailableUpdate:
Version: 41.20241121.0 (2024-11-21T03:10:35Z)
Commit: dc7f3ffdfe61b3ff6df6e0f0a69c16a8a783851c1e07cc6d37a25bbb23aae4a7
GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1
Diff: 327 upgraded, 10 removed, 1 added
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #3277
When testing I found out that there is different behavior in dnf5 compared to dnf4, where a mere
dnf makecachewould be enough, but dnf5 needs the --refresh option as well (ordnf clean metadataordnf clean expire-cache), see https://bugzilla.redhat.com/show_bug.cgi?id=2324177Not sure about the Exception being too generic. Should I create a new one, something like InstallationError? And notify the user through logger as to why
metadata --refreshis happening?Pull Request Checklist