LXD and manual provider shouldn't require auth type

Bug #1592981 reported by Nicholas Skaggs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Andrew Wilkins

Bug Description

Ass seen in http://reports.vapour.ws/releases/issue/5761b16f749a56189807fa65;

Attempting to bootstrap with lxd or manual seemingly requires configuration, but should not.

ERROR cmd supercommand.go:448 failed to initialize state: validating initialization args: validating cloud credentials: credential "" with auth-type "empty" is not supported (expected one of [])

summary: - LXD and manual shouldn't require auth type
+ LXD and manual provider shouldn't require auth type
Changed in juju-core:
status: New → Triaged
importance: Undecided → Critical
tags: added: blocker
tags: added: bootstrap jujuqa lxd-provider manual-provider
Ian Booth (wallyworld)
Changed in juju-core:
milestone: none → 2.0-beta9
Andrew Wilkins (axwalk)
Changed in juju-core:
status: Triaged → Won't Fix
status: Won't Fix → In Progress
assignee: nobody → Andrew Wilkins (axwalk)
Revision history for this message
Andrew Wilkins (axwalk) wrote :

This is fixed, but there is another issue for manual and maas that I'm working on fixing now:
https://bugs.launchpad.net/juju-core/+bug/1593033

Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta9 → none
milestone: none → 2.0-beta9
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.