Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1862445

Summary:	compliance policy creation fails for ansible deployment option on upgraded satellite.
Product:	Red Hat Satellite	Reporter:	Jameer Pathan <jpathan>
Component:	SCAP Plugin	Assignee:	Ondřej Pražák <oprazak>
Status:	CLOSED ERRATA	QA Contact:	Jameer Pathan <jpathan>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	ehelms, mhulan, oprazak
Target Milestone:	6.8.0	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_openscap-4.0.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 13:04:55 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 Jameer Pathan 2020-07-31 13:04:19 UTC

Description of problem:
compliance policy creation fails for ansible deployment option. 

Version-Release number of selected component (if applicable):
- Satellite 6.8.0 snap 10

How reproducible:
Always

Steps to Reproduce:
1. Import scap ansible roles and variables on satellite 6.7
2. Perform satellite 6.7 to 6.8 upgrade.
3. Try creating compliance policy using Ansible deployment option on upgraded 6.8 satellite.

Actual results:
Compliance policy creation for Ansible deployment option fails with "Failed to save when overriding parameters for ansible, cause: Default value is invalid" error.

Expected results:
Successfully created Compliance policy using Ansible deployment option.

Additional info:
Workaround:
go to the details of foreman_scap_client_port ansible variable:
- check override
- change parameter type from string to integer
- set default value to any random integer value
- save

Comment 1 Ondřej Pražák 2020-08-04 07:30:48 UTC

Created redmine issue https://projects.theforeman.org/issues/30557 from this bug

Comment 2 Bryan Kearney 2020-08-04 08:02:57 UTC

Upstream bug assigned to oprazak

Comment 3 Bryan Kearney 2020-08-04 08:02:59 UTC

Upstream bug assigned to oprazak

Comment 4 Bryan Kearney 2020-08-05 16:02:56 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30557 has been resolved.

Comment 5 Jameer Pathan 2020-08-25 08:26:45 UTC

Verified

Verified with:
- Satellite 6.8.0 snap 12

Test steps:
1. Import scap ansible roles and variables on satellite 6.7
2. Create policy with ansible deployment option.
3. Perform satellite 6.7 to 6.8 upgrade.
4. Try creating compliance policy using Ansible deployment option on upgraded 6.8 satellite.

Observations:
- Successfully created Compliance policy using Ansible deployment option.

Comment 8 errata-xmlrpc 2020-10-27 13:04:55 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 (Important: Satellite 6.8 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-2020:4366