Interestingly, I created a brand new selfservice network and DHCP doesn't work on that either. I've followed the instructions in the minimal setup (excluding the controllers as they're already set up) but the new node has no access to the DHCP agent in neutron it seems. Is there a likely component that I've overlooked?
Torin Woltjer Grand Dial Communications - A ZK Tech Inc. Company 616.776.1066 ext. 2006 www.granddial.com ---------------------------------------- From: "Torin Woltjer" <torin.wolt...@granddial.com> Sent: 10/30/18 10:48 AM To: <marciopr...@marcioprado.eti.br>, "openstack@lists.openstack.org" <openstack@lists.openstack.org> Subject: Re: [Openstack] DHCP not accessible on new compute node. I deleted both DHCP ports and they recreated as you said. However, instances are still unable to get network addresses automatically. Torin Woltjer Grand Dial Communications - A ZK Tech Inc. Company 616.776.1066 ext. 2006 www.granddial.com ---------------------------------------- From: Marcio Prado <marciopr...@marcioprado.eti.br> Sent: 10/29/18 6:23 PM To: torin.wolt...@granddial.com Subject: Re: [Openstack] DHCP not accessible on new compute node. The door is recreated automatically. The problem like I said is not in DHCP, but for some reason, erasing and waiting for OpenStack to re-create the port often solves the problem. Please, if you can find out the problem in fact, let me know. I'm very interested to know. You can delete the door without fear. OpenStack will recreate in a short time.
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
