Actions
Bug #3370
closedAll subcommands associated with "organization" fail
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Foreman commands (obsolete)
Target version:
Description
All subcommands associated with hammer organization fail with message "The server does not support such operation."
[root@rhel6b ~]# hammer -v organization list [ INFO 2013-10-18 20:24:36 Init] Configuration from the file /etc/foreman/cli_config.yml has been loaded [ INFO 2013-10-18 20:24:36 Init] Extension module hammer_cli_foreman loaded [ INFO 2013-10-18 20:24:36 HammerCLI::MainCommand] Called with options: {"verbose"=>true} [ INFO 2013-10-18 20:24:36 HammerCLIForeman::Organization] Called with options: {} [ INFO 2013-10-18 20:24:36 HammerCLIForeman::Organization::ListCommand] Called with options: {} The server does not support such operation.
production.log shows a weird request:
Started GET "/api/organization_id" for ::1 at 2013-10-18 20:25:05 +0000 Processing by Api::V1::HomeController#route_error as JSON Parameters: {"other"=>"organization_id", "home"=>{}} Authorized user admin(Admin User) Rendered api/v1/errors/route_error.json.rabl (0.3ms) Completed 404 Not Found in 16ms (Views: 0.9ms | ActiveRecord: 5.8ms)
foreman-1.3.0-1.el6.noarch
rubygem-hammer_cli-0.0.7-1.el6.noarch
rubygem-hammer_cli_foreman-0.0.7-1.el6.noarch
Updated by Martin Bacovsky about 11 years ago
- Status changed from New to Assigned
- Assignee set to Martin Bacovsky
- Target version set to 1.15.0
- Translation missing: en.field_release set to 1
This is caused by foreman_api that was generated with buggy version of apipie. Fixing the deps.
Updated by Martin Bacovsky about 11 years ago
- Status changed from Assigned to Ready For Testing
Updated by Martin Bacovsky about 11 years ago
- Status changed from Ready For Testing to Resolved
Actions