-
Notifications
You must be signed in to change notification settings - Fork 148
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
GPG check: do not raise an error when TargetUserSpaceInfo is missing
Previously, if the upgrade has been inhibited during TargetTransactionFactsCollectionPhase usually because we could not create (for whatever reason) the target userspace container, the actor checking rpm gpg keys failed with the `Could not check for valid GPG keys` error. This has confused many users as they couldn't know that this is impacted by the problem described in an inhibitor that is below this error. As it's for sure that the upgrade cannot continue when the target user space container has not been created (the TargetUserSpaceInfo msg is missing), we consider it safe to stop the gpg check here silently just with a warning msg instead of raising the error - as this check is important only in case we could actually upgrade. All other possible raised errors are presereved. jira: https://issues.redhat.com/browse/RHEL-30573 Signed-off-by: Petr Stodulka <[email protected]> Signed-off-by: Jakub Jelen <[email protected]>
- Loading branch information
Showing
2 changed files
with
15 additions
and
11 deletions.
There are no files selected for viewing
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
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