Thursday, 2024-04-18

opendevreviewMerged openstack/openstack-ansible-openstack_openrc unmaintained/victoria: Update .gitreview for unmaintained/victoria  https://review.opendev.org/c/openstack/openstack-ansible-openstack_openrc/+/91302207:38
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-tests unmaintained/victoria: Fix functional tests running locally  https://review.opendev.org/c/openstack/openstack-ansible-tests/+/91617409:02
opendevreviewJonathan Rosser proposed openstack/openstack-ansible unmaintained/victoria: DNM - testing unmaintained branch  https://review.opendev.org/c/openstack/openstack-ansible/+/91617509:09
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-os_tempest unmaintained/wallaby: Fix keystone-tempest-plugin to tag made for wallaby release  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/91627711:17
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-tests unmaintained/wallaby: Update .gitreview for unmaintained/wallaby  https://review.opendev.org/c/openstack/openstack-ansible-tests/+/91312711:18
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-tests unmaintained/wallaby: Update .gitreview for unmaintained/wallaby  https://review.opendev.org/c/openstack/openstack-ansible-tests/+/91312711:19
blues11I was testing OpenStack OVN and have an issues with network connectivity. The network connectivity works when floating IP address and a private IP address used at the same time. However it doesn't work when floating IP attaches to the VM directly 12:06
blues11This is for OpenStack ansible and here is my vlan config - https://paste.openstack.org/show/bdsSt1gunR4ScpML4fOg/12:07
blues11Any clue about this issue ?12:07
jrosser_blues11: are each of your compute nodes "ovn controllers" ?12:11
jrosser_the config in your paste is only applied to the `neutron_ovn_controller` ansible group12:12
blues11We have deployed like this network-gateway_hosts: *compute_hosts so all our hypervisor nodes are ovn controller nodes right?12:18
jrosser_and you've got bond0 on all the compute nodes as well?12:19
blues11Yes sure we can ping to outside with floating ip attached to vm but cannot connect flat network directly12:21
blues11https://paste.openstack.org/show/bDRxkLmyF9jFK0OHLm5R/ - Those nat setup works fine12:25
jrosser_you mean that it fails, or the port gets attached but no traffic flows?12:25
jrosser_(i must say that i've never used ovn myself) perhaps mgariepy might have some insights here12:27
blues11Can you see the test example 10.60.16.186 ip is directly atached to vm this is floating ip which is not working12:27
jrosser_sadly i'm not really understanding "However it doesn't work when floating IP attaches to the VM directly" becasue my understanding is that floating IP are dealt with by the neutron router12:28
mgariepyhey12:30
blues11Well thats not the case before with linux bridge we could do that, this is extremly helpfull to attach to vm for vrrp setup as well as whitelist ips in other env12:30
blues11Hi mgariepy 12:31
jrosser_i do wonder if there is confusion here with "attaching a floating IP to a VM directly" vs. "attachin the VM directly to the external network" which really are not the same thing12:33
mgariepycan you paste a bit more config and info on your network ?12:33
mgariepywhen you attach a fip to a vm it's natted via the router to the vms internal ip.12:34
mgariepylin the nat b5fac2ab-e4cb-4ba3-a9c7-1fc6b6fd395f in your last paste.12:35
blues11What we mean is attaching the VM directly to the external network not working12:35
mgariepyfip 10.60.16.183 is natted to 192.168.25.12912:35
blues11Yes that works fine (fip 10.60.16.183 is natted to 192.168.25.129)12:35
blues11port 7131019b-5107-4dd0-883d-c79eceef57c8         addresses: ["fa:16:3e:60:af:f7 10.60.16.186"] - This dosn't works 12:36
mgariepyyou expect to have this ip configured in the server i guess ?12:36
mgariepyvia a new interface AKA port.12:37
blues1110.60.16.186 we get this ip configured inside vm12:37
mgariepywhat are your routes?12:37
mgariepy`ip r`12:37
mgariepyinside the vm.12:38
mgariepydo you also have another ip inside that vm ?12:38
blues11default via 10.60.16.1 dev eth0  src 10.60.16.186  metric 100212:39
mgariepycan you ping the gw ?12:39
blues11We don't have any other IP in that VM12:39
blues11We are unable to do that thats the issue here12:40
mgariepywhat are the security rules applied to the vm ?12:43
blues11Thats same applied both vm icmp allowed 12:43
blues11I also tried with port security disabled 12:45
blues11We can see the tap interface showing in the hypervisor under ovs-system12:47
mgariepywhere does the gw live ?12:47
blues11gw is external l3 switch12:48
mgariepyhttps://access.redhat.com/solutions/406632112:48
mgariepycan you try the ovn-trace stuff from that page?12:48
blues11Sure, I will provide this later got little busy now. Thanks for your time mgariepy 12:51
opendevreviewJonathan Rosser proposed openstack/openstack-ansible unmaintained/wallaby: Update ansible role and openstack services for unmaintained branch names  https://review.opendev.org/c/openstack/openstack-ansible/+/91629112:55
mgariepyi do have both also but i don't mix the 2. my fip are on a network and i have another sperate network that i do attach directly to vms13:04
mgariepyi never tried to mix them tho.13:04
jrosser_if anyone has ideas about why only two jobs ran here i would be grateful https://review.opendev.org/c/openstack/openstack-ansible/+/91629114:14
jrosser_i excpected there to be quite a few more than that14:14
andrewbonneyThis looks quite sparse: https://github.com/openstack/openstack-ansible/blob/unmaintained/wallaby/zuul.d/project.yaml14:16
jrosser_ooooh i see whats going on /o\14:25
jrosser_i  still have a stable/wallaby locally14:25
jrosser_`git prune` is very useful in this situation14:26
opendevreviewJonathan Rosser proposed openstack/openstack-ansible unmaintained/wallaby: Update ansible role and openstack services for unmaintained branch names  https://review.opendev.org/c/openstack/openstack-ansible/+/91629114:28
opendevreviewJonathan Rosser proposed openstack/openstack-ansible unmaintained/wallaby: Return CI jobs after unmaintained branch renaming  https://review.opendev.org/c/openstack/openstack-ansible/+/91630214:28
opendevreviewJonathan Rosser proposed openstack/openstack-ansible unmaintained/wallaby: Update ansible role and openstack services for unmaintained branch names  https://review.opendev.org/c/openstack/openstack-ansible/+/91629114:55
opendevreviewJonathan Rosser proposed openstack/openstack-ansible unmaintained/wallaby: Return CI jobs after unmaintained branch renaming  https://review.opendev.org/c/openstack/openstack-ansible/+/91630214:55

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!