LXD no suitable availability zone 2.x client

Bug #1786309 reported by Simon Richardson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Unassigned

Bug Description

Juju sometimes fails when bootstrapping lxd on localhost with "suitable availability zone for machine 0 not found" when targeting 2.x lxd instead of 3.x lxd. As there are no availability zones for lxd, it seems we should select the first one and use that and some how that's no longer working for 2.x

Changed in juju:
status: New → Triaged
Revision history for this message
Joseph Phillips (manadart) wrote :

This is probably the error coming out of the AZ logic that is masking an error deeper in the stack - like errant use of the clustering API on an unsupported LXD version.

Changed in juju:
status: Triaged → In Progress
Changed in juju:
status: In Progress → Fix Committed
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.