Created attachment 684112 [details] logs and screen shot Description of problem: I put the iso domain in maintenance and I can see that the event log is reporting that it failed to refresh the floppy and iso lists while domain is in locked state. Version-Release number of selected component (if applicable): sf3 How reproducible: 100% Steps to Reproduce: 1. activate an iso domain 2. put domain in maintenance 3. Actual results: each time we put the iso domain in maintenance event lg is reporting that we failed to refresh it. Expected results: this alert should appear only when the domain is inactive and not when its in locked state. Additional info: screen shot and log 2013-01-21 10:47:45,411 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (pool-3-thread-48) [26357de3] Error code GetIsoListError and error message VDSGenericException: VDSErrorException: Failed to HsmGetIsoListVDS, e rror = Cannot get ISO list: ('afcde1c5-6022-4077-ab06-2beed7e5e404',) 2013-01-21 10:47:45,411 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (pool-3-thread-48) [26357de3] Command org.ovirt.engine.core.vdsbroker.vdsbroker.HsmGetIsoListVDSCommand return value Class Name: org.ovirt.engine.core.vdsbroker.irsbroker.IsoListReturnForXmlRpc mVMList Null mStatus Class Name: org.ovirt.engine.core.vdsbroker.vdsbroker.StatusForXmlRpc mCode 314 mMessage Cannot get ISO list: ('afcde1c5-6022-4077-ab06-2beed7e5e404',) 2013-01-21 10:47:45,411 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (pool-3-thread-48) [26357de3] HostName = gold-vdsd 2013-01-21 10:47:45,411 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (pool-3-thread-48) [26357de3] Command HsmGetIsoListVDS execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed to HsmG etIsoListVDS, error = Cannot get ISO list: ('afcde1c5-6022-4077-ab06-2beed7e5e404',)
Dafna, please explain what exact behavior is the regression, and from which version. thank you.
the regression is that in 3.0 and 3.1 when we put the iso domain in maintenance we would not get an error alert about not being able to read the iso list of the domain.
Added a check that if the domain is in maintenance, it is not written in event log in error because it's expected it cannot be accessed.
no error when putting ISO domain in maintenance. sf6.
3.2 has been released