Red Hat Bugzilla – Bug 1085417
CLI: A number of info command doesn't work if you pass them bad ids
Last modified: 2017-02-23 16:18:00 EST
Try these commands: hammer product info --id 885858585885 hammer system info --id 8588585858 You'll get weird results like: undefined method `readable?' for nil:NilClass or Error: 400 Bad Request I'd expect a message like: Could not find product with id 885858585885
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/6971 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/6971 has been closed ------------- dustin tsang Currently these commands seem to be having problems (excerpt from https://gist.github.com/dustint-rh/a60d05d0c62549b27dab): hammer capsule info --id 2141 protected method `resource_name' called for #<Katello::Api::V2::CapsulesController:0x0000001d229e18> hammer product info --id 2141 no resource loaded hammer repository info --id 2141 wrong number of arguments (0 for 1) ------------- dustin tsang 2 pull requests created: https://github.com/Katello/katello/pull/4543 https://github.com/Katello/hammer-cli-katello/pull/216 ------------- dustin tsang Applied in changeset commit:hammer-cli-katello|6b66fa036e7b3149db82072d0659bfa50a23e252.
VERIFIED # 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 # hammer product info --id 1668 [Foreman] Username: admin [Foreman] Password for admin: ID: 1668 Name: test_prod Label: test_prod Description: Sync State: finished Sync Plan ID: GPG: GPG Key ID: GPG Key: Organization: Default Organization Readonly: false Deletable: Content: 1) Repo Name: test_repo URL: /custom/test_prod/test_repo Content Type: docker
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