juju-deployer

Can't deploy mojo spec into a JAAS model

Bug #1717069 reported by Casey Marshall
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-deployer
Won't Fix
Wishlist
Unassigned

Bug Description

When I tried to deploy a mojo spec into a JAAS model, I got this error:

https://pastebin.canonical.com/198307/

I was able to deploy the mojo spec just fine when I bootstrapped a controller into the same cloud & region.

Juju version: 2.2.3-xenial-amd64
Mojo version: 0.4.5, installed from apt

Revision history for this message
Laurent Sesquès (sajoupa) wrote :

Looks like it's happening in juju-deployer, adding it to this bug.

Revision history for this message
Laurent Sesquès (sajoupa) wrote :

This is due to juju-deployer expecting user/password to be provided in accounts.yaml.
It should also be able to handle credentials.yaml.

no longer affects: mojo
Revision history for this message
Tom Haddon (mthaddon) wrote :

Confirmed with Casey this is no longer needed, as bundles are used for this.

Changed in juju-deployer:
importance: Undecided → Low
status: New → Won't Fix
Tom Haddon (mthaddon)
Changed in juju-deployer:
importance: Low → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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