Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1619217

Summary: OSP13 - ODL with new external network - no route to floating ips
Product: Red Hat OpenStack Reporter: Noam Manos <nmanos>
Component: opendaylightAssignee: Mike Kolesnik <mkolesni>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Noam Manos <nmanos>
Severity: high Docs Contact:
Priority: unspecified    
Version: 13.0 (Queens)CC: aadam, jchhatba, mkolesni, nmanos, nyechiel, oblaut, tfreger
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-17 11:31:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
odl with external network - no route to fip of new vm none

Description Noam Manos 2018-08-20 11:20:08 UTC 
Created attachment 1477143 [details]
odl with external network - no route to fip of new vm

Description of problem:
On OSP13 (deployed on virt undercloud) with ODL, creating a new external network (flat) with a cirros VM, but its floating ip is not reachable.

Version-Release number of selected component (if applicable):
OSP13 puddle 2018-08-14.4

How reproducible:
Always

Steps to Reproduce:
1. Deploy OSP13 with ODL
2. create VM with fip on external flat network and ping it.

You can use this script to simulate scenario:
https://code.engineering.redhat.com/gerrit/#/c/145740/2/Scripts/create_multi_topology.sh

For example:
./create_multi_topology.sh -t mvi -i cirros35 -n 1 -v 1 -e flat -c YES

Actual results:
Pinging VM FIP - Destination Host Unreachable

Expected results:
VM should be reachable, and accessible with ssh -i my_key.pem cirros@VM_FIP
Comment 1 Noam Manos 2018-08-20 12:13:44 UTC 
sosreports from all nodes are available here: 

http://rhos-release.virt.bos.redhat.com/log/bz1619217
Comment 3 Janki 2018-08-29 07:47:06 UTC 
Noam, Can you please try again after adding IPv6 related security groups as well please. I see you have both IPv4 and IPv6 subnets on the same network.

openstack security group rule create <sg> --protocol tcp --dst-port 22:22 --remote-ip ::0/0 --ethertype IPv6

openstack security group rule create <sg> --protocol ipv6-icmp
Comment 4 Janki 2018-08-30 04:48:00 UTC 
I could not reproduce this in my setup. I used 

./create_multi_topology.sh -t mvi -i cirros35 -n 1 -v 1 -e flat -c YES

$ nova list
+--------------------------------------+-------------------+--------+------------+-------------+------------------------------------------------------------+
| ID                                   | Name              | Status | Task State | Power State | Networks                                                   |
+--------------------------------------+-------------------+--------+------------+-------------+------------------------------------------------------------+
| 2f201f85-9039-4d14-8a7b-c7ba5a99091e | cirros35_vm1_net1 | ACTIVE | -          | Running     | net_ipv64_1=2001::f816:3eff:febf:ce8, 10.0.1.7, 10.0.0.219 |
+--------------------------------------+-------------------+--------+------------+-------------+------------------------------------------------------------+
[00:44:39.573] (tester) [stack@undercloud-0 ~]$ ping 10.0.0.219
PING 10.0.0.219 (10.0.0.219) 56(84) bytes of data.
64 bytes from 10.0.0.219: icmp_seq=1 ttl=64 time=1.31 ms
64 bytes from 10.0.0.219: icmp_seq=2 ttl=64 time=0.965 ms
64 bytes from 10.0.0.219: icmp_seq=3 ttl=64 time=0.731 ms
64 bytes from 10.0.0.219: icmp_seq=4 ttl=64 time=0.817 ms
Comment 5 Mike Kolesnik 2018-09-17 11:31:12 UTC 
Seems from Comment #4 there's not enough info to reproduce the bug, please reopen if you face it again and can provide the requested information.