yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #09534
[Bug 1278674] [NEW] Vm doesn't get IP due to deleting another subnet
Public bug reported:
I found that when a network has two subnet, vm can't get IP if I delete one subnet, you can reprodeuce this problem by the step:
1. create a new network
2. create subnetA in this network
3. create a port in subnetA
4. create subnetB in this network
5. delete subnetA
6. create vm in subnetB, the vm can't get IP
I analyse the problem, the reason is that:
in my environment, the network id is 2914fe0b-721e-4738-b018-71ac4883e6f8, then you can see there are two TAP in the namespace qdhcp-2914fe0b-721e-4738-b018-71ac4883e6f8
root@ubuntu-242:/var/log/neutron# ip netns exec qdhcp-2914fe0b-721e-4738-b018-71ac4883e6f8 ip addr show
10: tapfd90aa02-d9: <BROADCAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether fa:16:3e:6a:37:8f brd ff:ff:ff:ff:ff:ff
inet 60.60.60.3/24 brd 60.60.60.255 scope global tapfd90aa02-d9
inet 169.254.169.254/16 brd 169.254.255.255 scope global tapfd90aa02-d9
inet 70.70.70.2/24 brd 70.70.70.255 scope global tapfd90aa02-d9
inet6 fe80::f816:3eff:fe6a:378f/64 scope link
valid_lft forever preferred_lft forever
15: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
37: tapbed116e5-4f: <BROADCAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether fa:16:3e:96:c7:ec brd ff:ff:ff:ff:ff:ff
inet 70.70.70.2/24 brd 70.70.70.255 scope global tapbed116e5-4f
inet 169.254.169.254/16 brd 169.254.255.255 scope global tapbed116e5-4f
inet6 fe80::f816:3eff:fe96:c7ec/64 scope link
valid_lft forever preferred_lft forever
you can see that the ip: 70.70.70.2 is set on two tap
** Affects: neutron
Importance: Undecided
Assignee: shihanzhang (shihanzhang)
Status: New
** Changed in: neutron
Assignee: (unassigned) => shihanzhang (shihanzhang)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1278674
Title:
Vm doesn't get IP due to deleting another subnet
Status in OpenStack Neutron (virtual network service):
New
Bug description:
I found that when a network has two subnet, vm can't get IP if I delete one subnet, you can reprodeuce this problem by the step:
1. create a new network
2. create subnetA in this network
3. create a port in subnetA
4. create subnetB in this network
5. delete subnetA
6. create vm in subnetB, the vm can't get IP
I analyse the problem, the reason is that:
in my environment, the network id is 2914fe0b-721e-4738-b018-71ac4883e6f8, then you can see there are two TAP in the namespace qdhcp-2914fe0b-721e-4738-b018-71ac4883e6f8
root@ubuntu-242:/var/log/neutron# ip netns exec qdhcp-2914fe0b-721e-4738-b018-71ac4883e6f8 ip addr show
10: tapfd90aa02-d9: <BROADCAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether fa:16:3e:6a:37:8f brd ff:ff:ff:ff:ff:ff
inet 60.60.60.3/24 brd 60.60.60.255 scope global tapfd90aa02-d9
inet 169.254.169.254/16 brd 169.254.255.255 scope global tapfd90aa02-d9
inet 70.70.70.2/24 brd 70.70.70.255 scope global tapfd90aa02-d9
inet6 fe80::f816:3eff:fe6a:378f/64 scope link
valid_lft forever preferred_lft forever
15: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
37: tapbed116e5-4f: <BROADCAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether fa:16:3e:96:c7:ec brd ff:ff:ff:ff:ff:ff
inet 70.70.70.2/24 brd 70.70.70.255 scope global tapbed116e5-4f
inet 169.254.169.254/16 brd 169.254.255.255 scope global tapbed116e5-4f
inet6 fe80::f816:3eff:fe96:c7ec/64 scope link
valid_lft forever preferred_lft forever
you can see that the ip: 70.70.70.2 is set on two tap
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1278674/+subscriptions
Follow ups
References