Description of problem: Composite CV package search does not work. Version-Release number of selected component (if applicable): Satellite 6.2.13 How reproducible: consistent Steps to Reproduce: 1. Go to Content, Packages. 2. Find the package you are looking for, and click on it. 3. Go to the Repositories tab 4. Select the Lifecycle Environment your component and composite CV's are in. 5. Select the component CV, you will see the repository the package is in. 6. Select the component CV, you will see the message "No repositories contain this package". Actual results: package found in component CV but not composite Expected results: package would be found in both Additional info: This impacts the ability to verify new packages are in appropriate CV's. This is helpful during a security patching event, such as Spectre/Meltdown.
Correction to "Steps to Reproduce:" step 6: 6. Select the composite CV, you will see the message "No repositories contain this package".
Here is the current version of satellite we are on: Satellite 6.2.13 with hotfixes: bz 1468022 bz 1473349 bz 1416542 This could be environment or hotfix related.
Created attachment 1380485 [details] working I'm unable to reproduce this in 6.2.14. Attached is a screenshot of me finding the package in the composite content view it belongs to.
I was also unable to reproduce in 6.2.12 and 6.2.13. In both cases with a standard install, the package was finding it in the Composite Content View.
So Dylan Gross can reproduce on a clone of the satellite in question. But it seems that this only happens on certain CCV's. The supposition is that something went wrong during a publish/promote operation, and republishing and promoting does not correct the issue.
I have now been able to reproduce this independent of the customer's reproduction satellite with a vanilla lab satellite. It appears the search for either "Content"->"Package"/"Errata" will only find the package/errata if the LifecycleEnvironment+ContentView in the dropdown is the most recent version. I've tried with a number of different RPMs. An example of the search flow via the WebUI: "Content" "Package" search "filename~sssd-1.11.2-68.el7_0.6.x86_64.rpm" (Select package) "Repositories" tab Choose "Lifecycle Environment" and "Content View" in dropdowns Independent reproduction on Satellite v6.2.13: 1. Lifecycle environment path: Library, Dev 2. Create content View "rhel7" and publish new and promote to Dev. 3. [Normal behaviour check] At this point, the only Content View version is 1.0 and it is in both Library and Dev LE. Search using the above method for any known package. It will have hits when either "Library" or "Dev" are selected in the dropdown - and "rhel7" is selected for the Content View. 4. Publish a new version of the "rhel7" Content View. 5. [Behaviour check] Now, Version 2.0 is in the "Library" LE, and Version 1.0 is still in "Dev" LE. Doing the same searches will return a hit for the "Library"+"rhel7" because it is the most recent Content View Version, but nothing will be found for "Dev"+"rhel7" because it is n-1 from the most recent.
Connecting redmine issue http://projects.theforeman.org/issues/23141 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23141 has been resolved.
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. https://access.redhat.com/errata/RHSA-2018:2927