Openstack network failure

solved
openstack

#1

Hello folks,

I lifted my servers from 1 DC, drove down the road, plugged them all back in and wired them back up to exactly the same ports on the switch. Having switched everything back on, the VM’s load but the neutron layer refuses to work. I can ping myself from the qrouter, but it refuses to see any of the instances… except on some random reboots where like 1 host will have connectivity and no others…

As you can see here, I can ping my own router, I can ping an instance on 1 host, but not the other two, even thought they’re 3 identical openstack hosts. But if I rebooted the hosts, I might be able to ping an instance on another host, but not that one.

I should also mention they can’t get an IP either… so its not surprising.

Starting Initial cloud-init job (metadata service crawler)...
[  129.721461] cloud-init[834]: Cloud-init v. 19.1-1-gbaa47854-0ubuntu1~18.04.1 running 'init' at Wed, 30 Oct 2019 16:08:20 +0000. Up 129.52 seconds.
[  129.727258] cloud-init[834]: ci-info: ++++++++++++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++++++++++++
[  129.731718] cloud-init[834]: ci-info: +--------+------+------------------------------+-----------+-------+-------------------+
[  129.735721] cloud-init[834]: ci-info: | Device |  Up  |           Address            |    Mask   | Scope |     Hw-Address    |
[  129.739811] cloud-init[834]: ci-info: +--------+------+------------------------------+-----------+-------+-------------------+
[  129.745120] cloud-init[834]: ci-info: |  ens2  | True | fe80::f816:3eff:fead:843d/64 |     .     |  link | fa:16:3e:ad:84:3d |
[  129.749791] cloud-init[834]: ci-info: |   lo   | True |          127.0.0.1           | 255.0.0.0 |  host |         .         |
[  129.753859] cloud-init[834]: ci-info: |   lo   | True |           ::1/128            |     .     |  host |         .         |
[  129.757243] cloud-init[834]: ci-info: +--------+------+------------------------------+-----------+-------+-------------------+
[  129.761634] cloud-init[834]: ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++
[  129.765779] cloud-init[834]: ci-info: +-------+-------------+---------+-----------+-------+
[  129.769067] cloud-init[834]: ci-info: | Route | Destination | Gateway | Interface | Flags |
[  129.772396] cloud-init[834]: ci-info: +-------+-------------+---------+-----------+-------+
[  129.775558] cloud-init[834]: ci-info: |   1   |  fe80::/64  |    ::   |    ens2   |   U   |
[  129.778293] cloud-init[834]: ci-info: |   3   |    local    |    ::   |    ens2   |   U   |
[  129.781348] cloud-init[834]: ci-info: |   4   |   ff00::/8  |    ::   |    ens2   |   U   |
[  129.784044] cloud-init[834]: ci-info: +-------+-------------+---------+-----------+-------+

Well… it seems to get an ipv6 one, but thats no use to me!


#2

Okay cancel that. Having spent 2 days trying to figure it out… in horizon I renamed my internal network internal1 and magically I can ping everything… :rage:

problem solved


#3

bummer on the issue but glad you got it sorted