Bug 1324622

Summary: failed to discover hardware
Product: Red Hat OpenStack Reporter: Dan Yocum <dyocum>
Component: openstack-ironic-discoverdAssignee: RHOS Maint <rhos-maint>
Status: CLOSED WORKSFORME QA Contact: Shai Revivo <srevivo>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: apevec, dmanchad, dtantsur, ggillies, lhh, mburns, rhel-osp-director-maint
Target Milestone: ---   
Target Release: 10.0 (Newton)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-02 08:05:58 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:
Attachments:
Description Flags
openstack-ironic-inspector logs none

Description Dan Yocum 2016-04-06 19:48:59 UTC 
Description of problem:

When running ironic introspection, it fails with the error message:

WARNING: log file /run/initramfsw/rdsosreport.txt does not exist
ERROR: discoverd error 400: Unexpected exception during processing
ERROR: 400 Client Error: BAD REQUEST when calling discoverd
///lib/dracut/hooks/pre-mount/50-init.sh@475(source): give_up 'Failed to discover hardware'
///lib/dracut/hooks/pre-mount/50-init.sh@144(give_up): log 'Failed to discover hardware'
///lib/dracut/hooks/pre-mount/50-init.sh@136(log): echo 'Failed to discover hardware'
Failed to discover hardware

The last few lines in journalctl are:

DHCPDISCOVER on em1 to 255.255.255.255 ...
No DHCPOFFERS received.
DHCPDISCOVER on em3 to 255.255.255.255 ...
No DHCPOFFERS received.


NB: em1 is the 10GbT nic for api, tenant, storage, and storage management vlans.
em3 is the provisioning network

Version-Release number of selected component (if applicable):

OSP-d 7.3

[root@director1 ~]# rpm -qa | grep 'oscplug\|heat-templates'
openstack-heat-templates-0-0.8.20150605git.el7ost.noarch
openstack-tripleo-heat-templates-0.8.6-123.el7ost.noarch
python-rdomanager-oscplugin-0.0.10-28.el7ost.noarch

[root@director1 ~]# rpm -qa | grep ironic
python-ironicclient-0.5.1-12.el7ost.noarch
openstack-ironic-discoverd-1.1.0-8.el7ost.noarch
openstack-ironic-common-2015.1.2-2.el7ost.noarch
openstack-ironic-api-2015.1.2-2.el7ost.noarch
openstack-ironic-conductor-2015.1.2-2.el7ost.noarch
python-ironic-discoverd-1.1.0-8.el7ost.noarch


How reproducible:

every
Comment 2 Mike Burns 2016-04-07 21:36:02 UTC 
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.
Comment 3 Dmitry Tantsur 2016-04-18 08:22:13 UTC 
Hi! Please provide logs from the openstack-ironic-discoverd service.
Comment 5 Dan Yocum 2016-04-19 19:19:34 UTC 
Created attachment 1148721 [details]
openstack-ironic-inspector logs
Comment 6 Dmitry Tantsur 2016-05-09 12:43:06 UTC 
What's the version we're dealing with? The bug says OSPd7.3, but I clearly see OSPd8. The only error I see in the logs is that ironic-inspector-dbsync was not run to create the database schema - see http://tripleo.org/troubleshooting/troubleshooting.html#how-can-introspection-be-stopped
Comment 7 Dan Yocum 2016-05-23 20:41:23 UTC 
I experienced this on both 7.3 and 8.0 until the RHELv7.2 RAM disk was updated, which (I believe) has resolved the issue.
Comment 8 Dmitry Tantsur 2016-06-01 15:12:25 UTC 
So is it resolved for both versions? If so please close it. If not, please state which one is left to fix.
Comment 9 Dan Yocum 2016-06-01 15:31:10 UTC 
I think it was resolved when the rhelv7.2 ramdisk was updated for both, but I'll let the RHOS Ops guys chime in here, since they've got the hardware, now.
Comment 10 Dan Yocum 2016-06-01 15:34:05 UTC 
I think this was resolved with the rhelv7.2 ramdisk update, but I'll let the RHOS Ops guys chime in since they are now in possession of the hardware - I don't have access to it, anymore.
Comment 11 Graeme Gillies 2016-06-01 23:52:28 UTC 
I can confirm this is now resolved with the hardware in question. We have been able to introspect the hardware multiple times now without issue

Regards,

Graeme
Comment 12 Dmitry Tantsur 2016-06-02 08:05:58 UTC 
Thanks!