Red Hat Bugzilla – Bug 1256494
Cannot view content host errata with view_content_host permission
Last modified: 2016-07-27 05:18:04 EDT
Currently there is no permission that will give you access to view content host errata, you must be an administrator. [walden@wraines-sandbox katello ((7e2c153...))]$ grep -r "katello/api/v2/system_errata" . ./lib/katello/permissions/content_host_permissions.rb: 'katello/api/v2/system_errata' => [:show], ./lib/katello/permissions/content_host_permissions.rb: 'katello/api/v2/system_errata' => [:apply], We need to add a permission for system errata index. h3. Steps to Reproduce # Create a non-admin user # Give them the view content hosts permission # Login as that user # Go to the content host page # Note that you cannot view errara
Created from redmine issue http://projects.theforeman.org/issues/11470
Upstream bug assigned to walden@redhat.com
PR: https://github.com/Katello/katello/pull/5438
Moving to POST since upstream bug http://projects.theforeman.org/issues/11470 has been closed ------------- Walden Raines Applied in changeset commit:katello|b8caed331164398340f5e8974aea39b7930efedd.
*** This bug is verified in upstream. This fix should eventually land in future downstream builds *** Version Tested: # rpm -qa | grep foreman foreman-proxy-1.11.0-0.develop.201510201341git00875b3.el7.noarch foreman-selinux-1.11.0-0.develop.201510071426git6234447.el7.noarch tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-3.el7.noarch tfm-rubygem-foreman_docker-1.4.1-2.fm1_10.el7.noarch foreman-libvirt-1.11.0-0.develop.201510201422git6eb234a.el7.noarch foreman-compute-1.11.0-0.develop.201510201422git6eb234a.el7.noarch foreman-release-scl-1-1.el7.x86_64 foreman-gce-1.11.0-0.develop.201510201422git6eb234a.el7.noarch foreman-debug-1.11.0-0.develop.201510201422git6eb234a.el7.noarch tfm-rubygem-foreman_gutterball-0.0.1-3.el7.noarch hp-sl2x170zg6-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch tfm-rubygem-foreman_discovery-4.1.1-1.fm1_11.el7.noarch foreman-vmware-1.11.0-0.develop.201510201422git6eb234a.el7.noarch tfm-rubygem-foreman_hooks-0.3.9-1.el7.noarch tfm-rubygem-foreman-tasks-0.7.6-1.fm1_10.el7.noarch tfm-rubygem-hammer_cli_foreman_tasks-0.0.8-1.el7.noarch tfm-rubygem-foreman_bootdisk-6.0.0-2.fm1_10.el7.noarch hp-sl2x170zg6-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch hp-sl2x170zg6-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-ovirt-1.11.0-0.develop.201510201422git6eb234a.el7.noarch foreman-1.11.0-0.develop.201510201422git6eb234a.el7.noarch tfm-rubygem-hammer_cli_foreman_docker-0.0.3-4.el7.noarch foreman-release-1.11.0-0.develop.201510201422git6eb234a.el7.noarch foreman-postgresql-1.11.0-0.develop.201510201422git6eb234a.el7.noarch tfm-rubygem-hammer_cli_foreman-0.4.0-1.201510201150gitab068d9.el7.noarch steps: # Create a non-admin user # Give them the view content hosts permission # Login as that user # Go to the content host page # Note that you cannot view errata
*** Bug 1338675 has been marked as a duplicate of this bug. ***
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/RHBA-2016:1501