GCE (Google Compute Engine) Instance not Receiving DHCP ipv4 address - Support required
up vote
0
down vote
favorite
Symptom
My new VM instance (Linux Ubuntu - 18.04, created from a working image) does not receive an internal ipv4 address via DHCP (provided by GCE).
Diagnostics / Steps taken so far
- Removed virbr0 and recreated virbr0 interface via console access.
- Deleted instance and recreated 2x with the same result.
- SSH fails due to no ipv4 address.
- google shell fails due to no ipv4 address.
- console access is accessible.
- Tried changing hostname via meta tag and cron job with no luck.
Notes
- A working machine created in the same way receives an address and a ens4 interface is created. New machines do not get this.
- New builds were created using the cloud console including the license for VMX capabilities.
- I wonder if the reason dhcp fails is due to the hostname of the machine not matching the instance name due to the build process. However, the documents i have read indicate, once the ipv4 address is received, the hostname is updated?? Need to verify this.
Any ideas / support would be appreciated.
linux google-compute-engine ipv4 dhcp
add a comment |
up vote
0
down vote
favorite
Symptom
My new VM instance (Linux Ubuntu - 18.04, created from a working image) does not receive an internal ipv4 address via DHCP (provided by GCE).
Diagnostics / Steps taken so far
- Removed virbr0 and recreated virbr0 interface via console access.
- Deleted instance and recreated 2x with the same result.
- SSH fails due to no ipv4 address.
- google shell fails due to no ipv4 address.
- console access is accessible.
- Tried changing hostname via meta tag and cron job with no luck.
Notes
- A working machine created in the same way receives an address and a ens4 interface is created. New machines do not get this.
- New builds were created using the cloud console including the license for VMX capabilities.
- I wonder if the reason dhcp fails is due to the hostname of the machine not matching the instance name due to the build process. However, the documents i have read indicate, once the ipv4 address is received, the hostname is updated?? Need to verify this.
Any ideas / support would be appreciated.
linux google-compute-engine ipv4 dhcp
Some Progress - I have now managed to get an ipv4 address by manually running the dhcp client after a boot (it stops once the machine has been restarted). Not sure why it does this when the image it was copied from did not not this but hey ho.
– Gary Constable
Nov 7 at 17:02
What doescreated from a working image
mean? Is this a GCP image or an image from a machine outside GCP?
– John Hanley
Nov 7 at 19:33
Forgive my ignorance... what does this have to do with programming or development?
– jww
Nov 8 at 4:34
Hello, I've flagged this question as I feel it belongs on a different forum such as Serverfault. Please try asking this question on Serverfault.
– neilH
Nov 8 at 14:28
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Symptom
My new VM instance (Linux Ubuntu - 18.04, created from a working image) does not receive an internal ipv4 address via DHCP (provided by GCE).
Diagnostics / Steps taken so far
- Removed virbr0 and recreated virbr0 interface via console access.
- Deleted instance and recreated 2x with the same result.
- SSH fails due to no ipv4 address.
- google shell fails due to no ipv4 address.
- console access is accessible.
- Tried changing hostname via meta tag and cron job with no luck.
Notes
- A working machine created in the same way receives an address and a ens4 interface is created. New machines do not get this.
- New builds were created using the cloud console including the license for VMX capabilities.
- I wonder if the reason dhcp fails is due to the hostname of the machine not matching the instance name due to the build process. However, the documents i have read indicate, once the ipv4 address is received, the hostname is updated?? Need to verify this.
Any ideas / support would be appreciated.
linux google-compute-engine ipv4 dhcp
Symptom
My new VM instance (Linux Ubuntu - 18.04, created from a working image) does not receive an internal ipv4 address via DHCP (provided by GCE).
Diagnostics / Steps taken so far
- Removed virbr0 and recreated virbr0 interface via console access.
- Deleted instance and recreated 2x with the same result.
- SSH fails due to no ipv4 address.
- google shell fails due to no ipv4 address.
- console access is accessible.
- Tried changing hostname via meta tag and cron job with no luck.
Notes
- A working machine created in the same way receives an address and a ens4 interface is created. New machines do not get this.
- New builds were created using the cloud console including the license for VMX capabilities.
- I wonder if the reason dhcp fails is due to the hostname of the machine not matching the instance name due to the build process. However, the documents i have read indicate, once the ipv4 address is received, the hostname is updated?? Need to verify this.
Any ideas / support would be appreciated.
linux google-compute-engine ipv4 dhcp
linux google-compute-engine ipv4 dhcp
asked Nov 7 at 16:27
Gary Constable
41
41
Some Progress - I have now managed to get an ipv4 address by manually running the dhcp client after a boot (it stops once the machine has been restarted). Not sure why it does this when the image it was copied from did not not this but hey ho.
– Gary Constable
Nov 7 at 17:02
What doescreated from a working image
mean? Is this a GCP image or an image from a machine outside GCP?
– John Hanley
Nov 7 at 19:33
Forgive my ignorance... what does this have to do with programming or development?
– jww
Nov 8 at 4:34
Hello, I've flagged this question as I feel it belongs on a different forum such as Serverfault. Please try asking this question on Serverfault.
– neilH
Nov 8 at 14:28
add a comment |
Some Progress - I have now managed to get an ipv4 address by manually running the dhcp client after a boot (it stops once the machine has been restarted). Not sure why it does this when the image it was copied from did not not this but hey ho.
– Gary Constable
Nov 7 at 17:02
What doescreated from a working image
mean? Is this a GCP image or an image from a machine outside GCP?
– John Hanley
Nov 7 at 19:33
Forgive my ignorance... what does this have to do with programming or development?
– jww
Nov 8 at 4:34
Hello, I've flagged this question as I feel it belongs on a different forum such as Serverfault. Please try asking this question on Serverfault.
– neilH
Nov 8 at 14:28
Some Progress - I have now managed to get an ipv4 address by manually running the dhcp client after a boot (it stops once the machine has been restarted). Not sure why it does this when the image it was copied from did not not this but hey ho.
– Gary Constable
Nov 7 at 17:02
Some Progress - I have now managed to get an ipv4 address by manually running the dhcp client after a boot (it stops once the machine has been restarted). Not sure why it does this when the image it was copied from did not not this but hey ho.
– Gary Constable
Nov 7 at 17:02
What does
created from a working image
mean? Is this a GCP image or an image from a machine outside GCP?– John Hanley
Nov 7 at 19:33
What does
created from a working image
mean? Is this a GCP image or an image from a machine outside GCP?– John Hanley
Nov 7 at 19:33
Forgive my ignorance... what does this have to do with programming or development?
– jww
Nov 8 at 4:34
Forgive my ignorance... what does this have to do with programming or development?
– jww
Nov 8 at 4:34
Hello, I've flagged this question as I feel it belongs on a different forum such as Serverfault. Please try asking this question on Serverfault.
– neilH
Nov 8 at 14:28
Hello, I've flagged this question as I feel it belongs on a different forum such as Serverfault. Please try asking this question on Serverfault.
– neilH
Nov 8 at 14:28
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53193705%2fgce-google-compute-engine-instance-not-receiving-dhcp-ipv4-address-support-r%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Some Progress - I have now managed to get an ipv4 address by manually running the dhcp client after a boot (it stops once the machine has been restarted). Not sure why it does this when the image it was copied from did not not this but hey ho.
– Gary Constable
Nov 7 at 17:02
What does
created from a working image
mean? Is this a GCP image or an image from a machine outside GCP?– John Hanley
Nov 7 at 19:33
Forgive my ignorance... what does this have to do with programming or development?
– jww
Nov 8 at 4:34
Hello, I've flagged this question as I feel it belongs on a different forum such as Serverfault. Please try asking this question on Serverfault.
– neilH
Nov 8 at 14:28