Red Hat Bugzilla – Bug 1324884
hammer activationkey product-content command failed
Last modified: 2016-07-27 05:31:07 EDT
Created attachment 1144746 [details] production.log Description of problem: hammer activationkey product-content command failed Version-Release number of selected component (if applicable): satellite-6.2.0-6.2.beta.el7sat.noarch How reproducible: Always Steps to Reproduce: hammer> activation-key product-content --id=1 undefined method `map' for nil:NilClass Actual results: error as shown above Expected results: No error and product contents listed Additional info:
This is a regression and this seems to have broken in the recent builds (It worked fine 2 weeks back - https://bugzilla.redhat.com/show_bug.cgi?id=1250610#c7)
It appears that this error may only occur, if the activation key does not have any subscriptions attached to it.
Created redmine issue http://projects.theforeman.org/issues/14532 from this bug
Upstream bug component is Content Management
Upstream Katello PR: https://github.com/Katello/katello/pull/5945
Moving to POST since upstream bug http://projects.theforeman.org/issues/14532 has been closed ------------- Brad Buckingham Applied in changeset commit:katello|825eb8cb06d94ed6bf3f629dc62bcd3415703e74.
Verified in satellite-6.2.0-8.0.beta.el7sat.noarch # hammer -u admin -p changeme activation-key product-content --id=1 --------------|-----------------------------------------------|------|-----|---------|----------------------------------------------|--------- ID | NAME | TYPE | URL | GPG KEY | LABEL | ENABLED? --------------|-----------------------------------------------|------|-----|---------|----------------------------------------------|--------- 1460641048864 | sat6toolsrepo | | | | Default_Organization_sat6tools_sat6toolsrepo | default 2455 | Red Hat Enterprise Linux 7 Server (Kickstart) | | | | rhel-7-server-kickstart | default 2456 | Red Hat Enterprise Linux 7 Server (RPMs) | | | | rhel-7-server-rpms | default --------------|-----------------------------------------------|------|-----|---------|----------------------------------------------|---------
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/RHBA-2016:1501