Bug #5555
closed
hammer: unable to associate entities to orgs via cli
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1089635
Description of problem:
Unable to associate various entities to orgs via cli.
No association actually happens when trying the below example commands via hammer cli
1) hammer organization add-smart-proxy --name "ACME_Corporation" --smart-proxy "<proxy-hostname>
3)hammer organization add-user --id 1 --user-id 4
The user has been associated
Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140404.0/
How reproducible:
Try associating entites to org via CLI.
Trying to check the association via web-UI shows that the association was not successful.
Steps to Reproduce:
1.
2.
3.
Actual results:
Association of entities is not successful
Expected results:
Association of entities needs to be successful
Additional info:
Cannot check the association of various entities via CLI itself due to the bug
https://bugzilla.redhat.com/show_bug.cgi?id=1089631
Updated by Dominic Cleal over 10 years ago
- Status changed from New to Resolved
Seems to be working, marking as resolved.
[root@foreman ~]# hammer organization create --name foo Organization created [root@foreman ~]# hammer organization list ---|----- ID | NAME ---|----- 1 | foo ---|----- [root@foreman ~]# hammer proxy list ---|---------------------|--------------------------------- ID | NAME | URL ---|---------------------|--------------------------------- 1 | foreman.example.com | https://foreman.example.com:8443 ---|---------------------|--------------------------------- [root@foreman ~]# hammer organization add-smart-proxy --name foo --smart-proxy foreman.example.com
Log shows:
Started PUT "/api/organizations/1" for ::1 at 2014-05-20 18:28:40 +0100
Processing by Api::V2::OrganizationsController#update as JSON
Parameters: {"organization"=>{"smart_proxy_ids"=>["1"]}, "apiv"=>"v2", "id"=>"1"}
Authorized user admin(Admin User)
Expire fragment views/tabs_and_title_records-3 (0.6ms)
Completed 200 OK in 258ms (Views: 0.6ms | ActiveRecord: 0.0ms)
UI via org edit confirms it.
[root@foreman ~]# hammer organization add-user --id 1 --user-id 4 The user has been associated
Started PUT "/api/organizations/1" for ::1 at 2014-05-20 18:29:34 +0100
Processing by Api::V2::OrganizationsController#update as JSON
Parameters: {"organization"=>{"user_ids"=>["4"]}, "apiv"=>"v2", "id"=>"1"}
Authorized user admin(Admin User)
Expire fragment views/tabs_and_title_records-3 (0.5ms)
Completed 200 OK in 167ms (Views: 0.7ms | ActiveRecord: 0.0ms)
Updated by Bryan Kearney over 10 years ago
- Project changed from Hammer CLI to Katello
- Status changed from Resolved to New
- Assignee set to dustin tsang
- Triaged set to No
Updated by Bryan Kearney over 10 years ago
This only seems to occur when katello is installer, moving over to katello
Updated by Eric Helms over 10 years ago
- Status changed from New to Assigned
- Target version changed from 44 to 45
- Triaged changed from No to Yes
Updated by dustin tsang over 10 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Applied in changeset katello|commit:5dfda340f90f93039de436203b6b5b2f66186c6a.
Updated by Eric Helms over 10 years ago
- Translation missing: en.field_release set to 13