DCHPOFFER not leaving neutron network node

asked 2014-09-29 19:54:45 -0600

anonymous user

Anonymous

I have setup openstack on 3 nodes as follows:

  • 10.2.4.129: controller
  • 10.2.4.122: neutron network node (compute-122)
  • 10.2.4.125: compute node (compute-125)
root@compute-122:~# neutron agent-list
+--------------------------------------+--------------------+-------------+-------+----------------+
| id                                   | agent_type         | host        | alive | admin_state_up |
+--------------------------------------+--------------------+-------------+-------+----------------+
| 3c3d9e60-6b7b-4dfc-962b-cf818a6559e8 | DHCP agent         | compute-122 | :-)   | True           |
| 5bda115f-8f78-493f-a9d1-c8eb3e3e843d | Open vSwitch agent | compute-125 | :-)   | True           |
| 8fffa808-acd5-4bac-9ba1-fdb10db785c5 | L3 agent           | compute-122 | :-)   | True           |
| 970003e7-b0f7-4513-bf79-3e406a3a91d1 | Metadata agent     | compute-122 | :-)   | True           |
| 9b4b4e8f-d0d2-413d-b594-7456a68f3d6c | Open vSwitch agent | compute-122 | :-)   | True           |
+--------------------------------------+--------------------+-------------+-------+----------------+

When I try spawning a VM, it doesn't get an ip. So, I traced the DHCP/BOOTP packet and saw that it was reaching the dnsmasq service on the network node.

root@compute-122:~# strace -p 28005 -e network,write -s 4096

recvmsg(4, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"D\0\0\0\24\0\2\0\312h\1\0cm\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1\10\0\2\0\ 177\0\0\1\7\0\3\0lo\0\0\24\0\6\0\377\377\377\377\377\377\377\377l\31\33\0l\31\33\0X\0\0\0\24\0\2\0\312h\1\0cm\0\0\2\30\200\0\17\0\0\0\10\0\1\0\300\250\1e\10\0\2\0\300\2 50\1e\10\0\4\0\300\250\1\377\23\0\3\0tap25c0651b-89\0\0\24\0\6\0\377\377\377\377\377\377\377\377\215\31\33\0\215\31\33\0X\0\0\0\24\0\2\0\312h\1\0cm\0\0\2\20\200\0\17\0\ 0\0\10\0\1\0\251\376\251\376\10\0\2\0\251\376\251\376\10\0\4\0\251\376\377\377\23\0\3\0tap25c0651b-89\0\0\24\0\6\0\377\377\377\377\377\377\377\377\311\334\"\0\311\334\" \0", 244}], msg_controllen=0, msg_flags=0}, 0) = 244 recvmsg(4, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"\24\0\0\0\3\0\2\0\312h\1\0cm\0\0\0\0\0\0", 244}], msg_controllen=0, msg_flags=0}, MSG_PEEK|MSG_TRUNC) = 20 recvmsg(4, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"\24\0\0\0\3\0\2\0\312h\1\0cm\0\0\0\0\0\0", 244}], msg_controllen=0, msg_flags=0}, 0) = 20 write(13, "<30>Sep 29 19:08:45 dnsmasq-dhcp[28005]: DHCPDISCOVER(tap25c0651b-89) fa:16:3e:f0:45:cf ", 88) = 88 write(13, "<30>Sep 29 19:08:45 dnsmasq-dhcp[28005]: DHCPOFFER(tap25c0651b-89) 192.168.1.100 fa:16:3e:f0:45:cf ", 99) = 99 sendmsg(3, {msg_name(16)={sa_family=AF_INET, sin_port=htons(68), sin_addr=inet_addr("192.168.1.100")}, msg_iov(1)=[{"\2\1\6\0\351\232@\21\352B\0\0\0\0\0\0\300\250\1d\300\250\1e\0\0\0\0\372\26>\360E\317\0\0\0\0\0\0\0\0\0\0\0\0\0\0 ...

(more)
edit retag flag offensive close merge delete