Hide Forgot
Description of problem: it's not possible to create a lifecycle environment with specifying only a prior environment by its name (using --prior paramter). Hammer requires --prior-id to be set, rendering --prior parameter quite useless Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. hammer --output=csv lifecycle-environment create --prior="Library" --organization-id="1" --name="foo" Actual results: Missing arguments for 'prior_id' Could not create environment: Missing arguments for 'prior_id' Expected results: Lifecycle environment is created. Additional info: tested with snap2
Closed this by mistake.
[root@ibm-x3250m4-01 ~]# hammer -v -u admin -p changeme lifecycle-environment create --prior="Library" --organization-id="1" --name="DEV" Environment created [root@ibm-x3250m4-01 ~]# hammer -v -u admin -p changeme lifecycle-environment list --organization-id="1" ---|---------|-------- ID | NAME | PRIOR ---|---------|-------- 1 | Library | 2 | DEV | Library ---|---------|-------- [root@ibm-x3250m4-01 ~]# hammer -v -u admin -p changeme lifecycle-environment create --prior="DEV" --organization-id="1" --name="QE" Environment created [root@ibm-x3250m4-01 ~]# hammer -v -u admin -p changeme lifecycle-environment list --organization-id="1"---|---------|-------- ID | NAME | PRIOR ---|---------|-------- 3 | QE | DEV 1 | Library | 2 | DEV | Library ---|---------|-------- [root@ibm-x3250m4-01 ~]# hammer -v -u admin -p changeme lifecycle-environment create --prior="Library" --organization-id="1" --name="GA" Environment created [root@ibm-x3250m4-01 ~]# hammer -v -u admin -p changeme lifecycle-environment list --organization-id="1"---|---------|-------- ID | NAME | PRIOR ---|---------|-------- 3 | QE | DEV 1 | Library | 4 | GA | Library 2 | DEV | Library ---|---------|--------
Verified on Satellite 6.2.0 SNAP 4.0 Build.
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/RHBA-2016:1501