Description of problem: when running activation-key content-override, you must include the label of the product being overridden. However, a user can currently run content-override without passing --label. Of course, no change is made. Version-Release number of selected component (if applicable): Nightly How reproducible: always Steps to Reproduce: 1. create an activation key and add a subscription 2. run hammer -u admin -p **** activation-key content-override --id=<activation key id> --organization-id=<organization id> 3. view results Actual results: Command runs and returns "Updated content override" Expected results: An error should be returned informing the user that a product label is needed. 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/8892 from this bug
*** Bug 1187750 has been marked as a duplicate of this bug. ***
Moving to POST since upstream bug http://projects.theforeman.org/issues/8892 has been closed ------------- Christine Fouant Applied in changeset commit:katello|bc66876163e0cd5f6ccaaaf7223f990147aea9d5.
FAILEDQA : # rpm -qa | grep foreman foreman-1.7.2.8-1.el6_6sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.2-1.el6_6sat.noarch foreman-compute-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman_docker-1.2.0.2-1.el6_6sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.1-1.el6_6sat.noarch foreman-proxy-1.7.2.3-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 rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el6_6sat.noarch foreman-vmware-1.7.2.8-1.el6_6sat.noarch foreman-libvirt-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman_abrt-0.0.5-2.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch rubygem-hammer_cli_foreman-0.1.4.6-1.el6_6sat.noarch foreman-selinux-1.7.2.8-1.el6_6sat.noarch foreman-debug-1.7.2.8-1.el6_6sat.noarch foreman-gce-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman-redhat_access-0.0.8-2.el6_6sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.5-1.el6_6sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch foreman-postgresql-1.7.2.8-1.el6_6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el6_6sat.noarch foreman-ovirt-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.8-1.el6_6sat.noarch hammer -u admin -p changeme activation-key content-override --id 75 --organization 1 --content-label 'Busybox' --value 0 Could not update content override: Invalid content label: Busybox
This looks like the bug wasn't tested correctly. Moving back to ON_QA.
Verified in Satellite 6.1.0 snap 5. Version tested: RHEL 66 RHEL 7 # hammer -u admin -p **** activation-key content-override --content-label=rhel-7-server-satellite-6.0-rpms --value=0 --id=3 --organization-id=12 Updated content override
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