Comment 3 for bug 1688337

AIUI this was a case of AddModel using different credentials which may have
then been revoked after. The original issue was the underlying workers kept
restarting without an indication of who or what was wrong.

John
=:->

On Jun 21, 2017 03:41, "Heather Lanigan" <email address hidden> wrote:

> In general, the OpenStack provider checks the credentials at bootstrap, if
> they fail it says:
> ERROR authentication failed.
>
> Please ensure the credentials are correct. A common mistake is
> to specify the wrong tenant. Use the OpenStack "project" name
> for tenant-name in your model configuration.
>
> Though apparently there are other places a notice like this is needed.
> juju autoload-credentials also works well with the OpenStack clouds.
>
> So far, I've been unable to reproduce this error with different
> incorrect credentials at bootstrap. Can you please supply more
> information about when this error was encountered? And what, if
> anything, was incorrect about the credentials.
>
> This type of error could be an expired token problem.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1688337
>
> Title:
> login failures on Openstack should include better logging
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1688337/+subscriptions
>