Bug 1265595 - API and Hammer hostgroup and host inconsistent for setting ContentView and LifecycleEnvironment
Summary: API and Hammer hostgroup and host inconsistent for setting ContentView and Li...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: API
Version: 6.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks: 1122832
TreeView+ depends on / blocked
 
Reported: 2015-09-23 10:21 UTC by Peter Vreman
Modified: 2019-09-26 16:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:51:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Peter Vreman 2015-09-23 10:21:11 UTC
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:

Comment 2 Bryan Kearney 2016-07-08 20:47:59 UTC
Per 6.3 planning, moving out non acked bugs to the backlog

Comment 4 Ondřej Pražák 2017-01-18 15:49:58 UTC
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?

Comment 6 Satellite Program 2018-02-21 16:51:07 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, 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


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