-
Bug
-
Resolution: Done-Errata
-
Normal
-
6.16.0
-
Platform
-
False
-
foreman_maintain-1.7.3
-
None
-
None
-
None
-
None
-
Yes
Description of problem:
satellite-maintain update run after self-upgrade uses inappropriate Y+1 update scenario
How reproducible:
determinictic
Is this issue a regression from an earlier version:
yes
Steps to Reproduce:
1. Plan and prepare for an upgrade by running self-upgrade
# satellite-maintain self-upgrade
2. Change your mind and try to yet update on current satellite version (before continuning in upgrade)
# satellite-maintain update run
>>> applying Y+1 update scenario on Y satellite version
Actual behavior:
[Describe the issue in detail, including what is happening and where]
inappropriate Y+1 update scenario is applied
Expected behavior:
[Describe what should be happening instead]
update prevents to apply Y+1 scenario
Business Impact / Additional info:
- links to
-
RHBA-2024:140284 Important: Satellite 6.16.0 release
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Critical: Satellite 6.16.0 release), and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2024:8906