| opendevreview | Michael Johnson proposed openstack/octavia master: DNM: Testing apparmor issue with rsyslog https://review.opendev.org/c/openstack/octavia/+/955495 | 00:15 |
|---|---|---|
| opendevreview | Michael Johnson proposed openstack/octavia master: DNM: Testing apparmor issue with rsyslog https://review.opendev.org/c/openstack/octavia/+/955495 | 04:06 |
| opendevreview | Michael Johnson proposed openstack/octavia master: DNM: Testing apparmor issue with rsyslog https://review.opendev.org/c/openstack/octavia/+/955495 | 04:11 |
| opendevreview | Michael Johnson proposed openstack/octavia master: DNM: Testing apparmor issue with rsyslog https://review.opendev.org/c/openstack/octavia/+/955495 | 06:08 |
| opendevreview | Michael Johnson proposed openstack/octavia master: DNM: Testing apparmor issue with rsyslog https://review.opendev.org/c/openstack/octavia/+/955495 | 17:05 |
| manumoh | Hey .. is there any problem in having multiple subnet in lb-mgmt-net network | 18:41 |
| manumoh | I have 2 subnets under lb-mgmt-net , I noticed that amphora getting more than on ip from lb-mgmt-net , one form each subnet | 18:43 |
| johnsom | Yeah, so that setting is an odd setup that one vendor wanted. | 19:57 |
| johnsom | There is no issue with having more than one lb-mgmt-net, all of the traffic there is routable. | 19:57 |
| johnsom | The issue is that configuration setting for multiple subnets, attaches them all as that one company needed. | 19:58 |
| johnsom | It defeats the purpose in my mind | 19:58 |
| johnsom | Ideally we would choose one from the list and if it's full try another one. At least that is how I would have done it. | 19:59 |
| opendevreview | Michael Johnson proposed openstack/octavia master: DNM: Testing apparmor issue with rsyslog https://review.opendev.org/c/openstack/octavia/+/955495 | 20:14 |
| manumoh | johnsom: But octavia will make a server create call with the network id right or does it perform something in addition ? | 20:23 |
| johnsom | manumoh I am talking about this setting: https://github.com/openstack/octavia/blob/master/octavia/common/config.py#L464 | 20:25 |
| johnsom | Oh, right, sorry I mis-read your question. Yes, by default nova will attach all subnets on each lb-mgmt-net specified in the above config | 20:27 |
| johnsom | Which isn't great either | 20:27 |
| manumoh | https://www.irccloud.com/pastebin/jOIB2KoO/ | 20:29 |
| manumoh | is there something we can do to avoid this | 20:31 |
| manumoh | I need only 1 ip assigned to the port | 20:31 |
| johnsom | At the moment, since this is the default behavior of nova (to allocate IPs on all subnets of a network), the only option is to have one subnet on the lb-mgmt-net | 20:42 |
| manumoh | is this applicable only to lb-mgmt-net? never seen nova creating port like this when a network has multiple subnets in it | 20:45 |
| manumoh | the server create API response clearly shows only single ip got assigned "addresses": {"octavia-mgmt-net": [{"version": 4, "addr": "192.168.13.22", "OS-EXT-IPS:type": "fixed", "OS-EXT-IPS-MAC:mac_addr": "*******}]} | 21:05 |
| manumoh | 2025-07-22 20:00:24.541 182180 DEBUG novaclient.v2.client [-] RESP BODY: {"interfaceAttachments": [{"net_id": "3a201ef5-ec17-45d2-9363-ffc0109163be", "port_id": "d106a19c-2758-4386-b2af-b2fa4a4dbcb9", "mac_addr": "******", "port_state": "ACTIVE", "fixed_ips": [{"subnet_id": "83c68154-1209-4853-9988-b7259722922a", "ip_address": "192.168.13.22"}]}]} | 21:06 |
| johnsom | It always happens in nova if you pass in a network on server create. Wait until it is fully online and do a server show. You must pass in a network ID on instance create. | 21:07 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!