init container blocks due to operator exec request got 137 error
Bug #1877515 reported by
Yang Kelvin Liu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Yang Kelvin Liu |
Bug Description
application-
Re-produces steps:
1. bootstrap and deploy some workload to 2.8;
2. upgrade charm;
3. the workload pod now always waits to init;
4. the above error message occurs in model log;
5. run juju scale, new pods are all waiting to be initialised;
# kill the operator, new operator recovers everything.
Changed in juju: | |
milestone: | none → 2.8-rc1 |
importance: | Undecided → High |
status: | New → Triaged |
assignee: | nobody → Yang Kelvin Liu (kelvin.liu) |
tags: | added: k8s |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
milestone: | 2.8-rc1 → none |
Changed in juju: | |
milestone: | none → 2.8-rc2 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/ /github. com/juju/ juju/pull/ 11566 will be landed to 2.8-rc2 to fix it.