The ipv6 address in network_data.json within configdrive is wrong when using IronicDriver to deploy BM

[Eric Lei]

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.

[Matt Riedemann (mriedem)]

> 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.

[Matt Riedemann (mriedem)]

I guess this is the VIF attach baremetal API you're referring to?

https://docs.openstack.org/api-ref/baremetal/#attach-a-vif-to-a-node

It seems ironic should not let you do that while a node is being provisioned, so I'm going to add ironic to this bug.

[Matt Riedemann (mriedem)]

> so I'm going to add ironic to this bug.

Ironic bugs are tracked in storyboard so I guess the ironic bug for this would have to be reported there.

[Eric Lei (leiyashuai)]

Thanks and I have reported a bug here:
https://storyboard.openstack.org/#!/story/2006919

I selected a network including a SLAAC mode ipv6 subnet to build an instance. After build, the ips in configdrive and in horizon are inconsistent.