The ipv6 address in network_data.json within configdrive is wrong when using IronicDriver to deploy BM
Bug #1853389 reported by
Eric Lei
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Incomplete
|
Undecided
|
Eric Lei | ||
Bug Description
After i build an instance with IronicDriver using ipv6 network, the ipv6 address in network_data.json is the old address which neutron allocated in the beginning.
An (ironic) vif-attach call will update mac address of the neutron port before spawn method, which would cause ipv6 address changed.
So, we should update network_info in spawn method of IronicDriver to get the latest ipv6 address. Thus, the network_data.json would be right.
| Changed in nova: | |
| assignee: | nobody → Eric Lei (leiyashuai) |
| tags: | added: ironic |
Revision history for this message
| Matt Riedemann (mriedem) wrote | #1 |
| Changed in nova: | |
| status: | New → Incomplete |
Revision history for this message
| Matt Riedemann (mriedem) wrote | #2 |
Revision history for this message
| Matt Riedemann (mriedem) wrote | #3 |
Revision history for this message
| Eric Lei (leiyashuai) wrote | #4 |
To post a comment you must log in.
> An (ironic) vif-attach call will update mac address of the neutron port before spawn method, which would cause ipv6 address changed.
Are you saying that to reproduce the issue, while the baremetal instance is building in nova, you're making an external asynchronous call to the ironic baremetal API to attach a VIF somehow? Or you're trying to attach a vif to the server in nova while it's building (which shouldn't be possible because the instance is undergoing a task_state transition).
I'm unclear on what the issue is here or how it's reproduced so I'm going to mark this as incomplete.