Comment 2 for bug 1822637
Revision history for this message
| Anastasia (anastasia-macmood) wrote Re: Operations no longer possible with a reanimated account on AWS | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
This is a normal behavior - Juju will not use the same credential once it is marked as invalid.
You have enabled and disabled and re-enabled credential in a cloud console. Juju paused. But you did not tell Juju that the credential is ok again. This is mostly the result of your testing scenario. Under normal circumstance, in a natural flow of events, the details of a credential will change, so you need to tell Juju to mark that credential as valid. Please use 'update-credential' after re-activating it.