Red Hat Bugzilla – Bug 1171669
Updating host-collection using only id is failing
Last modified: 2017-02-23 15:44:37 EST
Description of problem: Updating host-collection using id is failing Version-Release number of selected component (if applicable): # rpm -q foreman foreman-1.8.0-0.develop.201412031715git5ba6c39.el7.noarch How reproducible: everytime Steps to Reproduce: 1.# hammer -v -u admin -p changeme --output csv host-collection update --id="38" --organization-id="27" --description="<caption>mVeDNOpJCjsKMwf</caption>" [ERROR 2014-12-08 05:40:53 Exception] Missing arguments for 'name' Could not update the the host collection: Missing arguments for 'name' [ERROR 2014-12-08 05:40:53 Exception] ApipieBindings::MissingArgumentsError (Missing arguments for 'name'): /usr/share/gems/gems/apipie-bindings-0.0.11/lib/apipie_bindings/action.rb:62:in `validate!' /usr/share/gems/gems/apipie-bindings-0.0.11/lib/apipie_bindings/api.rb:158:in `call' /usr/share/gems/gems/apipie-bindings-0.0.11/lib/apipie_bindings/resource.rb:14:in `call' /usr/share/gems/gems/hammer_cli-0.1.3/lib/hammer_cli/apipie/command.rb:42:in `send_request' /usr/share/gems/gems/hammer_cli_foreman-0.1.3/lib/hammer_cli_foreman/commands.rb:165:in `send_request' /usr/share/gems/gems/hammer_cli-0.1.3/lib/hammer_cli/apipie/command.rb:33:in `execute' /usr/share/gems/gems/clamp-0.6.2/lib/clamp/command.rb:68:in `run' /usr/share/gems/gems/hammer_cli-0.1.3/lib/hammer_cli/abstract.rb:22:in `run' /usr/share/gems/gems/clamp-0.6.2/lib/clamp/subcommand/execution.rb:11:in `execute' /usr/share/gems/gems/clamp-0.6.2/lib/clamp/command.rb:68:in `run' /usr/share/gems/gems/hammer_cli-0.1.3/lib/hammer_cli/abstract.rb:22:in `run' /usr/share/gems/gems/clamp-0.6.2/lib/clamp/subcommand/execution.rb:11:in `execute' /usr/share/gems/gems/clamp-0.6.2/lib/clamp/command.rb:68:in `run' /usr/share/gems/gems/hammer_cli-0.1.3/lib/hammer_cli/abstract.rb:22:in `run' /usr/share/gems/gems/clamp-0.6.2/lib/clamp/command.rb:126:in `run' /usr/share/gems/gems/hammer_cli-0.1.3/bin/hammer:108:in `<top (required)>' /usr/bin/hammer:23:in `load' /usr/bin/hammer:23:in `<main>' 2.# hammer -v -u admin -p changeme --output csv host-collection update --name="wZuvDJvLkjQpEvX" --organization-id="27" --description="<caption>mVeDNOpJCjsKMwf</caption>" Message,Id,Name Host collection updated,38,wZuvDJvLkjQpEvX 3. Actual results: host collection updation using --id fails Expected results: host collection using --id should work additional info:
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.
Created redmine issue http://projects.theforeman.org/issues/8974 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/8974 has been closed ------------- dustin tsang Applied in changeset commit:katello|7e37fb8de1470492db675b1d34b23f0ea6bfaa1c.
VERIFIED: # hammer -u admin -p changeme host-collection update --id 26 --organization-id 1 --description "<caption>mVeDNOpJCjsKMwf</caption>" Host collection updated # rpm -qa | grep foreman foreman-postgresql-1.7.2.4-1.el7sat.noarch foreman-vmware-1.7.2.4-1.el7sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.4-1.el7.noarch foreman-compute-1.7.2.4-1.el7sat.noarch ruby193-rubygem-foreman_docker-1.1.0.2-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.1-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.1-1.el7.noarch ruby193-rubygem-foreman_openscap-0.3.0-1.el7sat.noarch foreman-1.7.2.4-1.el7sat.noarch foreman-gce-1.7.2.4-1.el7sat.noarch ruby193-rubygem-foreman_abrt-0.0.5-2.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.3-1.el7sat.noarch qe-sat6-rhel7.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-selinux-1.7.2.8-1.el7sat.noarch foreman-ovirt-1.7.2.4-1.el7sat.noarch ruby193-rubygem-foreman-redhat_access-0.0.7-2.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.4-1.el7.noarch foreman-proxy-1.7.2.1-1.el7sat.noarch foreman-libvirt-1.7.2.4-1.el7sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.4-1.el7sat.noarch qe-sat6-rhel7.usersys.redhat.com-foreman-client-1.0-1.noarch qe-sat6-rhel7.usersys.redhat.com-foreman-proxy-1.0-1.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
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