Red Hat Bugzilla – Bug 883170
[RFE] Allow --label when creating environments from the CLI
Last modified: 2017-02-23 16:20:27 EST
Description of problem: We don't seem to expose the label attribute for environments from the cli. Could we add that to the allowed attributes when creating environments? Version-Release number of selected component (if applicable): * candlepin-0.7.19-1.el6_3.noarch * candlepin-tomcat6-0.7.19-1.el6_3.noarch * elasticsearch-0.18.4-11.el6.noarch * katello-candlepin-cert-key-pair-1.0-1.noarch * katello-certs-tools-1.2.1-1h.el6_3.noarch * katello-cli-1.2.4-3h.el6_3.noarch * katello-cli-common-1.2.4-3h.el6_3.noarch * katello-common-1.2.6-3h.el6_3.noarch * katello-configure-1.2.3-1h.el6_3.noarch * katello-glue-candlepin-1.2.6-3h.el6_3.noarch * katello-headpin-1.2.6-3h.el6_3.noarch * katello-headpin-all-1.2.6-3h.el6_3.noarch * katello-selinux-1.2.1-1h.el6_3.noarch * thumbslug-0.0.27-1.el6_3.noarch * thumbslug-selinux-0.0.27-1.el6_3.noarch How reproducible: Steps to Reproduce: 1. headpin -u <username> -p <password> org create --name FOO 2. headpin -u <username> -p <password> environment create --org FOO --name BAR --prior Library 3. Actual results: Expected results: I should be able to specify what the label should be for an environment: 1. headpin -u <username> -p <password> org create --name FOO 2. headpin -u <username> -p <password> environment create --org FOO --name BAR --label BAZ --prior Library Additional info:
Created redmine issue http://projects.theforeman.org/issues/7422 from this bug
https://github.com/Katello/katello/pull/4665
Moving to POST since upstream bug http://projects.theforeman.org/issues/7422 has been closed ------------- Anonymous Applied in changeset commit:katello|9dae751e02c771d7cf5bdefafdcbeaf91d092de7.
VERIFIED : *** This bug is verified in upstream. This fix should eventually land in future downstream builds *** # rpm -qa | grep foreman foreman-gce-1.7.0-0.develop.201410081938git1cf31c6.el7.noarch ruby193-rubygem-foreman_discovery-1.4.0-0.1.rc4.el7.noarch hp-bl420cgen8-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-compute-1.7.0-0.develop.201410081938git1cf31c6.el7.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410git163c264.git.0.988ca80.el7.noarch foreman-release-1.7.0-0.develop.201410071158git54141ab.el7.noarch foreman-proxy-1.7.0-0.develop.201410081229git52f0bac.el7.noarch hp-bl420cgen8-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch foreman-ovirt-1.7.0-0.develop.201410081938git1cf31c6.el7.noarch ruby193-rubygem-foreman-tasks-0.6.9-1.el7.noarch foreman-selinux-1.7.0-0.develop.201409301113git2f345de.el7.noarch foreman-postgresql-1.7.0-0.develop.201410081938git1cf31c6.el7.noarch foreman-vmware-1.7.0-0.develop.201410081938git1cf31c6.el7.noarch ruby193-rubygem-foreman_bootdisk-4.0.0-1.el7.noarch foreman-1.7.0-0.develop.201410081938git1cf31c6.el7.noarch foreman-libvirt-1.7.0-0.develop.201410081938git1cf31c6.el7.noarch rubygem-hammer_cli_foreman-0.1.3-1.201409191432gitc38f9c8.el7.noarch # hammer -u admin -p changeme lifecycle-environment create --organization testorg --label DEV --name DEV --prior Library Environment created
This bug is slated to be released with Satellite 6.1.
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-2015:1592