yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #92795
[Bug 2035230] [NEW] Port on creation is returned without the fixed_ips field populated
Public bug reported:
I ran into an issue with port creation when using the openstack-
terraform provider (which then uses Gophercloud) to access the Neutron
API..... https://github.com/terraform-provider-openstack/terraform-
provider-openstack/issues/1606
In short a port is created, but that port does not have the `fixed_ips` field populated.
This is the response to the create request:
```
{
"ports": [
{
"admin_state_up": true,
"allowed_address_pairs": [
{
"ip_address": "10.3.4.0/24",
"mac_address": "fa:16:3e:3a:58:ec"
}
],
"binding:vnic_type": "normal",
"created_at": "2023-08-23T10:06:12Z",
"description": "",
"device_id": "",
"device_owner": "",
"dns_assignment": [],
"dns_name": "",
"extra_dhcp_opts": [],
"fixed_ips": [],
"id": "9b37978b-ed53-41c2-983f-31570eb88259",
"mac_address": "fa:16:3e:3a:58:ec",
"name": "vpn",
"network_id": "f946cedc-94d1-4bde-a680-f59d615ad2e3",
"port_security_enabled": true,
"project_id": "REDACTED",
"revision_number": 1,
"security_groups": [
"87acb073-5123-4473-b33b-fc78f522c6b8"
],
"status": "DOWN",
"tags": [],
"tenant_id": "REDACTED",
"updated_at": "2023-08-23T10:06:12Z"
}
]
}
```
If you look at my attempt to dive into the mechanics at https://github.com/terraform-provider-openstack/terraform-provider-openstack/issues/1606#issuecomment-1692082094, I am wondering if the IPAllocation might happening asynchronously and thus the response to the API call might not contain the fixed_ips if that takes to long?
All in all I just kindly as for a qualified comment if this is expected
behavior (needs handing within the terraform provider) or a bug (can be
fixed on the Neutron side).
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2035230
Title:
Port on creation is returned without the fixed_ips field populated
Status in neutron:
New
Bug description:
I ran into an issue with port creation when using the openstack-
terraform provider (which then uses Gophercloud) to access the Neutron
API..... https://github.com/terraform-provider-openstack/terraform-
provider-openstack/issues/1606
In short a port is created, but that port does not have the `fixed_ips` field populated.
This is the response to the create request:
```
{
"ports": [
{
"admin_state_up": true,
"allowed_address_pairs": [
{
"ip_address": "10.3.4.0/24",
"mac_address": "fa:16:3e:3a:58:ec"
}
],
"binding:vnic_type": "normal",
"created_at": "2023-08-23T10:06:12Z",
"description": "",
"device_id": "",
"device_owner": "",
"dns_assignment": [],
"dns_name": "",
"extra_dhcp_opts": [],
"fixed_ips": [],
"id": "9b37978b-ed53-41c2-983f-31570eb88259",
"mac_address": "fa:16:3e:3a:58:ec",
"name": "vpn",
"network_id": "f946cedc-94d1-4bde-a680-f59d615ad2e3",
"port_security_enabled": true,
"project_id": "REDACTED",
"revision_number": 1,
"security_groups": [
"87acb073-5123-4473-b33b-fc78f522c6b8"
],
"status": "DOWN",
"tags": [],
"tenant_id": "REDACTED",
"updated_at": "2023-08-23T10:06:12Z"
}
]
}
```
If you look at my attempt to dive into the mechanics at https://github.com/terraform-provider-openstack/terraform-provider-openstack/issues/1606#issuecomment-1692082094, I am wondering if the IPAllocation might happening asynchronously and thus the response to the API call might not contain the fixed_ips if that takes to long?
All in all I just kindly as for a qualified comment if this is
expected behavior (needs handing within the terraform provider) or a
bug (can be fixed on the Neutron side).
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2035230/+subscriptions
Follow ups