Verified on 6.14.3 - 1
Steps to Verify:
1. Setup the system as mentioned above in the reproducer:
- Create a folder containing 5 different versions of the sos rpm
- Create the reproducer script
2. Follow the steps mentioned above:
- Run the reproducer script
- Clean out the created artifacts
- Run it again, with the versions swapped
Expected Results:
The versions have the expected content count, where each version correctly increments up one package in the x.1 version, instead of copying either 1.0 or 2.0s packages.
Actual Results:
The versions have the expected content count, where each version correctly increments up one package in the x.1 version, instead of copying either 1.0 or 2.0s packages.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: Satellite 6.14.3 Async Security Update), 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:1536
Verified on 6.14.3 - 1 Steps to Verify: 1. Setup the system as mentioned above in the reproducer: - Create a folder containing 5 different versions of the sos rpm - Create the reproducer script 2. Follow the steps mentioned above: - Run the reproducer script - Clean out the created artifacts - Run it again, with the versions swapped Expected Results: The versions have the expected content count, where each version correctly increments up one package in the x.1 version, instead of copying either 1.0 or 2.0s packages. Actual Results: The versions have the expected content count, where each version correctly increments up one package in the x.1 version, instead of copying either 1.0 or 2.0s packages.