Feature #1740
VNC password should be optional on hypervisors
| Status: | New | Start: | 07/10/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | compute resources | |||
| Target version: | - | |||
| Backlog: | No | Difficulity: | ||
| Votes: | 3 (View) |
Description
As http://theforeman.org/issues/1739 is quite annoying for us,
the VNC password for direct connection in hypervisors should be optional.
Related issues
| related to Foreman - Feature #1711: Need an option to choose whether a Libvirt-based VM should have a VNC password set or not | New | 06/26/2012 |
History
Updated by Romain Vrignaud 11 months ago
- Tracker changed from Bug to Feature
Updated by Joshua Hoblitt 8 months ago
It would also be very convenient for theforeman to show the password it generated/set somewhere in on the host display. With libvirt, you have to dump the VMs xml config to fish out the vnc passwords that's been set.
Updated by Ryan Davies about 1 month ago
Joshua Hoblitt wrote:
It would also be very convenient for theforeman to show the password it generated/set somewhere in on the host display. With libvirt, you have to dump the VMs xml config to fish out the vnc passwords that's been set.
This would be a fantastic feature
Updated by Benjamin Papillon about 14 hours ago
As a workaround I'm viewing the html source where the password is
