Vsphere provider fails to deploy xenial

Bug #1715708 reported by Nicholas Skaggs
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Andrew Wilkins

Bug Description

It seems the vsphere provider fails to deploy xenial bundles. I can bootstrap a xenial or trusty controller, but xenial deployed bundles fail with:

2017-09-07 16:11:39 ERROR ('0', "failed to create instance in any availability zone: The name 'juju-95851d-0' already exists.")

Changed in juju:
status: New → Triaged
importance: Undecided → High
tags: added: vsphere-provider
Revision history for this message
Andrew Wilkins (axwalk) wrote :

I've been deploying xenial on vsphere all this week and last week without issue, so I don't think that's all there is to it. Can you please try again with develop? I landed some significant changes today that affect VM creation.

Changed in juju:
assignee: nobody → Andrew Wilkins (axwalk)
status: Triaged → Incomplete
milestone: none → 2.3-alpha1
Changed in juju:
milestone: 2.3-beta1 → 2.3-beta2
Changed in juju:
milestone: 2.3-beta2 → none
Revision history for this message
Merlijn Sebrechts (merlijn-sebrechts) wrote :

I can confirm that this has been fixed in the edge channel (2.3-beta4+develop-e488d78 (2878))

Changed in juju:
status: Incomplete → Fix Committed
Revision history for this message
Andrew Wilkins (axwalk) wrote :

Thanks, Merlijn!

Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.