Description of problem:
Discussed with Chris before, QE team will test the latest virt-who package in sattools repo, that means the virt-who developers only need to maintain the upstream build for rhel6 or rhel7.
if a stable virt-who package is available for rhel6.x, will create the same sat package (el6sat, el7sat) in sattools repo at the same time.
if a stable virt-who package is available for rhel7.x, will create the same sat package (el6sat, el7sat) in sattools repo at the same time.
the virt-who package in Satellite-6.2.0-RHEL-7-20161219.0/compose/sattools/x86_64/os/Packages/ is virt-who-0.17-10.el7sat, not virt-who-0.18-1.el7sat
the virt-who package in Satellite-6.2.0-RHEL-6-20161213.0/compose/sattools/x86_64/os/Packages/ is virt-who-0.17-9.el6sat, not virt-who-0.18-1.el6sat
so we need someone to:
1). create virt-who-0.18-1.el7sat and virt-who-0.18-1.el6sat package according to the latest build, always make sure virt-who for rhel and sattools is the same and latest package.
2). sync these two packages in sattools repo.
do you have the permission to create the .sat package?
when you create the package for rhel6.x or rhel7.x, it's more better to create the package for satellite as well.
I do not have permission to create .sat package, I can only update the content from which the .sat package will be built. We can ask Eric if I can acquire the appropriate permissions if so desired.
Would it be possible / desirable for me to build the .sat package?
moving this to 6.2.9
Please add verifications steps for this bug to help QE verify
Verified in Satellite 6.2.9 Snap 2
I see the following two packaged available in their respective satellite tools repos.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.