Red Hat Bugzilla – Bug 1265595
API and Hammer hostgroup and host inconsistent for setting ContentView and LifecycleEnvironment
Last modified: 2018-02-21 11:51:07 EST
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