Re: [oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 40 - Still Failing!

On 16 Feb 2018, at 09:47, Michal Skrivanek <michal.skrivanek(a)redhat.com&gt; wrote: On 16 Feb 2018, at 09:28, Simone Tiraboschi <stirabos(a)redhat.com&gt; wrote: On Fri, Feb 16, 2018 at 9:24 AM, Michal Skrivanek <michal.skrivanek@ redhat.com> wrote: > > > On 16 Feb 2018, at 09:16, Simone Tiraboschi <stirabos(a)redhat.com&gt; wrote: > > > > On Fri, Feb 16, 2018 at 3:30 AM, <jenkins(a)jenkins.phx.ovirt.org&gt; wrote: > >> Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he- >> basic-ansible-suite-master/ >> Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he- >> basic-ansible-suite-master/40/ >> Build Number: 40 >> Build Status: Still Failing >> Triggered By: Started by timer >> >> > We have: > > , kvmEnable=true, bootMenuEnable=false, devices=[Ljava.lang.Object;@5f007fc2, custom={}, vmType=kvm, memSize=3171, clientIp=, statusTime=4295581800, vmName=HostedEngineLocal}], log id: 41f6151b > 2018-02-15 21:24:30,233-05 ERROR [org.ovirt.engine.core.bll.AddUnmanagedVmsCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-88) [33c6683] Command 'org.ovirt.engine.core.bll.AddUnmanagedVmsCommand' failed: null > 2018-02-15 21:24:30,233-05 ERROR [org.ovirt.engine.core.bll.AddUnmanagedVmsCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-88) [33c6683] Exception: java.lang.NumberFormatException: null > at java.lang.Integer.parseInt(Integer.java:542) [rt.jar:1.8.0_161] > at java.lang.Integer.parseInt(Integer.java:615) [rt.jar:1.8.0_161] > at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder.parseIntVdsProperty(VdsBrokerObjectsBuilder.java:805) [vdsbroker.jar:] > > in http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic- > ansible-suite-master/40/artifact/exported-artifacts/test_ > logs/he-basic-ansible-suite-master/post-he_deploy/lago-he- > basic-ansible-suite-master-engine/_var_log/ovirt-engine/engine.log > > I think it's a regression in the engine on master. > I opened a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1545862 > > > I wonder, at that moment is that supposed to be a Hosted Engine VM? I > mean a one to be imported as HE VM into engine. Or just a “plain” libvirt > VM from engine’s POV > It's the bootstrap local VM; it's named <name>HostedEngineLocal</name> so at engine eyes it's for sure just a plain libvirt VM. the reason I was asking is that the vdc option HostedEngineVmName set by default to “HostedEngine” is the differentiator in this flow between regular external vm and HE special import

it’s due to your vcpu definition. You have "<vcpu placement='static'>2</vcpu>” whereas all oVirt VMs use additional attribute “current”. see _parse_domain_init() in libvirtxml.py Francesco, that should be easy to parse differently, we do not need to require “current” Thanks, michal > > > >> ------------------------------------- >> Changes Since Last Success: >> ------------------------------------- >> Changes for Build #38 >> [Gal Ben Haim] 4.2: Update reposync-config.repo >> >> [Sandro Bonazzola] ovirt-engine-api-explorer: re-align >> >> [Barak Korren] Use usrc.py in check-patch.sh >> >> >> Changes for Build #39 >> [Sandro Bonazzola] repos: add jemalloc >> >> >> Changes for Build #40 >> [Dominik Holler] network: test_ovn_provider assumes that engine's FQDN >> is working >> >> [Roy Golan] Add ovirt-flexdriver github project to stdci >> >> >> >> >> ----------------- >> Failed Tests: >> ----------------- >> No tests ran. > > > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > >