Bug 1981619

Summary:	Backporting of module changes into ansiblerole-foreman_scap_client bundled for Satellite 6.x
Product:	Red Hat Satellite	Reporter:	Kento Yagisawa <kyagisaw>
Component:	SCAP Plugin	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Jameer Pathan <jpathan>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.9.0	CC:	bbuckingham, mhulan, oprazak, osousa, tbrisker
Target Milestone:	6.10.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ansiblerole-foreman_scap_client-0.2.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-16 14:12:34 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:

Description Kento Yagisawa 2021-07-13 01:47:50 UTC

Description of problem:

Customer is facing issue when running Ansible playbook with session recording because of script module used by foreman_scap_client.

As far as I can see, there is no updated foreman_scap_client bundled for Satellite 6.9. It is still using ansiblerole-foreman_scap_client-0.1.0-1.el7sat.noarch

So I would like to request to backport the latest changes that merged by the following PR to Sat 6.x version.
https://github.com/theforeman/ansible-foreman_scap_client/pull/25

Comment 1 Marek Hulan 2021-07-13 07:52:05 UTC

The rebase is planned for 6.10. Ondra, is it safe to rebase this into 6.9? It contains the support for OVAL but that's backwards compatible IIRC. We'd have new variables that don't make sense in Satellite 6.9 though.

Comment 2 Ondřej Pražák 2021-07-14 06:41:32 UTC

I do not see anything in 0.2.0 that would break on 6.9, it would still be good to test before we do this.

Comment 6 Jameer Pathan 2021-08-19 05:47:56 UTC

Verified:

Verified with:
- Satellite 6.10.0 snap 14
- ansiblerole-foreman_scap_client-0.2.0-1.el7sat.noarch
- tfm-rubygem-foreman_openscap-4.3.3-1.el7sat.noarch
- tfm-rubygem-smart_proxy_openscap-0.9.1-1.el7sat.noarch

Test steps:
- Check ansiblerole-foreman_scap_client package version.
- Configure Openscap on content host via ansible.

Observation:
- 0.2.0 version of ansiblerole-foreman_scap_client is installed on Satellite 6.10.0 snap 14.
- Successfully configured Openscap on Satellite content host using Ansible deployment option. 
- Openscap report generated and uploaded successfully to Satellite.

Comment 10 errata-xmlrpc 2021-11-16 14:12:34 UTC

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 (Moderate: Satellite 6.10 Release), 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-2021:4702