Juju prompted for a password in the middle of a bundle deploy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Simon Richardson |
Bug Description
Juju just asked me for my password for an AWS controller in the middle of a bundle deploy:
$ juju deploy ./slurm-
Located charm "percona-cluster" in charm-store, revision 293
Executing changes:
- upload charm percona-cluster from charm-store for series bionic with architecture=amd64
- deploy application percona-cluster from charm-store on bionic
- upload charm /home/h/
please enter password for heitor on foocontroller:
- deploy application slurmctld on centos7
...
This shouldn't happen mid-way. Juju should query this information _before_ trying anything.
Changed in juju: | |
milestone: | 2.9.27 → 2.9.26 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Juju mints login macaroons with a TTL of 24 hours. It looks like at least some of the deploy steps did complete, but with unlucky timing, the macaroon expired par way through.
Juju could look at the TTL caveat on the macaroon and prompt to login again if a reasonable time is not remaining.