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 1738548

Summary:	Parameter --openscap-proxy-id is missing in hammer host create command.
Product:	Red Hat Satellite	Reporter:	shisingh
Component:	SCAP Plugin	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Radek Mynar <rmynar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	apatel, kgaikwad, mbacovsk, mhulan, mshira, ofedoren, oprazak, rabajaj, rmynar, vijsingh
Target Milestone:	6.8.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 12:59:02 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 shisingh 2019-08-07 12:31:51 UTC

Description of problem: 

While trying to create a host using hammer command, not able to specify openscap  capsule as the parameter --openscap-proxy-id parameter is missing in Red Hat Satellite 6.4 Server


Version-Release number of selected component (if applicable): Red Hat Satellite 6.4


How reproducible: Every time you try to create a host using hammer command.


Steps to Reproduce:
1. Login to any CLI of any Red Hat Satellite 6.4 Server

2.Execute below hammer command to list parameters:

  # hammer host create --help | grep -i openscap



Actual results: No output is provided, as no parameter is available on the Satellite Server


Expected results: It should provide us with the parameters using which we can specify the OpenSCAP capsule as mentioned below:

# hammer host create --help | grep openscap
 --openscap-proxy-id OPENSCAP_PROXY_ID   


Additional info: Reproduced the scenario on Red Hat Satellite 6.5 Server and it is working as expected.

Comment 3 Ondřej Pražák 2019-11-18 11:57:51 UTC

The option should be present in the 6.7 snaps, could QE verify?

Comment 5 Radek Mynar 2020-06-01 11:54:16 UTC

VERIFIED with 
Red Hat Satellite (build: 6.7.0) - hammer (0.19.2.1)
Red Hat Satellite (build: 6.8.0 Beta) - hammer (2.1.0)

Comment 6 Radek Mynar 2020-06-01 12:51:19 UTC

More details:
Red Hat Satellite (build: 6.7.0)[SNAP 20] - hammer (0.19.2.1)
Red Hat Satellite (build: 6.8.0 Beta)[SNAP 1] - hammer (2.1.0)

Verified using steps from initial comment:

# hammer host create --help | grep -i openscap
 --openscap-proxy-id OPENSCAP_PROXY_ID                         ID of OpenSCAP Capsule

Comment 9 errata-xmlrpc 2020-10-27 12:59:02 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