Project

General

Profile

Actions

Bug #19253

closed

hammer: `... job-invocation info -h` says "--name" is a possible option, but it returns "Error: 400 Bad Request"

Added by Adam Ruzicka about 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
CLI
Target version:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1440976

Description of problem:
`... job-invocation info -h` says "--name" is a possible option, but it returns "Error: 400 Bad Request"

Version-Release number of selected component (if applicable):
tfm-rubygem-hammer_cli-0.5.1.13-2.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_remote_execution-0.0.5.3-1.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. Have job with description "rex-template-date.sh at 2017-04-10"
2. Check help for "job-invocation info" sub command: # hammer -d --username <user> --password <pass> job-invocation info --help
3. Try to use "--name": # hammer --username <admin> --password <pass> job-invocation info --name "rex-template-date.sh at 2017-04-10"

Actual results:
Error: 400 Bad Request

Expected results:
Either should work (and maybe "--name" should be renamed to "--description", or it should provide helpful error message.

Actions #1

Updated by Adam Ruzicka about 7 years ago

  • Category set to CLI
  • Target version set to 113
Actions #2

Updated by The Foreman Bot about 7 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Adam Ruzicka
  • Pull request https://github.com/theforeman/hammer_cli_foreman_remote_execution/pull/15 added
Actions #3

Updated by Adam Ruzicka about 7 years ago

  • Target version changed from 113 to 1.12.4
Actions #4

Updated by Anonymous about 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF