2.6.5: in k8s on openstack deploy, several units stay in allocating state forever
Bug #1834657 reported by
Jason Hobbs
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Critical
|
Joseph Phillips | ||
Bug Description
When deploying k8s on openstack with the 2.6/candidate (2.6.5), several applications got stuck in 'allocating' state forever:
Revision history for this message
| Jason Hobbs (jason-hobbs) wrote | #1 |
Revision history for this message
| Jason Hobbs (jason-hobbs) wrote | #2 |
Revision history for this message
| Richard Harding (rharding) wrote | #3 |
| Changed in juju: | |
| milestone: | none → 2.6.5 |
| assignee: | nobody → Joseph Phillips (manadart) |
| importance: | Undecided → Critical |
| status: | New → Fix Committed |
| tags: | added: cdo-release-blocker |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Thank you for the report! This is indeed a 2.6.5 regression. It was caught last night and a patch has been applied.
https:/
We're working to get a fresh build of snaps to promote a new candidate with the fix.