| opendevreview | yatin proposed openstack/neutron master: [OVN] Remove backwards compatibility with OVN < v20.09 ver 2 https://review.opendev.org/c/openstack/neutron/+/904238 | 05:42 |
|---|---|---|
| ralonsoh | slaweq, hello! If you have 1 min: https://review.opendev.org/c/openstack/neutron/+/903707 | 07:05 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/2023.1: Improve the SG RPC callback ``security_group_info_for_ports`` https://review.opendev.org/c/openstack/neutron/+/904243 | 07:06 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/2023.2: Improve the SG RPC callback ``security_group_info_for_ports`` https://review.opendev.org/c/openstack/neutron/+/904244 | 07:07 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/zed: Improve the SG RPC callback ``security_group_info_for_ports`` https://review.opendev.org/c/openstack/neutron/+/904245 | 07:07 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/yoga: Improve the SG RPC callback ``security_group_info_for_ports`` https://review.opendev.org/c/openstack/neutron/+/904246 | 07:07 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/xena: Improve the SG RPC callback ``security_group_info_for_ports`` https://review.opendev.org/c/openstack/neutron/+/904247 | 07:07 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/wallaby: Improve the SG RPC callback ``security_group_info_for_ports`` https://review.opendev.org/c/openstack/neutron/+/904248 | 07:08 |
| opendevreview | Merged openstack/neutron master: [OVN] Retrieve the OVN agent extensions correctly https://review.opendev.org/c/openstack/neutron/+/903929 | 07:12 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/2023.2: [UT] OVN fake resources factory method should return instance https://review.opendev.org/c/openstack/neutron/+/904251 | 09:45 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/2023.2: [OVN] Add the bridge name and datapath type to the port VIF details https://review.opendev.org/c/openstack/neutron/+/904252 | 09:45 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/2023.1: [UT] OVN fake resources factory method should return instance https://review.opendev.org/c/openstack/neutron/+/904253 | 09:46 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/2023.1: [OVN] Add the bridge name and datapath type to the port VIF details https://review.opendev.org/c/openstack/neutron/+/904254 | 09:52 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/yoga: Improve the SG RPC callback ``security_group_info_for_ports`` https://review.opendev.org/c/openstack/neutron/+/904246 | 09:54 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/xena: Improve the SG RPC callback ``security_group_info_for_ports`` https://review.opendev.org/c/openstack/neutron/+/904247 | 09:56 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/wallaby: Improve the SG RPC callback ``security_group_info_for_ports`` https://review.opendev.org/c/openstack/neutron/+/904248 | 09:56 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron master: [OVN] "description" property missing in ``NeutronAgent`` https://review.opendev.org/c/openstack/neutron/+/904257 | 10:11 |
| amorin | hello neutron team | 11:21 |
| amorin | one question regarding neutron segments: I deployed a bobcat release, created a public/external/shared network and created two segments in it. It seems, enabling segments, break the possibility to create a floating IP: | 11:22 |
| amorin | Error while executing command: BadRequestException: 400, Unable to find any IP address on external network 2813f459-a20d-4e50-8193-fe3c639e1ab6. | 11:23 |
| amorin | taking a look at code lead me to this: https://github.com/openstack/neutron/blob/master/neutron/db/l3_db.py#L1531 | 11:23 |
| amorin | segments is deferring the IP allocation from what I understand, so FIP cannot be created | 11:24 |
| amorin | am I hitting a bug or is it expected in your opinion? | 11:24 |
| amorin | maybe sahid would know that? IIRC you were using segments in your deployments | 11:26 |
| ralonsoh | amorin, and how many subnets do you have in the ext network? | 11:45 |
| ralonsoh | what backend? | 11:45 |
| opendevreview | Merged openstack/neutron stable/2023.2: Make unit tests compatible with neutron-lib 3.8.1 https://review.opendev.org/c/openstack/neutron/+/904109 | 11:55 |
| amorin | ralonsoh: i have 2 subnets so far, ovs backend | 11:59 |
| amorin | Is the backend important for that api call? | 11:59 |
| ralonsoh | shouldn't be, but just to retrieve more info | 12:00 |
| ralonsoh | can you print the external_port info before this exception? | 12:01 |
| ralonsoh | you should check what IP addresses received during the creation | 12:01 |
| ralonsoh | and to what subnet are assigned | 12:02 |
| opendevreview | Merged openstack/neutron stable/2023.1: Make unit tests compatible with neutron-lib 3.4.2 https://review.opendev.org/c/openstack/neutron/+/904110 | 12:05 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron master: WIP == DNM == [OVN] Implement OVN agent metadata extension https://review.opendev.org/c/openstack/neutron/+/898238 | 12:07 |
| amorin | I printed it and the fixed_ips is empty array. | 12:16 |
| amorin | I remember something about deffered allocation when using segments | 12:16 |
| amorin | Maybe that would explain ? | 12:17 |
| amorin | I am not at computer now so can't print it, should be in 30 min | 12:17 |
| ralonsoh | amorin, so first thing is to identify why the previous operation (create port), provided this output. In any case, you should at least have some ipam allocations for this port | 12:18 |
| ralonsoh | so in between the exception and the port creation, check the BD | 12:18 |
| ralonsoh | DB* | 12:18 |
| amorin | I did openstack floating ip create | 12:19 |
| amorin | Not create port | 12:19 |
| amorin | If I do that against a public network without segments, it works | 12:19 |
| opendevreview | Fernando Royo proposed openstack/ovn-octavia-provider master: Allow LB members to mix IPv4 and IPv6 for the multivip LB https://review.opendev.org/c/openstack/ovn-octavia-provider/+/904152 | 12:19 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/2023.1: [OVN] Add the bridge name and datapath type to the port VIF details https://review.opendev.org/c/openstack/neutron/+/904254 | 12:23 |
| ralonsoh | amorin, this FIP creation command creates a port | 12:23 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/2023.1: [OVN] Add the bridge name and datapath type to the port VIF details https://review.opendev.org/c/openstack/neutron/+/904254 | 12:31 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron master: WIP == DNM == [OVN] Implement OVN agent metadata extension https://review.opendev.org/c/openstack/neutron/+/898238 | 12:33 |
| amorin | ack, back on PC, let me show you the port | 12:34 |
| amorin | ralonsoh: https://paste.opendev.org/show/bfRDfPLBEDJPA9f1I0lS/ | 12:34 |
| amorin | more I think about, more I think it's expected, how can we create a FIP without knowing in which segment it should be used | 12:36 |
| ralonsoh | no idea. Segments where created to be used along with router provider networks | 12:37 |
| ralonsoh | in this configuration, the L3 stuff is leveraged by the underlaying network system | 12:38 |
| ralonsoh | not openstack | 12:38 |
| ralonsoh | so no idea how to mix multiple segments and FIPs | 12:38 |
| amorin | I think it's not possible/supported | 12:38 |
| amorin | I was thinking that maybe I could use segments to map to nova AZ but that's not going to fit it seems | 12:39 |
| ralonsoh | as commented, when using multiple segments (with routed provided networks https://docs.openstack.org/neutron/latest/contributor/internals/segments.html), the L3 work is not managed by neutron | 12:39 |
| ykarel | amorin, wondering if you using config described in https://docs.openstack.org/neutron/latest/admin/config-bgp-floating-ip-over-l2-segmented-network.html and still hitting issue with FIPs? | 12:59 |
| amorin | hum, I am not using bgp agent, but there is something interesting about --service-type 'network:floatingip_agent_gateway' on subnets in that page | 13:01 |
| amorin | based on what is in that doc, I may be able to created a specific subnet with serice_type for routers/fip and it may work, right? | 13:02 |
| amorin | yeah, that worked! | 13:07 |
| ykarel | ok | 13:30 |
| opendevreview | Merged openstack/neutron stable/2023.2: [OVN] DB sync host/physnet - filter on agent_type https://review.opendev.org/c/openstack/neutron/+/903682 | 13:36 |
| opendevreview | Merged openstack/neutron stable/2023.1: [OVN] DB sync host/physnet - filter on agent_type https://review.opendev.org/c/openstack/neutron/+/903683 | 13:40 |
| opendevreview | Merged openstack/ovn-octavia-provider master: Allow LB members to mix IPv4 and IPv6 for the multivip LB https://review.opendev.org/c/openstack/ovn-octavia-provider/+/904152 | 15:13 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron master: WIP == DNM == [OVN] Implement OVN agent metadata extension https://review.opendev.org/c/openstack/neutron/+/898238 | 15:57 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!