Michal Skrivanek <michal.skrivanek@redhat.com> writes:
On 1 Sep 2017, at 13:39, Piotr Kliczewski <piotr.kliczewski@gmail.com> wrote:
All,
I pulled the latest engine master [1] and I see following exception below. Is it known issue?
I wonder if that’s a regression from Milan’s vdsm work on recovery/external vms….
Yes, it is. Engine assumes presence of some properties in external VMs that are apparently not present. I think Vdsm should extract them from domain XML in recovery.
[1] Based on 34f4d69117d916e52a7b2d5032d64b8d1185448c
2017-09-01 13:35:38,829+02 ERROR [org.ovirt.engine.core.bll.AddUnmanagedVmsCommand] (DefaultQuartzScheduler10) [353095e7] Command 'org.ovirt.engine.core.bll.AddUnmanagedVmsCommand' failed: null 2017-09-01 13:35:38,829+02 ERROR [org.ovirt.engine.core.bll.AddUnmanagedVmsCommand] (DefaultQuartzScheduler10) [353095e7] Exception: java.lang.NumberFormatException: null at java.lang.Integer.parseInt(Integer.java:542) [rt.jar:1.8.0_141] at java.lang.Integer.parseInt(Integer.java:615) [rt.jar:1.8.0_141] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder.parseIntVdsProperty(VdsBrokerObjectsBuilder.java:775) [vdsbroker.jar:] at org.ovirt.engine.core.bll.AddUnmanagedVmsCommand.convertVm(AddUnmanagedVmsCommand.java:119) [bll.jar:] at org.ovirt.engine.core.bll.AddUnmanagedVmsCommand.executeCommand(AddUnmanagedVmsCommand.java:96) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1202) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1342) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:1984) [bll.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:164) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:103) [utils.jar:]