Bug 1312020

Summary: During bulk introspection on virt one of the VMs times out with Error 0x040ee119
Product: Red Hat OpenStack Reporter: Marius Cornea <mcornea>
Component: rhosp-directorAssignee: Angus Thomas <athomas>
Status: CLOSED DUPLICATE QA Contact: Arik Chernetsky <achernet>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: dbecker, mburns, morazi, rhel-osp-director-maint
Target Milestone: y1   
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-26 13:08:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
intro.png none

Description Marius Cornea 2016-02-25 14:27:23 UTC
Created attachment 1130559 [details]
intro.png

Description of problem:
During bulk introspection on virt one VM times out with Error 0x040ee119.

Version-Release number of selected component (if applicable):
2016-02-19.3 puddle

How reproducible:
several times

Steps to Reproduce:
1. Deploy virt environment with 8 overcloud nodes
2. Run openstack baremetal introspection bulk start

Actual results:
One of the VMs doesn't run introspection, its gets stuck with Error 0x040ee119, No more network devices. 

Additional info:
Attaching a screenshot.

Manually resetting the VM gets it to boot.

Comment 1 Marius Cornea 2016-02-25 14:33:20 UTC
I see the following in openstack-ironic-inspector-dnsmasq.service journal:

DHCPNAK(br-ctlplane) 192.0.2.108 00:c7:f4:cf:58:7a address in use
DHCPNAK(br-ctlplane) 192.0.2.108 00:c7:f4:cf:58:7a address in use
DHCPNAK(br-ctlplane) 192.0.2.108 00:c7:f4:cf:58:7a address in use
DHCPNAK(br-ctlplane) 192.0.2.108 00:c7:f4:cf:58:7a address in use

which corresponds with the mac of the VM which is failed to boot. 192.0.2.108 though doesn't look to be pingable.

Comment 2 Marius Cornea 2016-02-26 13:08:42 UTC

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