Hide Forgot
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
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
Hi! Please provide logs from the openstack-ironic-discoverd service.
Created attachment 1148721 [details] openstack-ironic-inspector logs
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
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.
So is it resolved for both versions? If so please close it. If not, please state which one is left to fix.
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.
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.
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
Thanks!