Bug 1263662 - Button "Set Serial Console Key" is misplaced
Summary: Button "Set Serial Console Key" is misplaced
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ovirt-3.6.0-ga
: 3.6.0
Assignee: Nobody
QA Contact: Karolína Hajná
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-16 11:23 UTC by Eldan Hildesheim
Modified: 2016-05-20 01:23 UTC (History)
5 users (show)

Fixed In Version: 3.6.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-27 07:56:27 UTC
oVirt Team: Virt
Embargoed:
ofrenkel: ovirt-3.6.0?
rule-engine: planning_ack?
ofrenkel: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)
Button "Set Serial Console Key" is misplaced. (108.09 KB, image/jpeg)
2015-09-16 11:23 UTC, Eldan Hildesheim 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 46241 0 None None None Never

Description Eldan Hildesheim 2015-09-16 11:23:30 UTC 
Created attachment 1073981 [details]
Button "Set Serial Console Key" is misplaced.

Description of problem:
Button "Set Serial Console Key" is misplaced.


Actual results:
The button is misplaced under the VM tab.


Expected results:
Should be moved to an option under the username dropdown,
since the ssh key is a property of the user and not the system.
What would happen if a system has 2 or more  administrators?
Comment 1 Red Hat Bugzilla Rules Engine 2015-10-19 11:00:20 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 2 Karolína Hajná 2015-11-13 09:11:22 UTC 
Verified on oVirt 3.6.0.3-1.el6
Comment 3 Sandro Bonazzola 2015-11-27 07:56:27 UTC 
Since oVirt 3.6.0 has been released, moving from verified to closed current release.
Note You need to log in before you can comment on or make changes to this bug.