A too-long application name leaves charm stuck installing agent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Witold Krecicki |
Bug Description
Using libjuju to drive Juju 2.2.6, I've found that it's possible to deploy a charm that will always get stuck during 'installing agent' by specifying an application that is too long.
Step to recreate:
juju deploy mysql jujud-unit-
Observed behaviour:
`juju status` simply shows that the charm is 'installing agent' and does not change regardless of how long it's let run.
`juju debug-log` shows this recurring repeatedly:
machine-0: 13:40:34 ERROR juju.service.
ag-dc-ping-
Expected behaviour:
The deploying charm should enter an error state so that the operator (either a user or automaton driving libjuju) knows that deployment has failed (and why)
Changed in juju: | |
assignee: | nobody → Witold Krecicki (wpk) |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
It looks like the max name length is 51 characters. I can deploy an application named that long, but as soon as it hits 52 or above it triggers the above behavior.