Bug 895735 - [RFE] Specifying the keyname when removing custom info from a system should be required
Summary: [RFE] Specifying the keyname when removing custom info from a system should b...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Adam Price
QA Contact: Og Maciel
URL:
Whiteboard:
Depends On:
Blocks: 896096
TreeView+ depends on / blocked
 
Reported: 2013-01-15 21:46 UTC by Og Maciel
Modified: 2014-09-02 18:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
: 896096 (view as bug list)
Environment:
Last Closed: 2014-09-02 18:40:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Og Maciel 2013-01-15 21:46:25 UTC
Description of problem:

In order to delete a keyname/value pair from a system's custom information field, one must provide at least the keyname as an argument. However the cli does not make this requirement explicit which can be a bit confusing.

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

* candlepin-0.7.23-1.el6_3.noarch
* candlepin-tomcat6-0.7.23-1.el6_3.noarch
* elasticsearch-0.19.9-5.el6_3.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.2.1-1h.el6_3.noarch
* katello-cli-1.2.1-11h.el6_3.noarch
* katello-cli-common-1.2.1-11h.el6_3.noarch
* katello-common-1.2.1-12h.el6_3.noarch
* katello-configure-1.2.3-1h.el6_3.noarch
* katello-glue-candlepin-1.2.1-12h.el6_3.noarch
* katello-headpin-1.2.1-12h.el6_3.noarch
* katello-headpin-all-1.2.1-12h.el6_3.noarch
* katello-selinux-1.2.1-2h.el6_3.noarch
* thumbslug-0.0.28-1.el6_3.noarch
* thumbslug-selinux-0.0.28-1.el6_3.noarch

How reproducible:


Steps to Reproduce:
1. Create a random organization with a random set of environments
2. Register a system to this organization
3. ssh to the system and open the katello/headpin shell
4. Obtain the uuid or the name for the newly registered system
5. Check the current custom information attached to this system
6. Add a new custom information to the system:
   system add_custom_info <random name> --name <system_name> --keyname 'secret question' --value 'secret answer' (or use the system's uuid)
7. Add another custom information to the system:
   system add_custom_info <random name> --name <system_name> --keyname 'secret location' --value 'secret place' (or use the system's uuid)
8. Delete one of the custom information fields:
   system remove_custom_info <random name> --name <system_name>
  
Actual results:

Couldn't find custom info

Expected results:

Some type of notification stating that at least the keyname is required to remove a keyname/value pair.


Additional info:

Comment 1 Og Maciel 2013-01-15 21:48:28 UTC
sam> system info --org 9b8f7e32-b818-4d49-854a-7cf3abf1b3fb --name qeclient01---------------------------------------------------------------------------------------------------------------------
                         System Information For Org [ 9b8f7e32-b818-4d49-854a-7cf3abf1b3fb ]
---------------------------------------------------------------------------------------------------------------------

Name            : qeclient01
Ipv4 Address    : 127.0.0.1
Uuid            : 6dd89eb8-6250-492f-8e03-1e05536fde68
Location        : None
Registered      : 2013/01/07 14:05:04
Last updated    : 2013/01/07 14:05:04
Description:
    Initial Registration Params
Activation Keys:
    [  ]
Service Level   : 
Custom Info:
    [ asset-tag: None, secret question: secret answer ]

sam> system remove_custom_info --org 9b8f7e32-b818-4d49-854a-7cf3abf1b3fb --name qeclient01
Couldn't find custom info

Comment 3 Adam Price 2013-01-16 15:46:46 UTC
https://github.com/Katello/katello/pull/1404

Comment 4 Mike McCune 2013-08-16 18:05:04 UTC
getting rid of 6.0.0 version since that doesn't exist

Comment 5 Mike McCune 2013-09-19 18:08:48 UTC
These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM.  If this is a mistake feel free to re-open.

Comment 6 Mike McCune 2013-09-20 02:29:41 UTC
This bug was mistakenly closed during a triage process.  Moving back to MODIFIED or ON_QA depending

Comment 10 Og Maciel 2014-09-02 18:40:48 UTC
We no longer allow custom information to be associated with a content-host (aka system).


Note You need to log in before you can comment on or make changes to this bug.