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.

Description of problem:
The API for hsotgroups allows you to set ContentView and LifecycleEnvironment. But the similair hosts API does not have those fields. This is not inituive and confusing for end-users

PUT /api/hostgroups/:id 
...
hostgroup[content_view_id]
optional , nil allowed 	
Value: Must be a number.
hostgroup[lifecycle_environment_id]
optional , nil allowed 	
Value: Must be a number. 

PUT /api/hosts/:id
Update a host does not have these fields


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Set ContentView and LifecycleEnvironment using API
2. Set ContentView and LifecycleEnvironment using Hammer
3.

Actual results:
Not possible, fields are not supported

Expected results:
Consistent API for hostgroups and hosts to set ContentView and Lifecycle Environment

Additional info:

Per 6.3 planning, moving out non acked bugs to the backlog

This is already fixed in 6.2.7, hammer commands for both host and hostgroup have the following flags:  

--content-view
--content-view-id
--lifecycle-environment
--lifecycle-environment-id

Could QE verify?

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