Project

General

Profile

Actions
Copy link

Bug #4308

closed

hammer host actions are not consistent with parameter requirements

Added by Matt Chesler about 11 years ago. Updated over 5 years ago.

Status:
Resolved
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 status" works with either name or id but "hammer host start" returns an error unless id is provided.

Example:

$ hammer host status
Error: At least one of options --name, --id is required

$ hammer host status --name host.example.com
Status: Pending Installation
Power: poweredOff

$ hammer host status --id 571
Status: Pending Installation
Power: poweredOff

$ hammer host start --name host.example.com
missing param 'id' in parameters

$ hammer host start --id 571
[NO OUTPUT]

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

Actions
Copy link
 #1

Updated by Dominic Cleal about 11 years ago

  • Project changed from Foreman to Hammer CLI
  • Category set to Foreman commands (obsolete)
Actions
Copy link
 #2

Updated by Tomáš Strachota almost 7 years ago

  • Category changed from Foreman commands (obsolete) to Hosts
Actions
Copy link
 #3

Updated by Shira Maximov over 5 years ago

  • Status changed from New to Resolved

This issue was resolved already.

Actions
Copy link

Also available in: Atom PDF