Hide Forgot
Description of problem: Even on using valid name/id parameters, hammer organization sub-commands: add_environment, add_domain, add_subnet, add_user and more. Also hammer architecture add_operatingsystem always fail. Version-Release number of selected component (if applicable): rubygem-hammer_cli_foreman-0.0.9-2.el6sat.noarch rubygem-hammer_cli-0.0.8-2.el6sat.noarch rubygem-foreman_api-0.1.7-3.el6sat.noarch katello-foreman-all-1.4.6-55.el6sat.noarch artemis.usersys.redhat.com-foreman-client-1.0-1.noarch foreman-postgresql-1.3.0-24.el6sat.noarch ruby193-rubygem-katello-foreman-engine-0.0.12-4.el6sat.noarch artemis.usersys.redhat.com-foreman-proxy-1.0-1.noarch rubygem-hammer_cli_foreman-0.0.9-2.el6sat.noarch foreman-1.3.0-24.el6sat.noarch ruby193-rubygem-foreman-katello-engine-0.0.17-7.el6sat.noarch katello-configure-foreman-1.4.7-7.el6sat.noarch ruby193-rubygem-foreman_api-0.1.7-2.el6sat.noarch foreman-proxy-1.3.0-3.el6sat.noarch How reproducible: always Steps to Reproduce: 1. organization create --name org1 2. environment create --name envOne 3. organization add_environment --name org1 --environment-id 3 4. organization add_environment --name org1 --environment envOne Actual results: Error: resource or action not defined Expected results: It should be executed successfully
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Should be fixed in: hammer_cli 0.0.9 hammer_cli_foreman 0.0.10 foreman_api 0.1.8
qA_ack+ to this.
VERIFIED # hammer organization add-environment --name org1 --environment envOne
This was delivered with 6.0.3, which is the Satellite 6 Beta.