Why does DVR Floating IP not work with Murano?

asked 2017-12-07 09:09:01 -0500

mickt gravatar image

updated 2017-12-08 05:37:46 -0500

I have a murano issue when using DVR and Floating IP as outlined below. There is no issue when using murano with HA and Floating IP (same image and catalogue etc.). I also have no issue with DVR and Floating IP when not using Murano. I can also assign a floating IP post creation.

Murano Environment successfully deployed and instance created so I don't see anything in logs. I can console into instance and ping qrouter and qdhcp. The qrouter cannot ping instance (ip netns exec qrouter-6af97a81-f156-433f-bfe9-70ba1c352d2c ping 195.7.51.8), which I believe is correct as no route in table and qdhcp can ping instance as it has route. So all is good here.

When I include floating IP during creation however, the Floating IP is assigned to instance, which shows running and I can ping it from external source but the murano environment deployment appears to hang. I cannot ssh to the floating IP and the application task does not complete.

I've not managed to get to the bottom of it so if anyone has some ideas, it would be greatly appreciated. I'm using Pike.

.

Hosts

+------------+------------+

| Host       | Groups     |

+------------+------------+

| compute01  | [compute]  |

| compute07  | [compute]  |

| compute08  | [compute]  |

| compute09  | [compute]  |

| control01  | [control]  |

| control02  | [control]  |

| control03  | [control]  |

| database01 | [database] |

| database02 | [database] |

| network01  | [network]  |

| network02  | [network]  |

| storage01  | [storage]  |

| storage02  | [storage]  |

| storage03  | [storage]  |

+------------+------------+

ip netns

fip-83159071-ea14-46cf-a8bf-89b00e8eebae (id: 0)

qdhcp-ead6d583-12ed-409f-82c9-500179fbb22a

qdhcp-fe8cd55e-7314-4c11-9532-966b034c1bdb

qrouter-5922bf50-927f-4596-a30b-3ff50ae1f3c2

qrouter-6af97a81-f156-433f-bfe9-70ba1c352d2c

snat-6af97a81-f156-433f-bfe9-70ba1c352d2c

snat-5922bf50-927f-4596-a30b-3ff50ae1f3c2

ip netns exec qrouter-6af97a81-f156-433f-bfe9-70ba1c352d2c ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

       valid_lft forever preferred_lft forever

    inet6 ::1/128 scope host

       valid_lft forever preferred_lft forever

2: rfp-6af97a81-f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 2a:ff:f0:4b:f8:7c brd ff:ff:ff:ff:ff:ff link-netnsid 0

    inet 169.254.109.46/31 scope global rfp-6af97a81-f

       valid_lft forever preferred_lft forever
    inet6 fe80::28ff:f0ff:fe4b:f87c/64 scope link

       valid_lft forever preferred_lft forever

27: qr-e92f5636-25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN

    link/ether fa:16:3e:fe:b4:60 brd ff:ff:ff:ff:ff:ff

    inet 195.7.51.1/24 brd 195.7.51.255 scope global qr-e92f5636-25

       valid_lft forever preferred_lft forever

    inet6 fe80::f816:3eff:fefe:b460/64 scope link

       valid_lft forever preferred_lft forever

ip netns exec qrouter-6af97a81-f156-433f-bfe9-70ba1c352d2c route -n

Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

169.254.109.46  0.0.0.0         255.255.255.254 U     0      0        0 rfp-6af97a81-f

195.7.51.0      0.0.0.0         255.255.255.0   U     0      0        0 qr-e92f5636-25

ip netns exec qdhcp-ead6d583-12ed-409f-82c9-500179fbb22a ip a

 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

       valid_lft forever preferred_lft forever

    inet6 ...
(more)
edit retag flag offensive close merge delete