Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Packstack: Route to external network disappeared after rebooting controller

On my Newton-based Packstack (all-in-one controller plus two compute nodes), the controller has this route:

$ ip r
...
172.24.4.224/28 dev br-ex  proto kernel  scope link  src 172.24.4.225

All is fine there.

I also deployed an Ocata-based Packstack. After rebooting the controller, I can't access instances through their floating IPs anymore, and indeed, there is no route to 172.24.4.xxx.

I can't confirm that this route existed before, but I see traces in the deployment log file /var/tmp/packstack/latest/openstack-setup.log:

# grep openstack-setup.log
...
ipaddress => 172.24.4.1
ipaddress_br_ex => 172.24.4.1
network_br_ex => 172.24.4.0
2017-03-07 15:40:12::DEBUG::run_setup::626::root:: provision-demo-floatrange: 172.24.4.0/24

My networking skills are not sufficient to figure out where this route disappeared. Any idea where to look?

Packstack: Route to external network disappeared after rebooting controller

On my Newton-based Packstack (all-in-one controller plus two compute nodes), the controller has this route:

$ ip r
...
172.24.4.224/28 dev br-ex  proto kernel  scope link  src 172.24.4.225

All is fine there.

I also deployed an Ocata-based Packstack. After rebooting the controller, I can't access instances through their floating IPs anymore, and indeed, there is no route to 172.24.4.xxx.

I can't confirm that this route existed before, but I see traces in the deployment log file /var/tmp/packstack/latest/openstack-setup.log:

# grep openstack-setup.log
...
ipaddress => 172.24.4.1
ipaddress_br_ex => 172.24.4.1
network_br_ex => 172.24.4.0
2017-03-07 15:40:12::DEBUG::run_setup::626::root:: provision-demo-floatrange: 172.24.4.0/24

My networking skills are not sufficient to figure out where this route disappeared. Any idea where to look?

EDIT: I provisioned a new Packstack controller. Routing table:

$ ip r
default via 192.168.1.1 dev eth0
10.0.0.0/24 dev eth1  proto kernel  scope link  src 10.0.0.211
169.254.0.0/16 dev eth0  scope link  metric 1002
169.254.0.0/16 dev eth1  scope link  metric 1003
172.24.4.0/24 dev br-ex  proto kernel  scope link  src 172.24.4.1
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.211

(I don't really need eth1)

After rebooting, the 172 route has disappeared:

$ ip r
default via 192.168.1.1 dev eth0
10.0.0.0/24 dev eth1  proto kernel  scope link  src 10.0.0.211
169.254.0.0/16 dev eth0  scope link  metric 1002
169.254.0.0/16 dev eth1  scope link  metric 1003
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.211

So it would seem that Packstack is not that robust after all. At least the Ocata version.

Packstack: Route to external network disappeared after rebooting controller

On my Newton-based Packstack (all-in-one controller plus two compute nodes), the controller has this route:

$ ip r
...
172.24.4.224/28 dev br-ex  proto kernel  scope link  src 172.24.4.225

All is fine there.

I also deployed an Ocata-based Packstack. After rebooting the controller, I can't access instances through their floating IPs anymore, and indeed, there is no route to 172.24.4.xxx.

I can't confirm that this route existed before, but I see traces in the deployment log file /var/tmp/packstack/latest/openstack-setup.log:

# grep openstack-setup.log
...
ipaddress => 172.24.4.1
ipaddress_br_ex => 172.24.4.1
network_br_ex => 172.24.4.0
2017-03-07 15:40:12::DEBUG::run_setup::626::root:: provision-demo-floatrange: 172.24.4.0/24

My networking skills are not sufficient to figure out where this route disappeared. Any idea where to look?

EDIT: I provisioned a new Packstack controller.

This time, I removed the superfluous eth1 from the controller. Routing table:

$ ip r
default via 192.168.1.1 dev eth0
10.0.0.0/24 dev eth1  proto kernel  scope link  src 10.0.0.211
169.254.0.0/16 dev eth0  scope link  metric 1002
169.254.0.0/16 dev eth1  scope link  metric 1003
Packstack provisioned like this:

sudo packstack -d --default-password=bla --allinone

As recommended on the quickstart page, firewalld and NW manager disabled, network service enabled. Directly after installation, I have no ifcfg-br-ex, but this route exists:

172.24.4.0/24 dev br-ex  proto kernel  scope link  src 172.24.4.1
192.168.1.0/24 dev eth0  proto kernel  

And:

4: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000
    link/ether 5a:9d:96:0b:ed:48 brd ff:ff:ff:ff:ff:ff
    inet 172.24.4.1/24 scope link  src 192.168.1.211

(I don't really need eth1)

global br-ex valid_lft forever preferred_lft forever

After rebooting, the 172 route has disappeared:

$ ip r
default no route to 172, and:

9: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 5a:9d:96:0b:ed:48 brd ff:ff:ff:ff:ff:ff

After setting br-ex up and adding the IP address manually, I can access my instance via 192.168.1.1 dev eth0 10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.211 169.254.0.0/16 dev eth0 scope link metric 1002 169.254.0.0/16 dev eth1 scope link metric 1003 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.211

floating IP. So it would seem that I do have a good workaround, but somewhere in Packstack the setup of br-ex is not that robust after all. At least the Ocata version.quite watertight.

Packstack: Route to external network disappeared after rebooting controller

On my Newton-based Packstack (all-in-one controller plus two compute nodes), the controller has this route:

$ ip r
...
172.24.4.224/28 dev br-ex  proto kernel  scope link  src 172.24.4.225

All is fine there.

I also deployed an Ocata-based Packstack. After rebooting the controller, I can't access instances through their floating IPs anymore, and indeed, there is no route to 172.24.4.xxx.

I can't confirm that this route existed before, but I see traces in the deployment log file /var/tmp/packstack/latest/openstack-setup.log:

# grep openstack-setup.log
...
ipaddress => 172.24.4.1
ipaddress_br_ex => 172.24.4.1
network_br_ex => 172.24.4.0
2017-03-07 15:40:12::DEBUG::run_setup::626::root:: provision-demo-floatrange: 172.24.4.0/24

My networking skills are not sufficient to figure out where this route disappeared. Any idea where to look?

EDIT: I provisioned a new Packstack controller.

This time, I removed the superfluous eth1 from the controller. Packstack provisioned like this:

sudo packstack -d --default-password=bla --allinone

As recommended on the quickstart page, firewalld and NW manager disabled, network service enabled. Packstack provisioned like this:

sudo packstack -d --default-password=bla --allinone

Directly after installation, I have no ifcfg-br-ex, but this route exists:

172.24.4.0/24 dev br-ex  proto kernel  scope link  src 172.24.4.1

And:

4: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000
    link/ether 5a:9d:96:0b:ed:48 brd ff:ff:ff:ff:ff:ff
    inet 172.24.4.1/24 scope global br-ex
       valid_lft forever preferred_lft forever

After rebooting, no route to 172, and:

9: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 5a:9d:96:0b:ed:48 brd ff:ff:ff:ff:ff:ff

After setting br-ex up and adding the IP address manually, I can access my instance via floating IP. So I do have a good workaround, but somewhere in Packstack the setup of br-ex is not quite watertight.

Packstack: Route to external network disappeared after rebooting controller

On my Newton-based Packstack (all-in-one controller plus two compute nodes), the controller has this route:

$ ip r
...
172.24.4.224/28 dev br-ex  proto kernel  scope link  src 172.24.4.225

All is fine there.

I also deployed an Ocata-based Packstack. After rebooting the controller, I can't access instances through their floating IPs anymore, and indeed, there is no route to 172.24.4.xxx.

I can't confirm that this route existed before, but I see traces in the deployment log file /var/tmp/packstack/latest/openstack-setup.log:

# grep openstack-setup.log
...
ipaddress => 172.24.4.1
ipaddress_br_ex => 172.24.4.1
network_br_ex => 172.24.4.0
2017-03-07 15:40:12::DEBUG::run_setup::626::root:: provision-demo-floatrange: 172.24.4.0/24

My networking skills are not sufficient to figure out where this route disappeared. Any idea where to look?

EDIT: I provisioned a new Packstack controller.

This time, I removed the superfluous eth1 from the controller. As recommended on the quickstart page, firewalld and NW manager disabled, network service enabled. Packstack provisioned like this:

sudo packstack -d --default-password=bla --allinone

Directly after installation, I have no ifcfg-br-ex, but this route exists:

172.24.4.0/24 dev br-ex  proto kernel  scope link  src 172.24.4.1

And:

4: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000
    link/ether 5a:9d:96:0b:ed:48 brd ff:ff:ff:ff:ff:ff
    inet 172.24.4.1/24 scope global br-ex
       valid_lft forever preferred_lft forever

After rebooting, no route to 172, and:

9: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 5a:9d:96:0b:ed:48 brd ff:ff:ff:ff:ff:ff

After setting ip link set br-ex up and adding the IP address manually, I can access my instance via floating IP. So I do have a good workaround, but somewhere in Packstack the setup of br-ex is not quite watertight.

Packstack: Route to external network disappeared after rebooting controller

On my Newton-based Packstack (all-in-one controller plus two compute nodes), the controller has this route:

$ ip r
...
172.24.4.224/28 dev br-ex  proto kernel  scope link  src 172.24.4.225

All is fine there.

I also deployed an Ocata-based Packstack. After rebooting the controller, I can't access instances through their floating IPs anymore, and indeed, there is no route to 172.24.4.xxx.

I can't confirm that this route existed before, but I see traces in the deployment log file /var/tmp/packstack/latest/openstack-setup.log:

# grep openstack-setup.log
...
ipaddress => 172.24.4.1
ipaddress_br_ex => 172.24.4.1
network_br_ex => 172.24.4.0
2017-03-07 15:40:12::DEBUG::run_setup::626::root:: provision-demo-floatrange: 172.24.4.0/24

My networking skills are not sufficient to figure out where this route disappeared. Any idea where to look?

EDIT: I provisioned a new Packstack controller.

This time, I removed the superfluous eth1 from the controller. As recommended on the quickstart page, firewalld and NW manager disabled, network service enabled. Packstack provisioned like this:

sudo packstack -d --default-password=bla --allinone

Directly after installation, I have no ifcfg-br-ex, but this route exists:

172.24.4.0/24 dev br-ex  proto kernel  scope link  src 172.24.4.1

And:

4: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000
    link/ether 5a:9d:96:0b:ed:48 brd ff:ff:ff:ff:ff:ff
    inet 172.24.4.1/24 scope global br-ex
       valid_lft forever preferred_lft forever

After rebooting, no route to 172, and:

9: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 5a:9d:96:0b:ed:48 brd ff:ff:ff:ff:ff:ff

After ip link set br-ex up up and adding the IP address manually, I can access my instance via floating IP. So I do have a good workaround, but somewhere in Packstack the setup of br-ex is not quite watertight.

Packstack: Route to external network disappeared after rebooting controller

On my Newton-based Packstack (all-in-one controller plus two compute nodes), the controller has this route:

$ ip r
...
172.24.4.224/28 dev br-ex  proto kernel  scope link  src 172.24.4.225

All is fine there.

I also deployed an Ocata-based Packstack. After rebooting the controller, I can't access instances through their floating IPs anymore, and indeed, there is no route to 172.24.4.xxx.

I can't confirm that this route existed before, but I see traces in the deployment log file /var/tmp/packstack/latest/openstack-setup.log:

# grep openstack-setup.log
...
ipaddress => 172.24.4.1
ipaddress_br_ex => 172.24.4.1
network_br_ex => 172.24.4.0
2017-03-07 15:40:12::DEBUG::run_setup::626::root:: provision-demo-floatrange: 172.24.4.0/24

My networking skills are not sufficient to figure out where this route disappeared. Any idea where to look?

EDIT: I provisioned a new Packstack controller.

This time, I removed the superfluous eth1 from the controller. As recommended on the quickstart page, firewalld and NW manager disabled, network service enabled. Packstack provisioned like this:

sudo packstack -d --default-password=bla --allinone

Directly after installation, I have no ifcfg-br-ex, but this route exists:

172.24.4.0/24 dev br-ex  proto kernel  scope link  src 172.24.4.1

And:

4: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000
    link/ether 5a:9d:96:0b:ed:48 brd ff:ff:ff:ff:ff:ff
    inet 172.24.4.1/24 scope global br-ex
       valid_lft forever preferred_lft forever

After rebooting, no route to 172, and:

9: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 5a:9d:96:0b:ed:48 brd ff:ff:ff:ff:ff:ff

After ip link set br-ex up and adding the IP address manually, I can access my instance via floating IP. So I do have a good workaround, but somewhere in Packstack the setup of br-ex is not quite watertight.

I submitted a bug description.