Bug 1477993 - hammer global-parameter delete/set on existing parameter fails
hammer global-parameter delete/set on existing parameter fails
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Hammer (Show other bugs)
x86_64 Linux
unspecified Severity low (vote)
: Unspecified
: --
Assigned To: satellite6-bugs
Katello QA List
Depends On:
  Show dependency treegraph
Reported: 2017-08-03 08:17 EDT by Göran Törnqvist
Modified: 2017-08-03 08:20 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-08-03 08:20:28 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Göran Törnqvist 2017-08-03 08:17:48 EDT
Description of problem:
When I perform a:

hammer global-parameter set --name "myparam" --value "myvalue"
hammer global-parameter delete --name "myparam"

Where myparam is an existing parameter, it fails with message:

Resource common_parameter not found by id 'myparam'

The corresponding API calls works however so I believe the error is in hammer.

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

How reproducible:

Steps to Reproduce:
1. Create new parameter (works fine):
[root@satellite ~]# hammer global-parameter set --name "mynewparameter" --value "myvalue"
Created parameter [mynewparameter] with value [myvalue].

2. Try to update the parameter:
[root@satellite ~]# hammer global-parameter set --name "mynewparameter" --value "myvalue"
Resource common_parameter not found by id 'mynewparameter'

3. Try to delete the parameter:
[root@satellite ~]# hammer global-parameter delete --name "mynewparameter"
Could not delete the global parameter []:
  Resource common_parameter not found by id 'mynewparameter'

Actual results:
Update and delete of global parameter fails.

Expected results:
The parameter can be updated with "set" and deleted with "delete" options.

Additional info:
Comment 1 Göran Törnqvist 2017-08-03 08:20:28 EDT
Incorrect permissions for the user caused the error

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