karaf.log
karaf_after_VM_boot.log
karaf_before_VM_reboot.log
[NETVIRT-1055] IPV6 address not getting assigned until reboot the VM Manually Created: 04/Jan/18 Updated: 14/May/18 Resolved: 23/Mar/18 |
|
| Status: | Verified |
| Project: | netvirt |
| Component/s: | None |
| Affects Version/s: | Oxygen |
| Fix Version/s: | Oxygen |
| Type: | Bug | Priority: | Highest |
| Reporter: | RajaRajan Manickam | Assignee: | Somashekar B |
| Resolution: | Done | Votes: | 0 |
| Labels: | VPNV6 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
karaf.log
karaf_after_VM_boot.log
karaf_before_VM_reboot.log
|
| Priority: | Highest |
| Description |
|
IPV6 address not getting assigned until reboot the VM Manually. Steps:
Result:
All flows programmed. Fib-shows entries. No IPV6 address assigned to interface.
Workaround:
Reboot the VM |
| Comments |
| Comment by Faseela K [ 11/Jan/18 ] |
|
From the flow-dumps given flows are all looking proper, looks like something to do with the VM. Only upon reboot, the required packets are coming out of the VM is what I feel |
| Comment by Nishchya Gupta [ 22/Jan/18 ] |
|
IPV6 address getting assigned to VM's and able to ping among them. Unable to reproduce the issue with karaf-0.8.0-20180104.014256-1201. Devstackversion used : newton |
| Comment by RajaRajan Manickam [ 22/Jan/18 ] |
|
Hi Nishchya,
Please do not close any BUG.. If it is not tested in latest devstack version(pike),
Thanks, RajaRajan |
| Comment by Somashekar B [ 22/Mar/18 ] |
|
Below patch handles this issue. Problem: It has been corrected in the patch. |
| Comment by Somashekar B [ 22/Mar/18 ] |
|
The issue was only with unsolicited RA messages. This is fixed with the patch mentioned above. RA in response to RS had no issues. |
instead of All-nodes-address (FF02::1).