Bug 1862445 - compliance policy creation fails for ansible deployment option on upgraded satellite.
Summary: compliance policy creation fails for ansible deployment option on upgraded sa...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.8.0
Assignee: Ondřej Pražák
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-31 13:04 UTC by Jameer Pathan
Modified: 2020-10-27 13:05 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-foreman_openscap-4.0.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:04:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 30557 0 Normal Closed Compliance policy creation fails for ansible deployment option 2020-10-28 17:45:40 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:05:09 UTC

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


Note You need to log in before you can comment on or make changes to this bug.