| 2018-01-31 09:23:12 |
Calvin Hartwell |
bug |
|
|
added bug |
| 2018-01-31 09:23:24 |
Calvin Hartwell |
tags |
cpe-onsite |
cloud-init cpe-onsite juju k8s kubernetes |
|
| 2018-01-31 09:23:50 |
Calvin Hartwell |
tags |
cloud-init cpe-onsite juju k8s kubernetes |
cloud-init cpe-onsite dhcp juju k8s vsphere |
|
| 2018-01-31 10:39:49 |
Calvin Hartwell |
description |
Hi all,
Reported first for k8s: https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480
Juju bug reported here: https://bugs.launchpad.net/juju/+bug/1746358
Basically cloud-init is not giving newly provisioned machines on vSphere their correct hostname before the DHCP lease is given, meaning that every instance during DHCP has the hostname 'ubuntu' which messes up the entries on the DNS server.
Cheers,
- Calvin |
Hi all,
Reported first for k8s: https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480
Juju bug reported here: https://bugs.launchpad.net/juju/+bug/1746358
Basically cloud-init is not giving newly provisioned machines on vSphere their correct hostname before the DHCP lease is given, meaning that every instance during DHCP has the hostname 'ubuntu' which messes up the entries on the DNS server.
From my original juju bug:
We've had an issue recently when provisioning workloads on vSphere. Here is what happens:
1) Set vSphere as the cloud provider in juju (bootstrap)
2) Deploy workload on vSphere, in our case, Canonical Kubernetes (CDK)
3) Machines are deployed using VMDK, but when they boot the initial hostname is Ubuntu (for all machines) until juju changes it during deployment.
4) DHCP gives each machine a lease, but the DNS entries are all messed up because of identical hostnames.
5) If the machines are rebooted they will receive the correct DNS entries. Note that juju will set the correct hostname eventually, but not when the initial DHCP lease is given to the host.
We are seeing this in a production deployment for a customer in the field and would like to see it addressed with priority.
This issue has also been reported by several other users: https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480
https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/171
It seems to me that the code in question is here: https://github.com/juju/juju/blob/763d8e64fbf10d74bfb66384b9d3ae5987275a6a/provider/vsphere/internal/vsphereclient/createvm.go
I believe either the VMDK needs to be generated dynamically which includes the correct hostname/name of the unit in juju OR the correct API calls need to be made to vSphere/ESX/vCenter to set the hostname.
Cheers,
- Calvin |
|
| 2018-02-01 15:04:04 |
David Britton |
marked as duplicate |
|
1600766 |
|
| 2018-02-01 15:18:34 |
Chris Gregan |
tags |
cloud-init cpe-onsite dhcp juju k8s vsphere |
cdo-qa-blocker cloud-init cpe-onsite dhcp juju k8s vsphere |
|
| 2018-02-01 15:19:18 |
Chris Gregan |
bug |
|
|
added subscriber Canonical Field High |
| 2018-02-01 15:51:48 |
Chris Gregan |
removed subscriber Canonical Field High |
|
|
|
| 2018-02-01 15:52:04 |
Chris Gregan |
tags |
cdo-qa-blocker cloud-init cpe-onsite dhcp juju k8s vsphere |
cloud-init cpe-onsite dhcp juju k8s vsphere |
|
| 2018-02-01 18:12:20 |
David Britton |
removed duplicate marker |
1600766 |
|
|
| 2018-02-01 18:22:57 |
David Britton |
bug |
|
|
added subscriber Canonical Field High |
| 2018-02-01 18:23:17 |
David Britton |
tags |
cloud-init cpe-onsite dhcp juju k8s vsphere |
cdo-qa-blocker cloud-init cpe-onsite dhcp juju k8s vsphere |
|
| 2018-02-01 19:15:02 |
Chad Smith |
cloud-init: status |
New |
In Progress |
|
| 2018-02-01 19:15:04 |
Chad Smith |
cloud-init: assignee |
|
Chad Smith (chad.smith) |
|
| 2018-02-01 19:15:07 |
Chad Smith |
cloud-init: importance |
Undecided |
High |
|
| 2018-02-01 23:57:10 |
David Britton |
description |
Hi all,
Reported first for k8s: https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480
Juju bug reported here: https://bugs.launchpad.net/juju/+bug/1746358
Basically cloud-init is not giving newly provisioned machines on vSphere their correct hostname before the DHCP lease is given, meaning that every instance during DHCP has the hostname 'ubuntu' which messes up the entries on the DNS server.
From my original juju bug:
We've had an issue recently when provisioning workloads on vSphere. Here is what happens:
1) Set vSphere as the cloud provider in juju (bootstrap)
2) Deploy workload on vSphere, in our case, Canonical Kubernetes (CDK)
3) Machines are deployed using VMDK, but when they boot the initial hostname is Ubuntu (for all machines) until juju changes it during deployment.
4) DHCP gives each machine a lease, but the DNS entries are all messed up because of identical hostnames.
5) If the machines are rebooted they will receive the correct DNS entries. Note that juju will set the correct hostname eventually, but not when the initial DHCP lease is given to the host.
We are seeing this in a production deployment for a customer in the field and would like to see it addressed with priority.
This issue has also been reported by several other users: https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480
https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/171
It seems to me that the code in question is here: https://github.com/juju/juju/blob/763d8e64fbf10d74bfb66384b9d3ae5987275a6a/provider/vsphere/internal/vsphereclient/createvm.go
I believe either the VMDK needs to be generated dynamically which includes the correct hostname/name of the unit in juju OR the correct API calls need to be made to vSphere/ESX/vCenter to set the hostname.
Cheers,
- Calvin |
Hi all,
Reported first for k8s: https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480
Juju bug reported here: https://bugs.launchpad.net/juju/+bug/1746358
Basically cloud-init is not giving newly provisioned machines on vSphere their correct hostname before the DHCP lease is given, meaning that every instance during DHCP has the hostname 'ubuntu' which messes up the entries on the DNS server.
From my original juju bug:
We've had an issue recently when provisioning workloads on vSphere. Here is what happens:
1) Set vSphere as the cloud provider in juju (bootstrap)
2) Deploy workload on vSphere, in our case, Canonical Kubernetes (CDK)
3) Machines are deployed using VMDK, but when they boot the initial hostname is Ubuntu (for all machines) until juju changes it during deployment.
4) DHCP gives each machine a lease, but the DNS entries are all messed up because of identical hostnames.
5) If the machines are rebooted they will receive the correct DNS entries. Note that juju will set the correct hostname eventually, but not when the initial DHCP lease is given to the host.
We are seeing this in a production deployment for a customer in the field and would like to see it addressed with priority.
This issue has also been reported by several other users: https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480
https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/171
It seems to me that the code in question is here: https://github.com/juju/juju/blob/763d8e64fbf10d74bfb66384b9d3ae5987275a6a/provider/vsphere/internal/vsphereclient/createvm.go
I believe either the VMDK needs to be generated dynamically which includes the correct hostname/name of the unit in juju OR the correct API calls need to be made to vSphere/ESX/vCenter to set the hostname.
Cheers,
- Calvin
Related Bug:
* https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1600766 |
|
| 2018-02-01 23:57:42 |
David Britton |
bug watch added |
|
https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480 |
|
| 2018-02-01 23:59:28 |
David Britton |
bug |
|
|
added subscriber David Britton |
| 2018-02-02 00:04:20 |
David Britton |
description |
Hi all,
Reported first for k8s: https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480
Juju bug reported here: https://bugs.launchpad.net/juju/+bug/1746358
Basically cloud-init is not giving newly provisioned machines on vSphere their correct hostname before the DHCP lease is given, meaning that every instance during DHCP has the hostname 'ubuntu' which messes up the entries on the DNS server.
From my original juju bug:
We've had an issue recently when provisioning workloads on vSphere. Here is what happens:
1) Set vSphere as the cloud provider in juju (bootstrap)
2) Deploy workload on vSphere, in our case, Canonical Kubernetes (CDK)
3) Machines are deployed using VMDK, but when they boot the initial hostname is Ubuntu (for all machines) until juju changes it during deployment.
4) DHCP gives each machine a lease, but the DNS entries are all messed up because of identical hostnames.
5) If the machines are rebooted they will receive the correct DNS entries. Note that juju will set the correct hostname eventually, but not when the initial DHCP lease is given to the host.
We are seeing this in a production deployment for a customer in the field and would like to see it addressed with priority.
This issue has also been reported by several other users: https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480
https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/171
It seems to me that the code in question is here: https://github.com/juju/juju/blob/763d8e64fbf10d74bfb66384b9d3ae5987275a6a/provider/vsphere/internal/vsphereclient/createvm.go
I believe either the VMDK needs to be generated dynamically which includes the correct hostname/name of the unit in juju OR the correct API calls need to be made to vSphere/ESX/vCenter to set the hostname.
Cheers,
- Calvin
Related Bug:
* https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1600766 |
We've had an issue recently when provisioning workloads on vSphere. Here is what happens:
1) Set vSphere as the cloud provider in juju (bootstrap)
2) Deploy workload on vSphere, in our case, Canonical Kubernetes (CDK)
3) Machines are deployed using VMDK, but when they boot the initial hostname is Ubuntu (for all machines) until juju changes it during deployment.
4) DHCP gives each machine a lease, but the DNS entries are all messed up because of identical hostnames.
5) If the machines are rebooted they will receive the correct DNS entries. Note that juju will set the correct hostname eventually, but not when the initial DHCP lease is given to the host.
Basically cloud-init is not giving newly provisioned machines on vSphere their correct hostname before the DHCP lease is given, meaning that every instance during DHCP has the hostname 'ubuntu' which messes up the entries on the DNS server.
Related Bugs:
* https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1600766
* https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480
* https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/171 |
|
| 2018-02-02 00:04:28 |
David Britton |
bug watch added |
|
https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/171 |
|
| 2018-02-02 18:58:25 |
David Britton |
cloud-init: status |
In Progress |
Incomplete |
|
| 2018-02-05 23:45:55 |
David Britton |
cloud-init: status |
Incomplete |
In Progress |
|
| 2018-02-05 23:45:59 |
David Britton |
cloud-init: assignee |
Chad Smith (chad.smith) |
David Britton (davidpbritton) |
|
| 2018-02-15 20:43:26 |
David Britton |
cloud-init: status |
In Progress |
Incomplete |
|
| 2018-02-20 12:34:29 |
Dominique Poulain |
bug |
|
|
added subscriber Dominique Poulain |
| 2018-02-20 16:18:26 |
David Britton |
cloud-init: assignee |
David Britton (davidpbritton) |
Chad Smith (chad.smith) |
|
| 2018-02-20 16:37:39 |
David Britton |
cloud-init: status |
Incomplete |
In Progress |
|
| 2018-02-21 09:13:35 |
Merlijn Sebrechts |
bug |
|
|
added subscriber Merlijn Sebrechts |
| 2018-02-22 10:32:14 |
Ashley Lai |
bug |
|
|
added subscriber Ashley Lai |
| 2018-02-23 16:29:43 |
Jason Hobbs |
cloud-init: status |
In Progress |
Incomplete |
|
| 2018-02-27 21:54:55 |
Chad Smith |
merge proposal linked |
|
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/339720 |
|
| 2018-03-02 14:13:28 |
Chris Gregan |
cloud-init: status |
Incomplete |
In Progress |
|
| 2018-03-02 16:31:24 |
David Britton |
cloud-init: status |
In Progress |
Incomplete |
|
| 2018-03-02 16:54:07 |
David Britton |
cloud-init: status |
Incomplete |
In Progress |
|
| 2018-03-15 05:38:09 |
Chad Smith |
cloud-init: status |
In Progress |
Fix Committed |
|
| 2018-03-15 20:50:34 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/341482 |
|
| 2018-03-27 20:55:26 |
Chad Smith |
cloud-init: status |
Fix Committed |
Fix Released |
|
| 2018-04-16 20:11:00 |
Chad Smith |
information type |
Public |
Public Security |
|
| 2018-05-29 20:28:41 |
hatifnatt |
bug |
|
|
added subscriber hatifnatt |
| 2023-05-11 10:03:53 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/3108 |
|
