[openstack-dev] Gate issues - what you can do to help

Clark Boylan clark.boylan at gmail.com
Thu Oct 3 16:49:38 UTC 2013


On Thu, Oct 3, 2013 at 6:54 AM, Gary Kotton <gkotton at vmware.com> wrote:
> Hi,
> I think that I may have stumbled upon the problem, but need the help from
> someone on the infra team. Then again I may just be completely mistaken.
>
> Prior to the little hiccup we have at the moment VM's that were used for
> devstack on the infra side would have 1 interface:
>
> 2013-09-10 06:32:22.208 | Triggered by: https://review.openstack.org/40359
> patchset 4
> 2013-09-10 06:32:22.208 | Pipeline: gate
> 2013-09-10 06:32:22.208 | IP configuration of this host:
> 2013-09-10 06:32:22.209 | 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc
> noqueue state UNKNOWN
> 2013-09-10 06:32:22.209 |     inet 127.0.0.1/8 scope host lo
> 2013-09-10 06:32:22.209 | 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu
> 1500 qdisc pfifo_fast state UP qlen 1000
> 2013-09-10 06:32:22.209 |     inet 10.2.144.147/15 brd 10.3.255.255 scope
> global eth0
> 2013-09-10 06:32:23.193 | Running devstack
> 2013-09-10 06:32:23.866 | Using mysql database backend
>
>
>
> In the latest version they have 2:
>
> 2013-10-03 11:33:54.298 | 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc
> noqueue state UNKNOWN
> 2013-10-03 11:33:54.299 |     inet 127.0.0.1/8 scope host lo
> 2013-10-03 11:33:54.300 | 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu
> 1500 qdisc pfifo_fast state UP qlen 1000
> 2013-10-03 11:33:54.301 |     inet 162.242.160.129/24 brd 162.242.160.255
> scope global eth0
> 2013-10-03 11:33:54.302 | 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu
> 1500 qdisc pfifo_fast state UP qlen 1000
> 2013-10-03 11:33:54.302 |     inet 10.208.24.83/17 brd 10.208.127.255
> scope global eth1
> 2013-10-03 11:33:57.539 | Running devstack
> 2013-10-03 11:33:58.780 | Using mysql database backend
>
>
>
> The problems occur when the when the the following line is invoked:
>
> https://github.com/openstack-dev/devstack/blob/stable/grizzly/lib/quantum#L
> 302
>
> Anyone able to clarify why an additional interface was added?
>
I think the extra interface is a result of using both HPCloud and
Rackspace VMs in the check pipeline tests. HPCloud VMs come with a
single interface with NAT in front of it, Rackspace VMs come with two
interfaces (an internal and external interface). It all depends on
where the test is being run.

Clark



More information about the OpenStack-dev mailing list