Torin Woltjer
2018-11-15 15:33:33 UTC
I've just done this and the problem is still there.
Torin Woltjer
Grand Dial Communications - A ZK Tech Inc. Company
616.776.1066 ext. 2006
www.granddial.com
----------------------------------------
From: Marcio Prado <***@marcioprado.eti.br>
Sent: 11/2/18 5:08 PM
To: ***@granddial.com
Subject: Re: [Openstack] DHCP not accessible on new compute node.
Clone the hd of a server and restore to what is not working.
then only change the required settings ... ip, hostname, etc.
Marcio Prado
Analista de TI - Infraestrutura e Redes
Fone: (35) 9.9821-3561
www.marcioprado.eti.br
Em 02/11/2018 16:27, Torin Woltjer <***@granddial.com> escreveu:I've completely wiped the node and reinstalled it, and the problem still persists. I can't ping instances on other compute nodes, or ping the DHCP ports. Instances don't get addresses or metadata when started on this node.
From: Marcio Prado <***@marcioprado.eti.br>
Sent: 11/1/18 9:51 AM
To: ***@granddial.com
Cc: ***@lists.openstack.org
Subject: Re: [Openstack] DHCP not accessible on new compute node.
I believe you have not forgotten anything. This should probably be bug
...
As my cloud is not production, but rather masters research. I migrate
the VM live to a node that is working, restart it, after that I migrate
back to the original node that was not working and it keeps running ...
Marcio Prado
Analista de TI - Infraestrutura e Redes
Fone: (35) 9.9821-3561
www.marcioprado.eti.br
Torin Woltjer
Grand Dial Communications - A ZK Tech Inc. Company
616.776.1066 ext. 2006
www.granddial.com
----------------------------------------
From: Marcio Prado <***@marcioprado.eti.br>
Sent: 11/2/18 5:08 PM
To: ***@granddial.com
Subject: Re: [Openstack] DHCP not accessible on new compute node.
Clone the hd of a server and restore to what is not working.
then only change the required settings ... ip, hostname, etc.
Marcio Prado
Analista de TI - Infraestrutura e Redes
Fone: (35) 9.9821-3561
www.marcioprado.eti.br
Em 02/11/2018 16:27, Torin Woltjer <***@granddial.com> escreveu:I've completely wiped the node and reinstalled it, and the problem still persists. I can't ping instances on other compute nodes, or ping the DHCP ports. Instances don't get addresses or metadata when started on this node.
From: Marcio Prado <***@marcioprado.eti.br>
Sent: 11/1/18 9:51 AM
To: ***@granddial.com
Cc: ***@lists.openstack.org
Subject: Re: [Openstack] DHCP not accessible on new compute node.
I believe you have not forgotten anything. This should probably be bug
...
As my cloud is not production, but rather masters research. I migrate
the VM live to a node that is working, restart it, after that I migrate
back to the original node that was not working and it keeps running ...
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 [1]_
-------------------------
FROM: "Torin Woltjer"
SENT: 10/30/18 10:48 AM
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
_ [1] [1]WWW.GRANDDIAL.COM [1]_
-------------------------
FROM: Marcio Prado
SENT: 10/29/18 6:23 PM
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.
------
[1] http://www.granddial.com
--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 [1]_
-------------------------
FROM: "Torin Woltjer"
SENT: 10/30/18 10:48 AM
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
_ [1] [1]WWW.GRANDDIAL.COM [1]_
-------------------------
FROM: Marcio Prado
SENT: 10/29/18 6:23 PM
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.
------
[1] http://www.granddial.com
Marcio Prado
Analista de TI - Infraestrutura e Redes
Fone: (35) 9.9821-3561
www.marcioprado.eti.br