Bug 1751354 - virt-who configuration password required but no asterisk
Summary: virt-who configuration password required but no asterisk
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Virt-who Configure Plugin
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: 6.6.0
Assignee: Marek Hulan
QA Contact: Kunxin Huang
satellite-doc-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-11 19:28 UTC by Jeffrey Cutter
Modified: 2019-10-22 19:51 UTC (History)
2 users (show)

Fixed In Version: tfm-rubygem-foreman_virt_who_configure-0.4.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:51:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
password required but no asterisk on name (32.71 KB, image/png)
2019-09-11 19:28 UTC, Jeffrey Cutter
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27804 0 Normal Closed Cannot create kubevirt config for virt-who configure plugin via UI 2019-12-12 05:38:51 UTC
Red Hat Bugzilla 1745944 0 unspecified CLOSED Cannot create kubevirt config for virt-who configure plugin via UI 2021-02-22 00:41:40 UTC

Description Jeffrey Cutter 2019-09-11 19:28:35 UTC
Created attachment 1614206 [details]
password required but no asterisk on name

Description of problem:

When creating or editing a virt-who configuration in the WebUI, the Hypervisor Password is required but there is no asterisk on that field as with the other required fields.

Comment 3 Marek Hulan 2019-09-12 06:14:08 UTC
Fixed as part of fix for https://bugzilla.redhat.com/show_bug.cgi?id=1745944

Comment 5 Bryan Kearney 2019-10-22 19:51:28 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, 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/RHSA-2019:3172


Note You need to log in before you can comment on or make changes to this bug.