yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #80763
[Bug 1853389] [NEW] The ipv6 address in network_data.json within configdrive is wrong when using IronicDriver to deploy BM
Public bug reported:
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.
** Affects: nova
Importance: Undecided
Assignee: Eric Lei (leiyashuai)
Status: New
** Changed in: nova
Assignee: (unassigned) => Eric Lei (leiyashuai)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1853389
Title:
The ipv6 address in network_data.json within configdrive is wrong when
using IronicDriver to deploy BM
Status in OpenStack Compute (nova):
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1853389/+subscriptions