units stay blocked with "Connect a container runtime."
Bug #1834722 reported by
Jason Hobbs
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kubernetes Control Plane Charm |
Fix Released
|
Medium
|
Mike Wilson | ||
Kubernetes Worker Charm |
Fix Released
|
Medium
|
Mike Wilson |
Bug Description
Starting this afternoon, when deploying kubernetes-worker, my units go into blocked state and stay there with this message:
"Connect a container runtime."
It seems like the charm was changed and that a container runtime now has to be connected, but I don't see anything about that in the charm docs or release notes.
Was there a charm release?
Changed in charm-kubernetes-worker: | |
status: | In Progress → Fix Committed |
milestone: | none → 1.15+ck1 |
Changed in charm-kubernetes-master: | |
status: | Fix Committed → Fix Released |
Changed in charm-kubernetes-worker: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
There was a release today to support 1.15. The release notes[1] on ubuntu.com have information about this. Where did you look so we can update those docs to point to the proper place?
[1] https:/ /ubuntu. com/kubernetes/ docs/release- notes