Bug 2058950

Summary:	New UI page does not provide any information of which Scap policy is applied on the client system
Product:	Red Hat Satellite	Reporter:	Jaskaran Singh Narula <janarula>
Component:	Hosts	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	NEW ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	afeferku, aruzicka, inecas
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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:

Description Jaskaran Singh Narula 2022-02-27 06:26:25 UTC

Description of problem:

The new Host page does not provide any way to figure out or troublehshoot which openscap policy is applied on the client system. 

Version-Release number of selected component (if applicable):
Satellite 7.0 Beta 

How reproducible:
100% 

Steps to Reproduce:
1. Install Satellite 7
2. Assign Scap policy to the host.  
3. Navigate to Hosts > All Hosts > Click on any Host
4. No tab or section that shows the information of which scap policy is applied on the client system.

Actual results:
No info about which openscap policy is assigned to the hosts.

Expected results:
Section or option to look for which policy is applied to the host. 

Additional info:

This was possible in the older version of the satellite where we had the option to see YMAL output on the same page.

Comment 1 Brad Buckingham 2022-02-28 14:05:17 UTC

Amir,

Is this expected behavior for 7.0?

Comment 2 Amir 2022-03-13 21:27:31 UTC

Hi Brad,
scap content is not expected for 7.0

Comment 6 Brad Buckingham 2023-03-06 11:40:19 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 8 Brad Buckingham 2023-04-06 15:56:05 UTC

Based upon further review from the engineering team, this bugzilla will not be closed at this time.