Regenerate mac address of a port
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Wishlist
|
Harald Jensås |
Bug Description
Openstack Ironic need to set the mac address of neutron port to the actual mac address of the hardware for DHCP/PXE deployment to work. When using pre-created neutron ports there is an issue where previously used ports cause a conflict when a new instance is scheduled onto the same baremetal hosts.
Example:
openstack port create --network private test-port1
openstack port create --network private test-port2
openstack server create \
--image cirros-
--port test-port1\
--flavor baremetal \
test-server
openstack server delete test-server
openstack server create \
--image cirros-
--port test-port2 \
--flavor baremetal \
test-server
The second server create command fails with:
fault:
code: 500
created: '2018-04-
< .. snip .. >
message: 'Build of instance 5982f29a-
prepping block device.'
An in conductor log:
Apr 29 14:21:35 ironic-
It should be possible to "return" the port by resetting a mac in the base MAC address Neutron uses for VIFs. e.g a port update request that triggers regeneration of the mac address. Ironic would add this to it's interface detach method, to ensure no previously used ports cause issues when deploying new baremetal instances.
Changed in neutron: | |
status: | New → In Progress |
Changed in neutron: | |
status: | In Progress → New |
tags: |
added: rfe-triaged removed: rfe |
Changed in neutron: | |
importance: | Undecided → Wishlist |
Changed in neutron: | |
status: | New → In Progress |
tags: | added: queens-backport-potential |
Related fix proposed to branch: master /review. openstack. org/565931
Review: https:/