Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Packstack complains of not being able to detect ipaddress of interface

About a month after installing RDO Kilo on CentOS 7 with packstack, I wanted to set up horizon to use https. So using the same answer file that we used originally, I edited the CONFIG_HORIZON_SSL option to read "y" instead of "n" and re-ran packstack, with the following result:

Adding Neutron FWaaS Agent manifest entries          [ DONE ]
Adding Neutron LBaaS Agent manifest entries          [ DONE ]
Adding Neutron API manifest entries               [ ERROR ]

ERROR : "Couldn't detect ipaddress of interface ten on node 10.0.2.13"
Please check log file /var/tmp/packstack/20150810-170722-80OEvA/openstack-setup.log for more information

The log file adds nothing to this error report. It is looking for interface "ten" (short for tenant) because:

# Interface for the Open vSwitch tunnel. Packstack overrides the IP
# address used for tunnels on this hypervisor to the IP found on the
# specified interface (for example, eth1).
CONFIG_NEUTRON_OVS_TUNNEL_IF=ten

However, you can:

[root@plume ~(keystone_admin)]# ssh 10.0.2.13
Last login: Mon Aug 10 16:54:15 2015 from 10.0.2.1
[root@compute-0-3 ~]# ip addr show dev ten
3: ten: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
   link/ether 00:1e:67:b3:75:42 brd ff:ff:ff:ff:ff:ff
    inet 10.0.1.13/24 brd 10.0.1.255 scope global ten
       valid_lft forever preferred_lft forever
     inet6 fe80::21e:67ff:feb3:7542/64 scope link
       valid_lft forever preferred_lft forever
[root@compute-0-3 ~]# ping 10.0.1.1
PING 10.0.1.1 (10.0.1.1) 56(84) bytes of data.
64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=0.267 ms
64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=0.196 ms
^C
--- 10.0.1.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.196/0.231/0.267/0.038 ms
[root@compute-0-3 ~]# logout
Connection to 10.0.2.13 closed.
[root@plume ~(keystone_admin)]# ping 10.0.1.13
PING 10.0.1.13 (10.0.1.13) 56(84) bytes of data.
64 bytes from 10.0.1.13: icmp_seq=1 ttl=64 time=0.231 ms
64 bytes from 10.0.1.13: icmp_seq=2 ttl=64 time=0.187 ms
^C
--- 10.0.1.13 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.187/0.209/0.231/0.022 ms

I also attempted to run packstack using the original (unmodified) answer file. Same result. Could someone point me to why this answer file might be behaving this way this month, when last month it seemed happy?

Packstack complains of not being able to detect ipaddress of interface

About a month after installing RDO Kilo on CentOS 7 with packstack, I wanted to set up horizon to use https. So using the same answer file that we used originally, I edited the CONFIG_HORIZON_SSL option to read "y" instead of "n" and re-ran packstack, with the following result:

Adding Neutron FWaaS Agent manifest entries          [ DONE ]
Adding Neutron LBaaS Agent manifest entries          [ DONE ]
Adding Neutron API manifest entries               [ ERROR ]

ERROR : "Couldn't detect ipaddress of interface ten on node 10.0.2.13"
Please check log file /var/tmp/packstack/20150810-170722-80OEvA/openstack-setup.log for more information

The log file adds nothing to this error report. It is looking for interface "ten" (short for tenant) because:

# Interface for the Open vSwitch tunnel. Packstack overrides the IP
# address used for tunnels on this hypervisor to the IP found on the
# specified interface (for example, eth1).
CONFIG_NEUTRON_OVS_TUNNEL_IF=ten

However, you can:

[root@plume ~(keystone_admin)]# ssh 10.0.2.13
Last login: Mon Aug 10 16:54:15 2015 from 10.0.2.1
[root@compute-0-3 ~]# ip addr show dev ten
3: ten: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
   link/ether 00:1e:67:b3:75:42 brd ff:ff:ff:ff:ff:ff
    inet 10.0.1.13/24 brd 10.0.1.255 scope global ten
       valid_lft forever preferred_lft forever
     inet6 fe80::21e:67ff:feb3:7542/64 scope link
       valid_lft forever preferred_lft forever
[root@compute-0-3 ~]# ping 10.0.1.1
PING 10.0.1.1 (10.0.1.1) 56(84) bytes of data.
64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=0.267 ms
64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=0.196 ms
^C
--- 10.0.1.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.196/0.231/0.267/0.038 ms
[root@compute-0-3 ~]# logout
Connection to 10.0.2.13 closed.
[root@plume ~(keystone_admin)]# ping 10.0.1.13
PING 10.0.1.13 (10.0.1.13) 56(84) bytes of data.
64 bytes from 10.0.1.13: icmp_seq=1 ttl=64 time=0.231 ms
64 bytes from 10.0.1.13: icmp_seq=2 ttl=64 time=0.187 ms
^C
--- 10.0.1.13 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.187/0.209/0.231/0.022 ms

I also attempted to run packstack using the original (unmodified) answer file. Same result. Could someone point me to why this answer file might be behaving this way this month, when last month it seemed happy?