Bug 1431246 - Cannot update cluster from 3.6 to 4.0 - Exception: java.lang.IllegalStateException: At most one USB controller expected...
Summary: Cannot update cluster from 3.6 to 4.0 - Exception: java.lang.IllegalStateExce...
Keywords:
Status: CLOSED DUPLICATE of bug 1430009
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: ---
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.1.2
: ---
Assignee: jniederm
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-10 17:35 UTC by Jiri Belka
Modified: 2017-03-13 13:16 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-13 13:16:38 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.1+


Attachments (Terms of Use)

Description Jiri Belka 2017-03-10 17:35:04 UTC
Description of problem:

Cannot update cluster from 3.6 to 4.0 - Exception: 
java.lang.IllegalStateException: At most one USB controller expected...

in UI dialog:

Operation Canceled
Error while executing action Edit Cluster properties: Internal Engine Error

A part of engine.log:

Cannot update cluster from 3.6 to 4.0 - Exception: 
java.lang.IllegalStateException: At most one USB controller expected...

IIUC it happens as there was a snapshot from 3.5 cluster on 3.6 engine which was later previewed and commited in 4.0 engine with 3.6 cluster:

2017-03-10 18:26:09,588 ERROR [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-49) [12abba1a] Exception: java.lang.IllegalStateException: At most one USB controller expected for VM=vm4-test3(8443a9e4-dbb
5-44b9-95d7-d3ea57ef42b2), found=[VmDevice:{id='VmDeviceId:{deviceId='4c81b173-f880-4967-b61a-6eba4f3eb8e6', vmId='8443a9e4-dbb5-44b9-95d7-d3ea57ef42b2'}', device='usb', type='CONTROLLER', bootOrder='0', specPara
ms='[]', address='{slot=0x01, bus=0x00, domain=0x0000, type=pci, function=0x2}', managed='false', plugged='true', readOnly='false', deviceAlias='usb', customProperties='[]', snapshotId='null', logicalName='null',
 usingScsiReservation='false', hostDevice='null'}, VmDevice:{id='VmDeviceId:{deviceId='bed78f15-54f3-4a45-b9a1-5f1d594e22e6', vmId='8443a9e4-dbb5-44b9-95d7-d3ea57ef42b2'}', device='usb', type='CONTROLLER', bootOr
der='0', specParams='[index=0, model=piix3-uhci]', address='', managed='true', plugged='false', readOnly='false', deviceAlias='', customProperties='[]', snapshotId='null', logicalName='null', usingScsiReservation
='false', hostDevice='null'}]
        at org.ovirt.engine.core.bll.utils.VmDeviceUtils.updateNormalUsb(VmDeviceUtils.java:766) [bll.jar:]
        at org.ovirt.engine.core.bll.utils.VmDeviceUtils.updateUsbSlots(VmDeviceUtils.java:707) [bll.jar:]
        at org.ovirt.engine.core.bll.utils.VmDeviceUtils.updateVmDevices(VmDeviceUtils.java:1185) [bll.jar:]
        at org.ovirt.engine.core.bll.UpdateVmCommand.executeVmCommand(UpdateVmCommand.java:236) [bll.jar:]
        at org.ovirt.engine.core.bll.VmCommand.executeCommand(VmCommand.java:103) [bll.jar:]
        at org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1305) [bll.jar:]
        at org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1447) [bll.jar:]
        at org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2075) [bll.jar:]
        at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInRequired(TransactionSupport.java:141) [utils.jar:]
        at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:107) [utils.jar:]

Version-Release number of selected component (if applicable):
ovirt-engine-4.0.7.4-0.1.el7ev.noarch

How reproducible:
1 in 1

Steps to Reproduce:
1. (would take time to reproduce but maybe this would help) have 3.6 engine with 3.5 cluster with el6
2. have a vm, create snapshot
3. upgrade whole env to 4.0 engine, 3.6 ngn (el7), cluster 3.6/dc 3.6
4. preview snapshot and commit
5. update hsots to 4.0 ngn
6. update cluster to 4.0

Actual results:
Internal Engine Error in UI

Expected results:
should work

Additional info:

Comment 1 Jiri Belka 2017-03-10 17:38:54 UTC
Update of VM properties - ie. open Edit dialog and click OK - is broken, same error in engine.log.

Thus it seems the result is losing a VM?

Comment 2 Jiri Belka 2017-03-10 17:39:29 UTC
Same for running the VM, failure.

Comment 3 Michal Skrivanek 2017-03-11 09:29:03 UTC
please get the full engine.log containing the VM run or attach a screenshot of VM's "VM Devices" subtab listing all devices

Comment 4 Tomas Jelinek 2017-03-13 07:55:31 UTC
Hmm, maybe in such situation instead of failing the edit just fix the usb controllers (e.g. remove all and recreate)?

Comment 6 Jiri Belka 2017-03-13 09:51:39 UTC
(In reply to Michal Skrivanek from comment #3)
> please get the full engine.log containing the VM run or attach a screenshot
> of VM's "VM Devices" subtab listing all devices

Unfortunatelly I had to delete that VM to proceed with my work.

Comment 7 jniederm 2017-03-13 13:16:38 UTC

*** This bug has been marked as a duplicate of bug 1430009 ***


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