Cannot add MAAS credentials through juju add-credential

Bug #1578376 reported by Cheryl Jennings
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
juju-core
Invalid
High
Unassigned

Bug Description

After doing add-cloud for my MAAS, I am unable to add credentials for the MAAS:

$ juju add-credential maas2
ERROR cloud "maas2" does not require credentials

But bootstrap requires there to be credentials:

$ juju bootstrap maas2 maas2
ERROR detecting credentials for "maas2" cloud provider: credentials not found

You can work around this by manually adding in the credentials into ~/.local/share/juju/credentials.yaml

Revision history for this message
Ian Booth (wallyworld) wrote :

It sounds like the new MAAS provider is still WIP in this area - the provider needs to have the credential schema defined.

Revision history for this message
Cheryl Jennings (cherylj) wrote :

The "maas2" was my name for the cloud, not the cloud type.

$ jj list-clouds
CLOUD TYPE REGIONS
aws ec2 us-east-1, us-west-1, us-west-2, eu-west-1, eu-central-1, ap-southeast-1, ap-southeast-2 ...
...
local:maas maas
local:maas2 maas

Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta7 → 2.0-beta8
Revision history for this message
Andrew Wilkins (axwalk) wrote :

Cheryl, did your clouds.yaml specify auth-types for your maas2 cloud? juju show-cloud should return something like:

    defined: local
    type: maas
    auth-types: [oauth1]
    endpoint: http://<address>/MAAS/

Changed in juju-core:
status: Triaged → Incomplete
Revision history for this message
Cheryl Jennings (cherylj) wrote :

No, once I added in the auth-types to the cloud definition, I was able to add-credential.

This is a regression from previous betas and we need to make sure we call this out in the release notes. Although, I imagine it will be less of a problem once we have an interactive add-cloud.

Changed in juju-core:
milestone: 2.0-beta8 → none
Changed in juju-core:
status: Incomplete → Triaged
milestone: none → 2.0-beta9
Changed in juju-core:
status: Triaged → Invalid
milestone: 2.0-beta9 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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