Ask Your Question
0

dhcp lease not issued for new networks

asked 2019-04-22 13:07:25 -0500

stef97 gravatar image

Hi, After I added a new compute and network node I noticed that any new network I create does not provide dhcp leases Horizon is reporting the IP was successfully assigned but the Vm does not get it If I attach the vm to one of the old networks while running on the new node, it is working fine if I move the vm to one of the old nodes it is working fine The above is happening irrespective of on which host the dnsmaq/netspace is running running tcpdump on the netspace interface appears to indicate that all is good

I would really appreciate any help as it does not make any sense to me

below some technical details

ip netns exec qdhcp-77011d2e-259e-4788-8b06-6f4fee8c350e tcpdump -vnes0 -i tapda8686cd-dd

14:01:59.165236 fa:16:3e:35:52:7c > Broadcast, ethertype IPv4 (0x0800), length 332: (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 318) 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:35:52:7c, length 290, xid 0xe90e6162, secs 60, Flags [none] Client-Ethernet-Address fa:16:3e:35:52:7c Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message Option 53, length 1: Discover Client-ID Option 61, length 7: ether fa:16:3e:35:52:7c MSZ Option 57, length 2: 576 Parameter-Request Option 55, length 9: Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname Domain-Name, MTU, BR, NTP Classless-Static-Route Vendor-Class Option 60, length 12: "udhcp 1.20.1" Hostname Option 12, length 6: "cirros" 14:01:59.165444 fa:16:3e:47:a4:7b > fa:16:3e:35:52:7c, ethertype IPv4 (0x0800), length 370: (tos 0xc0, ttl 64, id 3425, offset 0, flags [none], proto UDP (17), length 356) 10.10.200.10.bootps > 10.10.200.26.bootpc: BOOTP/DHCP, Reply, length 328, xid 0xe90e6162, secs 60, Flags [none] Your-IP 10.10.200.26 Server-IP 10.10.200.10 Client-Ethernet-Address fa:16:3e:35:52:7c Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message Option 53, length 1: Offer Server-ID Option 54, length 4: 10.10.200.10 Lease-Time Option 51, length 4: 86400 RN Option 58, length 4: 43200 RB Option 59, length 4: 75600 Subnet-Mask Option 1, length 4: 255.255.255.0 BR Option 28, length 4: 10.10.200.255 Domain-Name Option 15, length 14: "openstacklocal" Default-Gateway Option 3, length 4: 10.10.200.1 Classless-Static-Route Option 121, length 14: (169.254.169.254/32:10.10.200.10),(default:10.10.200.1) Domain-Name-Server Option 6, length 4: 10.9.0.2 MTU Option 26, length 2: 1450

openstack server show test3 +-------------------------------------+----------------------------------------------------------+ | Field | Value | +-------------------------------------+----------------------------------------------------------+ | OS-DCF:diskConfig | AUTO | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | http://ops04.tor.medavail.net | | OS-EXT-SRV-ATTR:hypervisor_hostname | http://ops04.tor.medavail.net | | OS-EXT-SRV-ATTR:instance_name | instance-0000012e | | OS-EXT-STS:power_state | Running | | OS-EXT-STS:task_state | None | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-04-17T16:52:35.000000 | | OS-SRV-USG:terminated_at | None | | accessIPv4 | | | accessIPv6 | | | addresses | 2testnetwork=10.10.200.26

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2019-04-24 08:58:54 -0500

stef97 gravatar image

updated 2019-05-02 07:29:20 -0500

I apologize for jumping the gun and asking for help without doing my due diligence I spent last few days investigating and the only difference that I found between the current nodes and the new one is missing iptables rule for neutron port on controller

Current nodes have something like below, new nodes doesn't

ACCEPT udp -- any any http://ops03.tor.medavail.net anywhere multiport dports 4789 /* 001 neutron tunnel port incoming neutron_tunnel_10.10.30.158_10.10.30.223 */

We are using vxlan

Although adding it manually does NOT solve my issue, I am thinking that there might be other rules missing

Any idea my iptables are not being properly configured when adding nodes using packstack ? Any resources / tutorilas for adding a compute/neutron centos 7 node manually ?

Steven

edit flag offensive delete link more

Comments

I ended up copying /etc/sysconfig/iptables from a working node and that solved my issue Still not sure why iptables did not get created properly when I deployed a new node

stef97 gravatar imagestef97 ( 2019-05-03 12:59:37 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2019-04-22 13:05:55 -0500

Seen: 12 times

Last updated: May 02