Bug 1322430

Summary: Introspection hangs for a node using an iscsi volume for boot
Product: Red Hat OpenStack Reporter: Ruchika K <rkharwar>
Component: openstack-ironic-discoverdAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: Shai Revivo <srevivo>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: apevec, bnemec, dtantsur, lhh, mburns, rhel-osp-director-maint, rkharwar
Target Milestone: ---   
Target Release: 10.0 (Newton)   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-06 16:11:51 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
Failing node's screenshot
none
Failiong nodes screenshot 2/2
none
rdsosreport from 1st failing node none

Comment 1 Ruchika K 2016-03-30 13:44:38 UTC 
Description of problem:
Introspection appears to hang when running introspection on a node with only 
- 1. iscsi volume for boot
- 2. USB stick
- 3. No other local storage


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


How reproducible:
100%

Steps to Reproduce:
1. Netapp storage configured with LUNS and LUNs mapped to individual nodes.
2. On the undercloud the following settings are made

/usr/lib/python2.7/site-packages/ironic/drivers/modules/ipxe_config.template was updated to append  "rd.iscsi.ibft=1 rd.iscsi.firmware=1"

/httpboot/discoverd.ipxe was updated to append "rd.iscsi.firmware=1"


3.

Actual results:
Introspection fails to complete and hangs waiting for the node to respond with some status.


Expected results:


Additional info:
Comment 2 Ruchika K 2016-03-30 19:57:09 UTC 
Created attachment 1141917 [details]
Failing node's screenshot
Comment 3 Ruchika K 2016-03-30 19:57:39 UTC 
Created attachment 1141918 [details]
Failiong nodes screenshot 2/2
Comment 4 Ruchika K 2016-03-30 21:36:36 UTC 
Created attachment 1141944 [details]
rdsosreport from 1st failing node
Comment 6 Ben Nemec 2016-04-04 16:25:42 UTC 
Copying in the IRC discussion I had with Chris regarding the rdsosreport log:

<bnemec> I'm seeing: Warning: iscistart: Could not get list of targets from firmware.
<bnemec> Which causes iscsistart to exit 1.
<bnemec> Then dracut is waiting for iscsi to finish starting: /lib/dracut-lib.sh@425(check_finished): . /lib/dracut/hooks/initqueue/finished/iscsi_started.sh
<bnemec> Which it never does because it already failed earlier.

I see a note from Chris as well that on Friday they were able to introspect a single node in this environment.  I don't have any more details than that though, so I can't say what was done to get it working.
Comment 7 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 9 Dmitry Tantsur 2016-09-06 16:11:51 UTC 

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