[NETVIRT-417] IPV6_service: IPV4 address assignment failing for VM already running with IPV6 address Created: 10/Jan/17  Updated: 08/Nov/19  Resolved: 08/Nov/19

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Boron
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Abhik Ghosh Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Zip Archive log.zip    
External issue ID: 7508

 Description   

Scenario:
---------

Validating dual stack Ipv4 and IPv6 address assignment to Neutron VM by creating the IPV6 subnet first, then spawn the VM and then creating IPV4 subnet.

1.create a IPV6 subnet in slaac mode:

neutron net-create mynet1
neutron subnet-create mynet1 2001:db8:1234::/64 --name ipv6s1 --ip-version 6 --ipv6-ra-mode slaac --ipv6-address-mode slaac
neutron router-create router1
neutron router-interface-add router1 ipv6s1

2.spawn the VM:

nova boot --flavor m1.small --image cirros-0.3.4-x86_64-uec --availability-zone nova:test-ovs --nic net-name=mynet1 vm1

3.create IPV4 subnet to the same network (also enable dhcp on ODL):

neutron subnet-create mynet1 13.0.0.0/24 --name ipv4s1 --enable-dhcp

5.reboot the VM

------------------------------

VM doesn't receive dhcp offer even if we run dhcp client or reboot the VM. Also, the table 60 entry is missing.

But, if we create another VM, then both the addresses are assigned for it. The corresponding table 60 entries are also seen.

Attached logs:
1>Openstack log
2>Karaf log



 Comments   
Comment by Abhik Ghosh [ 10/Jan/17 ]

Attachment log.zip has been added with description: Openstack and karaf log

Comment by mahesh loni [ 09/Oct/17 ]

Steps to reproduce :

1.Create network
2.create ipv6 subnet
neutron subnet-create n1 2001:db8:cafe::/64 --ip-version 6 --ipv6-ra-mode slaac --ipv6-address-mode slaac --name ipv6s1
neutron router-create R1
neutron router-interface-add R1 ipv6s1
3.Boot VM in any compute node
4.check the VM is having ipv6 address
5.Now create ipv4 subnet
neutron subnet-create n1 13.0.0.0/24
6.Now VM is not getting assigned IPv4 address

Comment by Abhinav Gupta [ 08/Nov/19 ]

Old bug, will reopen if seen again

Generated at Wed Feb 07 20:21:30 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.