Bug 2214290
Summary: | Assigning scap policy to a user with only view-hosts permission leads to rendering of page in loop | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | addubey |
Component: | SCAP Plugin | Assignee: | Leos Stejskal <lstejska> |
Status: | CLOSED ERRATA | QA Contact: | addubey |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.14.0 | CC: | ahumbe, lstejska, mhulan, pcreech, rlavi, shwsingh, zhunting |
Target Milestone: | 6.14.0 | Keywords: | Triaged, UserExperience |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | rubygems-foreman_openscap-7.0.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-11-08 14:19:49 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Is this a regression from Satellite 6.13 (or earlier)? Is there a stack trace from logs that can be attached? Is the fix here both in openscap and foreman_puppet? Is it safe to pull foreman_puppet 7.0.0 into foreman 3.7.0? Hi, the fix is only in the foreman_openscap-7.0.0, which should be safe to pull to 3.7.0 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 (Important: Satellite 6.14 security and bug fix 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-2023:6818 |
Created attachment 1970429 [details] page_view Description of problem: Assigning scap policy to a user with onyl view-hosts permission leads to the rendering of a page in loop Version-Release number of selected component (if applicable): 6.14.0 snap -3 How reproducible: Always Steps to Reproduce: 1. Have a user with only view-hosts permission 2. Navigate Hosrt- > All hosts -> select host -> click on Select Action button 3. Click on the assign policy button the page keeps rendering. Actual results: The page is stuck (attached ss) Expected results: Should exhibit a correct behavior Additional info: We should also see at the very first that the host with such permissions should be able to initiate an action by clicking on the select action button or not.