https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETVIRT-1470 netvirt <p>VMs dint get ipv6 address via SLAAC after VM evacuation</p> <h3><a name="1EFFECT"></a>1 EFFECT</h3> <h4><a name="1.1Troublesummary"></a>1.1 Trouble summary</h4> <p>VMs didnt get ipv6 address after VM evacuation.</p> <h3><a name="2DESCRIPTION"></a>2 DESCRIPTION</h3> <h4><a name="2.1.Detailedtroubledescription"></a>2.1. Detailed trouble description</h4> <p>After Vm evacuation (3 vms) none of the vm's first nic got ipv6 address<br/> vminfo.txt file in the logs will have information about VM in the logs<br/> flow dumps are provided before and after migration.</p> <h3><a name="3MEASURES"></a>3 MEASURES</h3> <h4><a name="3.1.WorkaroundandRecovery"></a>3.1. Workaround and Recovery</h4> <p>None</p> NETVIRT-1470

VMs dint get ipv6 address via SLAAC after VM evacuation

Bug High Resolved Done Edwin Anthony RajaRajan Manickam Wed, 24 Oct 2018 11:17:13 +0000 Mon, 25 Nov 2019 07:56:01 +0000 Mon, 25 Nov 2019 07:56:01 +0000 Magnesium ipv6service 0 2 <p>1.Boot VM with metadata set to ha-offline as below .</p> <p> nova meta vm4 set ha-policy='ha-offline'</p> <p> 2.Power off the compute node .<br/> 3. nova host-evacuate &lt;poweredoffcomputename&gt;<br/> 4.Vms will move to other compute nodes .</p> Development Priority Rank 0|i03jtz: