Description of problem: Manifest can only be seen or managed by the user who imported that. Other than that user no other user even the admin user can not see or manage the manifest. Version-Release number of selected component (if applicable): satellite 6.4 How reproducible: 100% Steps to Reproduce: 1. Create a user and give admin access to that user. 2. Import manifest with that user. 3. Now logout and login with admin or another user who as admin access. And go to below path manifest can not be seen. Content >> Subscriptions >> Manage Manifest >> USMA ---> This will show "No Manifest Uploaded" Actual results: Other user can not see the manifest but the user who uploaded. Expected results: Other user should see and manage the manifest if they have admin access. Additional info:
Created redmine issue https://projects.theforeman.org/issues/25957 from this bug
Upstream bug assigned to jomitsch
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25957 has been resolved.
This bug was cloned and is still going to be included in the 6.4.3 release. It no longer has the sat-6.4.z+ flag and 6.4.3 Target Milestone Set which are now on the 6.4.z cloned bug. Please see the Clones field to track the progress of this bug in the 6.4.3 release.
Verified in Satellite 6.5.0 Snap 19 I followed both the initial reproducer steps and the ones outlined in #9. both paths worked without issue.
For 6.4.3: This bugfix is not able to be backported to 6.4.z and will be resolved in 6.5 which is nearing completion. We closed out the 6.4.3 bug and will continue to track this bug through completion in 6.5 GA. If anyone feels we need to extend extra effort to rework a backport of this, feel free to re-open the 6.4.3 clone https://bugzilla.redhat.com/1684704 with a justification and we will re-consider.
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-2019:1222