one badly formed credential makes bootstrap fail

Bug #1616523 reported by Nate Finch on 2016-08-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

I have a credentials.yaml file that looks like this:

      auth-type: userpass
      # secrets etc
      auth_type: jsonfile
      file: /home/nate/google.json

Note that google/nate credential has a typo in that auth_type should be auth-type.

This on malformed entry in credentials.yaml causes bootstrap to fail. In fact, even bootstrap --clouds fails:

$ juju bootstrap --clouds
You can bootstrap on these clouds. See ‘--regions <cloud>’ for all regions.
ERROR error loading credential for cloud "aws": missing auth-type

^^ why does the aws cloud care what my google credentials are?

In fact, I can't bootstrap at all:

$ juju bootstrap lxd lxd
ERROR loading credentials: missing auth-type

If I'm bootstrapping lxd, why does juju care if I have a badly formed credential for the cloud named google?

Maybe print a warning, sure... but just failing seems a bit extreme.

Also, there's absolutely no indication of how to fix the problem. As a developer, I luckily realized that I should look at my credentials.yaml file, but a user wouldn't know to do that from that error message.

tags: added: usability
Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.0-beta17
Changed in juju:
milestone: 2.0-beta17 → 2.0-beta18
Changed in juju:
milestone: 2.0-beta18 → 2.0.1
Curtis Hovey (sinzui) on 2016-10-28
Changed in juju:
milestone: 2.0.1 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers