Bug 1403636 - Packstack cannot detect IP of the 2nd NIC [NEEDINFO]
Summary: Packstack cannot detect IP of the 2nd NIC
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: Mitaka
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: trunk
Assignee: Martin Magr
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-12 02:35 UTC by Alex Meng
Modified: 2018-07-17 12:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-17 12:30:06 UTC
chris.brown: needinfo? (mengxiandong)

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Alex Meng 2016-12-12 02:35:23 UTC 
Description of problem:
When you want to install OpenStack with 2 NICs, packstack will fail and report error as below:
ERROR : "Couldn't detect ipaddress of interface eth1 on node 192.168.122.151"

Version-Release number of selected component (if applicable):
CentOS Linux release 7.2.1511 (Core)
openstack-packstack.noarch       8.0.2-1.el7
centos-release-openstack-mitaka-1-5.el7.noarch.rpm

How reproducible:

Steps to Reproduce:
1. Install CentOS 7.2 to a x86 server or VM with 2 NICs;
2. Generate packstack answer file, to put management network on NIC1 (specify the IPs for the service hosts), and put NIC2 device name as CONFIG_NEUTRON_OVS_TUNNEL_IF
3. Start installation with packstack.

Actual results:
PackStack will halt and report error similar to below message
ERROR : "Couldn't detect ipaddress of interface eth1 on node 192.168.122.151"

Expected results:
PackStack should be able to get the configured IP for eth1 and finish the 
installation without any error.

Additional info:
Comment 1 Alex Meng 2016-12-12 02:37:20 UTC 
Similar bug has been reported a long time ago:
https://ask.openstack.org/en/question/84889/packstack-fails-to-detect-ipaddress-of-interface-eth1/
Comment 2 Christopher Brown 2017-06-22 15:42:50 UTC 
Hi Alex,

Sorry you didn't get a response to this.

Can you let me know if this is still a problem and I'll take a look?

Thanks
Note You need to log in before you can comment on or make changes to this bug.