Comment 5 for bug 1822637

I agree that there should be a message on the pending machine about "no
credential available" or "credential suspended due to invalid responses",
or something along those lines.
It seems that when the provisioner goes to create a new instance, it can
see why it is unable to do so, and report that to the user. It may not give
them the immediate understanding that 'update-credential' is the way
forward, but it would at least give them an idea that the machine isn't
just slow to provision.

On Tue, Apr 2, 2019 at 3:40 AM Peter Matulis <email address hidden>
wrote:

> I feel the user is left adrift here.
>
> > you did not tell Juju that the credential is ok again
>
> I did not tell Juju that the credential was *not* ok.
>
> Juju performed an internal action so the onus is on Juju to guide the
> user somehow ("This credential has been marked as invalid. To use it
> again, ensure the corresponding cloud account is active and your
> credential is valid. Then use the `update-credential` command").
>
> Anyway, the command output suggests everything is working as expected,
> but that's not what happens. The machine stays in a pending state
> forever.
>
> https://paste.ubuntu.com/p/Y3prD7rdNd/
>
> I can confirm that this gets things working again:
>
> juju update-credential aws jlaurin
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1822637
>
> Title:
> Operations no longer possible with a reanimated account on AWS
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1822637/+subscriptions
>