Description of problem: hammer --version command fails with inappropriate error Version-Release number of selected component (if applicable): # rpm -q foreman foreman-1.7.2.3-1.el7sat.noarch How reproducible: everytime Steps to Reproduce: 1.# hammer --version hammer (0.1.4) * hammer_cli_foreman (0.1.4) Error: undefined method `version' for HammerCLIForemanBootdisk:Module 2. 3. Actual results: hammer --version fails Expected results: --version should work as expected 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.
related - similar bug #1192113 (but for another hammer module)
Created redmine issue http://projects.theforeman.org/issues/9742 from this bug
First part of the fix is ensuring hammer can cope with plugins that don't provide version info. Second part is fixing the plugins to provide versions. Opened two bugs for the latter: https://bugzilla.redhat.com/show_bug.cgi?id=1201686 https://bugzilla.redhat.com/show_bug.cgi?id=1201687
Moving to POST since upstream bug http://projects.theforeman.org/issues/9742 has been closed ------------- Anonymous Applied in changeset commit:dbbbbcdb6d6358208d3c5cc4063567ee6dcdda64.
VERIFIED : # rpm -qa | grep foreman rubygem-hammer_cli_foreman_discovery-0.0.1.3-1.el6_6sat.noarch foreman-gce-1.7.2.13-1.el6_6sat.noarch ruby193-rubygem-foreman-redhat_access-0.0.9-1.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el6_6sat.noarch foreman-compute-1.7.2.13-1.el6_6sat.noarch foreman-vmware-1.7.2.13-1.el6_6sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.8-1.el6_6sat.noarch foreman-postgresql-1.7.2.13-1.el6_6sat.noarch rubygem-hammer_cli_foreman-0.1.4.6-1.el6_6sat.noarch foreman-ovirt-1.7.2.13-1.el6_6sat.noarch ruby193-rubygem-foreman_docker-1.2.0.4-1.el6_6sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.9-1.el6_6sat.noarch foreman-debug-1.7.2.13-1.el6_6sat.noarch foreman-libvirt-1.7.2.13-1.el6_6sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.3-1.el6_6sat.noarch foreman-selinux-1.7.2.8-1.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-client-1.0-1.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch ruby193-rubygem-foreman_abrt-0.0.5-2.el6_6sat.noarch foreman-1.7.2.13-1.el6_6sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el6_6sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch foreman-proxy-1.7.2.4-1.el6_6sat.noarch # hammer --version hammer (0.1.4.6) * hammer_cli_foreman (0.1.4.6) * hammer_cli_foreman_bootdisk (0.1.2.5) * hammer_cli_foreman_discovery (0.0.1.3) * hammer_cli_gutterball (unknown version) * hammer_cli_import (0.10.6.3) * hammer_cli_katello (0.0.7.4)
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