Created redmine issue http://projects.theforeman.org/issues/16490 from this bug

*** Bug 1380654 has been marked as a duplicate of this bug. ***

Both linked issues must be fixed. They are currently pending review. Once they are in, this will allow do commands such as

> hammer host info --id 2
> hammer hostgroup info --id 2

which will contain e.g. (similar to Puppet Proxy ID)

> OpenSCAP Proxy:         1

also creating/updating will be available

> hammer host update --id 2 --openscap-proxy-id 1
> hammer hostgroup create --name openscap --openscap-proxy-id 1

All is to be found in /apidoc after new apipie cache is generated e.g. by

> foreman-rake apipie:cache

Note for QE: this also touched WebUI, the OpenSCAP proxy field should now support inheriting like other proxy fields. The label and inline helps changed. UI part should be also tested.

Upstream bug assigned to mhulan@redhat.com

Upstream bug assigned to mhulan@redhat.com

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

Satellite 6.3.0 snap 20

FOR HOSTGROUP:

hammer hostgroup update --help
--openscap-proxy-id OPENSCAP_PROXY_ID                     ID of OpenSCAP Capsule

hammer hostgroup info --id 1
Id:                     1
'''
'''
Locations:              
    Default Location
Organizations:          
    Default Organization
Parent Id:              
OpenSCAP Proxy:         1
Content View:           RHEL 6 CV
Lifecycle Environment:  DEV
Content Source:         satellite

[root@dell-per630-fc-01 ~]# hammer hostgroup update --id 1 --openscap-proxy-id 1
Hostgroup updated
[root@dell-per630-fc-01 ~]# hammer hostgroup info --id 1
Id:                     1
'''
'''
Locations:              
    Default Location
Organizations:          
    Default Organization
Parent Id:              
OpenSCAP Proxy:         1
Content View:           RHEL 6 CV
Lifecycle Environment:  DEV
Content Source:         dell-per630-fc-01.

hammer> hostgroup create --name test --openscap-proxy-id 1
Hostgroup created
hammer> hostgroup info --id 2
Id:                     2
Name:                   test
Title:                  test
Puppet CA Proxy Id:     
Puppet Master Proxy Id: 
Puppetclasses:          

Parameters:             

Parent Id:              
OpenSCAP Proxy:         1
Content View:           
Lifecycle Environment:  
Content Source:



The new sub-command is exposed for the hostgroup
------------------------------------------------------------------------------
For HOST
According to the https://bugzilla.redhat.com/show_bug.cgi?id=1374285#c13

hammer> host info --id 13
Id:                       13
UUID:                     e72746d7-47a3-4351-b447-a12152c41dcd
Name:                     rocky-pridham.
""""
OpenSCAP Proxy:

There is the OpenScap Proxy field available via INFO command , but on trying to update this
host update --help
No --openscap-proxy-id command

host update --id 13 --openscap-proxy-id 1
Could not update the host:
  Error: Unrecognised option '--openscap-proxy-id'
  
  See: ' host update --help'

We should also be able to manipulate proxy for individual host.

Was this missed or should this be tracked under issue?

This now fails for host only, the reason is that hosts controller is required before foreman_openscap plugin is initiated. This is caused by katello https://github.com/Katello/katello/blob/7ef4d0cba21d867581bafdf875e366d874c0cefc/lib/katello/plugin.rb#L248

I suggest we change this to VERIFIED since for hostgroups it works, and opening a separate issue for hosts with the information from above. Users should be unblocked by this.

If you're going to open separate issue, please link it to http://projects.theforeman.org/issues/21382, I sent a fix upstream for it already.

Verifying this as per the comments #19 and #20

New Issue filed for host: https://bugzilla.redhat.com/show_bug.cgi?id=1505295

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, 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-2018:0336

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, 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-2018:0336