Hide Forgot
Description of problem: It is not possible to provide LIFECYCLE_ENVIRONMENT_NAME to 'hammer hostgroup create' as it complains that organization not found though organization id is provided, only LIFECYCLE_ENVIRONMENT_ID is accepted. On 6.2 it was possible to specify '--organization-id' parameter but it is not available anymore. Parameter '--lifecycle-environment-organization-id' that was used in upstream also not available. So it is not possible to use '--lifecycle-environment' at all. 1. Provide LCE name and organization id > hammer> hostgroup create --lifecycle-environment="TS3A9O" --organization-ids="47" --name="test" > Could not create the hostgroup: > Error: Could not find organization, please set one of options --organizations, --organization-ids. 2. Check LCE id > hammer> lifecycle-environment info --name="TS3A9O" --organization-id=47 > ID: 54 > Name: TS3A9O 3. Provide LCE id via --lifecycle-environment-id parameter > hammer> hostgroup create --lifecycle-environment-id=54 --organization-ids=47 --name="inCpTB" > Hostgroup created Version-Release number of selected component (if applicable): Satellite 6.3.0 Snap 3.0, Foreman 1.13.1-1 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Hostgroup is not created when providing LIFECYCLE_ENVIRONMENT_NAME. Hammer complains that --organizations or --organization-ids parameter was not provided but they was. Expected results: Hostgroup should be created with both available options (with '--lifecycle-environment' just as with --lifecycle-environment-id if organization id/name was provided) Additional info:
Created redmine issue http://projects.theforeman.org/issues/17619 from this bug
Upstream bug component is Content Management
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17619 has been resolved.
passed automation test on satellite 6.3.0 snap 3
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