Canonical Juju

Expirable bugs

Incomplete bug reports can expire if they are unattended and are inactive. These bugs are not confirmed, or in a status that indicates they were confirmed. An Incomplete bug can remain in this list indefinitely, so long as the bug is regularly updated. See Bugs/Expiry.

1 → 11 of 11 results First • Previous • Next • Last
High
Incomplete
#2057928 Migration from 2.9 to 3.3 caused unit agent to stop working
Canonical Juju 6
Undecided
Incomplete
#2058048 Mess in spaces support for Azure
Canonical Juju 6
Low
Incomplete
#2058339 Unable to create application, got error: model cache: "UUID" did not appear in cache timeout
Canonical Juju 6
Undecided
Incomplete
#2059105 Status Code 418 (I'm a teapot) thrown by the Pebble readiness check
Canonical Juju 6
Undecided
Incomplete
#2059253 Canot bootstrap with --config
Canonical Juju 6
High
Incomplete
#2060271 Deployed charm contains future revision code
Canonical Juju 6
Undecided
Incomplete
#2025160 juju controllers hit open file limit
Canonical Juju 14
High
Incomplete
#2053055 Unretrievable data during controller migration from 2.9.x -> 3.1+
Canonical Juju 12
Undecided
Incomplete
#2060804 juju debug-log has line limit
Canonical Juju 6
Undecided
Incomplete
#2060706 cannot bootstrap local machine
Canonical Juju 6
Undecided
Incomplete
#2065761 invalid cmr macaroon when getting cmr secret
Canonical Juju 10
1 → 11 of 11 results First • Previous • Next • Last