On Tue, Sep 12, 2017 at 1:32 PM, oVirt Jenkins <jenkins(a)ovirt.org&gt; wrote: This is indeed due to a bug in that change. Should have been solved by a later patch, already merged: https://gerrit.ovirt.org/81500 What should I do? For the record, the bug was an extra newline in lines 102 and 113 of: https://gerrit.ovirt.org/#/c/81499/2/src/plugins/otopi/dialog/machine.py Causing the second line to be sent without a prefix, thus confusing the MachineDialogParser, in: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2484/artifa... 2017-09-12 05:45:43,175-04 DEBUG [org.ovirt.otopi.dialog.MachineDialogParser] (VdsDeploy) [12d19b6d] Got: **%EventsListEnd 2017-09-12 05:45:43,175-04 DEBUG [org.ovirt.otopi.dialog.MachineDialogParser] (VdsDeploy) [12d19b6d] Got: **%EventEnd 2017-09-12 05:45:43,175-04 DEBUG [org.ovirt.otopi.dialog.MachineDialogParser] (VdsDeploy) [12d19b6d] Got: STAGE init METHOD otopi.plugins.otopi.dialog.machine.Plugin._init_machine_events_stuff (None) 2017-09-12 05:45:43,175-04 ERROR [org.ovirt.otopi.dialog.MachineDialogParser] (VdsDeploy) [12d19b6d] Cannot parse input: java.lang.RuntimeException: Invalid data received during bootstrap at org.ovirt.otopi.dialog.MachineDialogParser.nextEvent(MachineDialogParser.java:358) [otopi.jar:] at org.ovirt.otopi.dialog.MachineDialogParser.nextEvent(MachineDialogParser.java:393) [otopi.jar:] at org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase.threadMain(VdsDeployBase.java:310) [bll.jar:] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141] -- Didi