Bug 1038226

Summary: [Admin Portal] Broken main VM tab UI when there's a VM having settings from OSInfo file that does not exist anymore
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: ovirt-engine-webadmin-portalAssignee: Shahar Havivi <shavivi>
Status: CLOSED WONTFIX QA Contact: sefi litmanovich <slitmano>
Severity: high Docs Contact:
Priority: low    
Version: 3.3.0CC: ecohen, istein, mgoldboi, michal.skrivanek, ofrenkel, rbalakri, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: 4.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-02 12:53:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
engine.log none

Description Jiri Belka 2013-12-04 16:30:12 UTC
Created attachment 832742 [details]
engine.log

Description of problem:
Broken main VM tab UI when there's a VM having settings from OSInfo file that does nto exist anymore. This is not related to browser cache as I used completely clean FF 17 profile.

Version-Release number of selected component (if applicable):
is25

How reproducible:
100%

Steps to Reproduce:
0. have some normal VM running
1. create new osinfo like below:
-%-
os.OpenBSD.id.value = 666
os.OpenBSD.name.value = OpenBSD
os.OpenBSD.devices.network.value = pv
os.OpenBSD.derivedFrom.value = other
-%-
   as /etc/ovirt-engine/osinfo.conf.d/08-sectderiveexistvalues.properties
2. service ovirt-engine restart
3. create new VM, select OS type as OpenBSD (the best OS, :P)
4. log of
5. delete /etc/ovirt-engine/osinfo.conf.d/08-sectderiveexistvalues.properties
6. service ovirt-engine restart
7. fire up FF with clean profile
8. log in  and do next steps:
9. - select the VM, try to go to VM properties (Edit button, right-click -> 
Edit). Secret trick: switch to other main tab, go back to VM main tab, select other "valid" VM (you should see active Edit), select problematic VM
10.- do previous secret trick to start the problematic VM, try to open console (Console button, right-click -> Console). Do secret trick from above but now select other running "valid" VM, then select again problematic VM and try to open console

Actual results:
UI is broken in VM main tab
9 - impossible to edit the VM
10 - impossible to open console, with the trick again, you get console from previously selected VM (the "valid" one and running) not the problematic VM's console

Expected results:
???

Additional info:
yes it is not good when we deliberately delete our own osinfo file but there's still something fishy in UI :)

2013-Dec-04, 16:40
VM broken-ui was created by admin@internal.

Comment 1 Michal Skrivanek 2014-08-22 13:01:35 UTC
this bug won't fit into 3.5 release and is being deferred to a later release. If you deeply care about this bug and deserves to be re-evaluated please let me know

Comment 2 Moran Goldboim 2015-09-02 12:51:36 UTC
lowering priority and pushing to 4.0, rare use case.

Comment 3 Michal Skrivanek 2015-09-02 12:53:07 UTC
too much effort, there are lot of things which falls apart once you remove one config.
osinfo additions are just one way

no one touched this for a year, closing as we won't get to it in 3.6, likely nor 4.0 either...