Comment 1 for bug 1808504

Hi, I am bit lost with your reproducer scenario, do these steps look OK:
openstack network create xxxtest
openstack subnet create --network xxxtest --subnet-range 192.168.10.0/24 --allocation-pool start=192.168.10.2,end=192.168.10.11 subnet1
openstack subnet create --network xxxtest --subnet-range 192.168.11.0/24 --allocation-pool start=192.168.11.2,end=192.168.11.2 subnet2

This creates a single port for DHCP with IPs in both subnets:
openstack port list --network xxxtest -f json
[
  {
    "Status": "ACTIVE",
    "Fixed IP Addresses": "ip_address='192.168.10.2', subnet_id='5b69c973-fcca-4e1a-ae84-7d154f5c0869'\nip_address='192.168.11.2', subnet_id='2d0bd114-d0b2-46d3-83ed-71592fbf1989'",
    "ID": "69939e7b-573c-47ee-8db9-83b70f2ecd96",
    "MAC Address": "fa:16:3e:3b:9c:53",
    "Name": ""
  }
]

It matches port 176b3f71-0e54-4df1-8928-b4e5b199ee1c in your example (which after delete also has only one IP left as expected)

This other port listed the bug is strange, it is DOWN, with IP outside of the subnet range (192.168.168.3 so not .10.x or .11.x)

What is your Openstack version and neutron configuration?