| lotyrin | That's not it because I just forced a VM to be created on each node connected to the "lb-mgmt-net" and it didn't cause the bridges to be created on the nodes where they are missing | 00:07 |
|---|---|---|
| lotyrin | Or maybe it was because now they are all there... | 00:19 |
| lotyrin | And octavia-interface.service is up on all nodes now, very curious | 00:22 |
| lotyrin | Thanks for the help mloza | 00:26 |
| *** queria is now known as Guest2162 | 02:25 | |
| *** queria is now known as Guest2163 | 02:31 | |
| nconcetti | i am having some trouble making floating ip's work. anyone willing to give me a hint? all machines (3x controller, 2x hypervisor) are bare-metal, each has 4 nic interfaces connected to separate networks (no VLAN). iface1 has wan connectivity (64 ip's) via a switch. there is no dhcp present, so everything static. i created an external network reflecting the wan network, added a host-route like | 09:24 |
| nconcetti | 0.0.0.0/0,<ip of the gateway> and created a vxlan network. Both are connected with a router, as described in the tutorials. That works flawlessly, i can reach the network from within a VM, but when assigning a floating ip which is in the public wan range, packets don't reach my vm's. My Question is, do i need to forwards packets via a 1:1 NAT or can neutron advertise floating-ip's via ARP? | 09:24 |
| nconcetti | if it does, i need a hint at where to look. Maybe a security policy? | 09:25 |
| frickler | nconcetti: security groups might be an issue. outgoing traffic froma vm is allowed by default, but you need to create rules if you want to allow anything to go into your vm | 09:32 |
| *** rlandy is now known as rlandy|ruck | 10:33 | |
| nconcetti | frickler: thank you! that helps me very much. i always thought floating IP's are something like a 1:1 NAT equivalent. Didn't think about that | 11:05 |
| *** sshnaidm is now known as sshnaidm|afk | 12:17 | |
| weezel | hello everyone, can someone help with any kind of hints on the following problem? | 13:36 |
| weezel | detaching volumes from an running openstack instance fails with the following error: except nova.exception.DeviceDetachFailed: Device detach failed for vdb: Run out of retry while detaching device vdb with device alias virtio-disk1 from instance ebc55b0c-3c | 13:36 |
| weezel | i've tried to debug it but without any success... i'm using wallaby deployed with kolla-ansible | 13:36 |
| *** onelegend is now known as Guest2260 | 23:01 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!