yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #84366
[Bug 1903342] Re: Neutron – port creation should fail when used network has no subnet associated
This is still invalid, there are good reasons to create a port without a
fixed_ip. You might want to discuss with nova whether they want to make
step 4 invalid, but step 2 is correct and should not be changed.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1903342
Title:
Neutron – port creation should fail when used network has no subnet
associated
Status in neutron:
Invalid
Bug description:
### Scenario ###
1) openstack network create net_a
2) port create --network net_a port_a
### Actual Result ###
Port is successfully created:
(openstack) port show port_a -f json
{
"admin_state_up": true,
"allowed_address_pairs": [],
"binding_host_id": "",
"binding_profile": {},
"binding_vif_details": {},
"binding_vif_type": "unbound",
"binding_vnic_type": "normal",
"created_at": "2020-11-05T15:21:22Z",
"data_plane_status": null,
"description": "",
"device_id": "",
"device_owner": "",
"dns_assignment": [],
"dns_domain": null,
"dns_name": "",
"extra_dhcp_opts": [],
"fixed_ips": [],
"id": "65753162-f5ce-4b19-9b63-c1756cc31c4a",
"location": {
"cloud": "",
"region_name": "regionOne",
"zone": null,
"project": {
"id": "4bda515a91d143c5a62863cb87b6ec81",
"name": "admin",
"domain_id": null,
"domain_name": "Default"
}
},
"mac_address": "fa:16:3e:16:a0:a7",
"name": "port_a",
"network_id": "ab0c613f-fcbf-41c4-8366-a7d0d32d6583",
"port_security_enabled": true,
"project_id": "4bda515a91d143c5a62863cb87b6ec81",
"propagate_uplink_status": null,
"qos_policy_id": null,
"resource_request": null,
"revision_number": 1,
"security_group_ids": [
"f711e6d6-7998-4864-ae1b-0998c0ea068a"
],
"status": "DOWN",
"tags": [],
"trunk_details": null,
"updated_at": "2020-11-05T15:21:22Z"
}
### Expected Result ###
Port creation should fail with appropriate Error/Warning message.
The reason for that is that when such a port is used to create the VM, created VM will be created without "ip_address" and this is a problem.
Openstack administrator should'n do that (creating port before subnet), but they can as nothing prevents them to do so.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1903342/+subscriptions