Bug 1737879 - Get wrong prompts when create virt-who-config missing argments via hammer CLI
Summary: Get wrong prompts when create virt-who-config missing argments via hammer CLI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: 6.8.0
Assignee: satellite6-bugs
QA Contact: Kunxin Huang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-06 10:21 UTC by Kunxin Huang
Modified: 2020-10-27 13:32 UTC (History)
12 users (show)

Fixed In Version: tfm-rubygem-hammer_cli-0.20.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:32:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27595 0 Normal Closed Get wrong prompts when create virt-who-config missing argments via hammer CLI 2020-10-19 13:58:06 UTC
Red Hat Product Errata RHBA-2020:4367 0 None None None 2020-10-27 13:32:24 UTC

Comment 3 Marek Hulan 2019-08-06 10:33:24 UTC 
This does not seem specific to virt-who-config command but rather the whole CLI, moving to Hammer for further investigation of what we can do to improve experience here.
Comment 6 Oleh Fedorenko 2019-08-12 16:27:05 UTC 
Created redmine issue https://projects.theforeman.org/issues/27595 from this bug
Comment 7 Bryan Kearney 2019-11-05 20:31:25 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27595 has been resolved.
Comment 13 errata-xmlrpc 2020-10-27 13:32:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite 6.8 Satellite Tools Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4367
Note You need to log in before you can comment on or make changes to this bug.