Bug 1178928

Summary:	Unable to update activation key by id
Product:	Red Hat Satellite	Reporter:	jcallaha
Component:	Hammer	Assignee:	Christine Fouant <cfouant>
Status:	CLOSED ERRATA	QA Contact:	jcallaha
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	Nightly	CC:	bbuckingham, bkearney
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/8833
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-12 05:21:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description jcallaha 2015-01-05 16:36:44 UTC

Description of problem:
A user is required to provide an activation key's name, even if they provide the activation key's id, in order to update the key.

Version-Release number of selected component (if applicable):
Nightly

How reproducible:
Always

Steps to Reproduce:
1. Create an activation key
2. Obtain the id of the key and its organization
3. Run hammer activation-key update --max-content-hosts=5 --id=<x> --organization-id=<y>

Actual results:
[root@cloud-qe-9 ~]# hammer -u admin -p **** activation-key update --max-content-hosts=5 --id=1 --organization-id=1
Could not update the activation key:
  Missing arguments for 'name'


Expected results:
[root@cloud-qe-9 ~]# hammer -u admin -p **** activation-key update --max-content-hosts=5 --id=1 --organization-id=1
Activation Key successfully updated

Comment 1 RHEL Program Management 2015-01-05 16:54:21 UTC

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.

Comment 3 Christine Fouant 2015-01-05 18:22:46 UTC

Created redmine issue http://projects.theforeman.org/issues/8833 from this bug

Comment 4 Bryan Kearney 2015-01-09 19:05:12 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/8833 has been closed
-------------
Christine Fouant
Applied in changeset commit:katello|ac237cac266b9580fcb9e52bf3348ab6af66d949.

Comment 5 jcallaha 2015-01-23 20:26:11 UTC

*** This bug is verified in upstream.  This fix should eventually land in future downstream builds ***

Version Tested:
RHEL 66 / 7

katello-server-ca-1.0-1.noarch
katello-installer-2.2.0-1.201501201412git322b29f.el7.noarch
katello-installer-base-2.2.0-1.201501201412git322b29f.el7.noarch
katello-repos-2.1.1-1.el7.noarch
katello-certs-tools-2.0.1-1.el7.noarch
rubygem-hammer_cli_katello-0.0.7-1.201501210105git793226f.git.0.2414ced.el7.noarch
katello-2.1.0-1.201411061509gitb0b8f43.el7.noarch
ruby193-rubygem-katello-2.2.0-1.201501210052gitecf9bc4.el7.noarch
pulp-katello-0.3-3.el7.noarch
katello-default-ca-1.0-1.noarch

Comment 6 Bryan Kearney 2015-08-11 13:23:30 UTC

This bug is slated to be released with Satellite 6.1.

Comment 7 errata-xmlrpc 2015-08-12 05:21:16 UTC

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