cloud-id: enable ESXi 6.5.0

Bug #1731868 reported by Merlijn Sebrechts on 2017-11-13
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
High
Scott Moser
cloud-init (Ubuntu)
High
Chad Smith

Bug Description

Just bootstrapped a Juju controller on a Vmware vsphere cloud and I got a message from cloud-init that the system identified the datasource as ec2. Hypervisor: VMware ESXi, 6.5.0, 5310538

**************************************************************************
# A new feature in cloud-init identified possible datasources for #
# this system as: #
# ['Ec2', 'None'] #
# However, the datasource used was: OVF #
# #
# In the future, cloud-init will only attempt to use datasources that #
# are identified or specifically configured. #
# For more information see #
# https://bugs.launchpad.net/bugs/1669675 #
# #
# If you are seeing this message, please file a bug against #
# cloud-init at #
# https://bugs.launchpad.net/cloud-init/+filebug?field.tags=dsid #
# Make sure to include the cloud provider your instance is #
# running on. #
# #
# After you have filed a bug, you can disable this warning by launching #
# your instance with the cloud-config below, or putting that content #
# into /etc/cloud/cloud.cfg.d/99-warnings.cfg #
# #
# #cloud-config #
# warnings: #
# dsid_missing_source: off #
**************************************************************************

Related branches

Mark Shuttleworth (sabdfl) wrote :

Can we bump up the priority of this, please?

Changed in cloud-init (Ubuntu):
importance: Undecided → High
assignee: nobody → Scott Moser (smoser)
David Britton (davidpbritton) wrote :

Hi Merlijn

I added the cloud-init project on here, and we will target cloud-init 17.2 for this fix.

Just so you know, this is currently a *warning* and your system should be usable even with this warning message displaying when you log in. If you find that it's blocking you (other than being annoying), please do comment back.

Thanks for reporting this and helping to make Ubuntu better!

Changed in cloud-init:
milestone: none → 17.2
assignee: nobody → Chad Smith (chad.smith)
Changed in cloud-init (Ubuntu):
assignee: Scott Moser (smoser) → Chad Smith (chad.smith)
Changed in cloud-init:
importance: Undecided → High
status: New → In Progress
Changed in cloud-init (Ubuntu):
status: New → Triaged
tags: added: dsid
summary: - vmware reported as 'EC2', 'None'
+ cloud-id: enable ESXi 6.5.0
Chad Smith (chad.smith) on 2017-12-07
Changed in cloud-init:
assignee: Chad Smith (chad.smith) → nobody
assignee: nobody → Scott Moser (smoser)
Scott Moser (smoser) on 2017-12-08
Changed in cloud-init:
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cloud-init - 17.1-53-ga5dc0f42-0ubuntu1

---------------
cloud-init (17.1-53-ga5dc0f42-0ubuntu1) bionic; urgency=medium

  * New upstream snapshot.
    - OVF: improve ds-identify to support finding OVF iso transport.
      (LP: #1731868)
    - VMware: Support for user provided pre and post-customization scripts
      [Maitreyee Saikia]

 -- Chad Smith <email address hidden> Fri, 08 Dec 2017 14:46:36 -0700

Changed in cloud-init (Ubuntu):
status: Triaged → Fix Released

This bug is believed to be fixed in cloud-init in 1705804. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: Fix Committed → Fix Released
Chad Smith (chad.smith) wrote :

Validated as fixed in Bionic, will be available in Xenial and Artful with cloud-init 18.1.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers