Project

General

Profile

Bug #4309

hammer host start no longer powers on VMware host

Added by Matt Chesler almost 9 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Hosts
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:
In Kanboard:
Red Hat JIRA:

Description

hammer host start --name <FQDN> worked properly to power on VMware host prior to Foreman 1.4.0 upgrade, now it exits with nothing printed to STDOUT/STDERR and an exit code of 65.

This is an RPM based installation, upgraded from Foreman 1.3.2

Relevant RPM versions:

ruby193-rubygem-fog.noarch 1.19.0-1.el6 @foreman
rubygem-hammer_cli.noarch 0.0.18-1.el6 @foreman
rubygem-hammer_cli_foreman.noarch 0.0.18-1.el6 @foreman
foreman.noarch 1.4.0-1.el6 @foreman


Related issues

Related to Foreman - Bug #4315: Hosts power management API doesn't return standard error responsesNew
Related to Hammer CLI - Tracker #26990: Tracker for VMware issuesClosed

History

#1 Updated by Dominic Cleal almost 9 years ago

  • Project changed from Foreman to Hammer CLI
  • Category set to Foreman commands (obsolete)
  • Status changed from New to Need more information

Could you please run hammer with -v, and also paste the contents of /var/log/foreman/production.log when running the command?

#2 Updated by Matt Chesler almost 9 years ago

hammer -v output:

$ hammer -v host start --id 597
[ERROR 2014-02-11 09:23:36 Exception] <NilClass> nil

From /var/log/foreman/production.log:

Started PUT "/api/hosts/597/power" for 127.0.0.1 at 2014-02-11 09:23:36 -0500
Processing by Api::V2::HostsController#power as JSON
  Parameters: {"apiv"=>"v2", "id"=>"597", "host"=>{}}
Authorized user admin(Admin User)
Completed 422 Unprocessable Entity in 29ms (Views: 0.4ms | ActiveRecord: 6.2ms)

#3 Updated by Dominic Cleal almost 9 years ago

  • Status changed from Need more information to New

Looks like it's missing the power_action parameter for the API call. The API controller isn't returning the right format either for error messages, so I'll create an issue for that.

#4 Updated by Dominic Cleal almost 9 years ago

  • Related to Bug #4315: Hosts power management API doesn't return standard error responses added

#5 Updated by Tomáš Strachota over 4 years ago

  • Category changed from Foreman commands (obsolete) to Hosts

#6 Updated by Oleh Fedorenko over 3 years ago

#7 Updated by Oleh Fedorenko over 3 years ago

I tried to power on a VMware host on latest Foreman instance with hammer and it worked. Also hammer shows errors properly if there is any.

Closing the issue.

#8 Updated by Oleh Fedorenko over 3 years ago

  • Status changed from New to Closed

Also available in: Atom PDF