Description of problem: In automation, we created a hostgroup with lifecycle environment. Hostgroup was created successfully but when we checked the info of hostgroup, we did not find the associated lifecycle environment. Same issue is with creating hostgroup with content-view. 2016-07-26 11:25:10 - robottelo.ssh - DEBUG - >>> m] LANG=en_US.UTF-8 hammer -v -u admin -p changeme --output=csv hostgroup create --lifecycle-environment="C9Hafk" --organization-id="16" --name="FheyUd" Message,Id,Name Hostgroup created,1,FheyUd 2016-07-26 11:25:15 - robottelo.ssh - DEBUG - >>> [] LANG=en_US.UTF-8 hammer -v -u admin -p changeme hostgroup info --id="1" Id: 1 Name: FheyUd Title: FheyUd Puppet CA Proxy Id: Puppet Master Proxy Id: Puppetclasses: Parameters: Organizations: xxLCT7 Parent Id: Version-Release number of selected component (if applicable): sat62 GA snap21.1 How reproducible: Steps to Reproduce: 1. create hostgroup with cv and lifecycle environment. 2. check hostgroup info 3. Actual results: Expected results: Hostgroup info should show associated cv and lifecycle-environment Additional info:
Upstream bug component is Hammer
Upstream bug component is Content Management
Moving to POST since upstream bug http://projects.theforeman.org/issues/15990 has been closed
*** Bug 1371504 has been marked as a duplicate of this bug. ***
It worked on sat 6.3.0 snap 6: hammer> hostgroup list ---|--------|--------|------------------|-------------|------ ID | NAME | TITLE | OPERATING SYSTEM | ENVIRONMENT | MODEL ---|--------|--------|------------------|-------------|------ 1 | hgroup | hgroup | | | ---|--------|--------|------------------|-------------|------ hammer> hostgroup info --id 1 Id: 1 Name: hgroup Title: hgroup Puppet CA Proxy Id: Puppet Master Proxy Id: Puppetclasses: Parameters: Organizations: Default Organization Parent Id: Content View: FooContentView Lifecycle Environment: EnvTest So I am moving this bug to VERIFIED
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