init container blocks due to operator exec request got 137 error

Bug #1877515 reported by Yang Kelvin Liu
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
High
Yang Kelvin Liu

Bug Description

application-mariadb-k8s: 23:25:18 ERROR juju.worker.uniter resolver loop error: executing operation "remote init": command terminated with exit code 137

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.

Tags: k8s Edit Tag help
Ian Booth (wallyworld)
Changed in juju:
milestone: none → 2.8-rc1
importance: Undecided → High
status: New → Triaged
assignee: nobody → Yang Kelvin Liu (kelvin.liu)
tags: added: k8s
Ian Booth (wallyworld)
Changed in juju:
status: Triaged → In Progress
Changed in juju:
milestone: 2.8-rc1 → none
Ian Booth (wallyworld)
Changed in juju:
milestone: none → 2.8-rc2
Revision history for this message
Yang Kelvin Liu (kelvin.liu) wrote :

https://github.com/juju/juju/pull/11566 will be landed to 2.8-rc2 to fix it.

Ian Booth (wallyworld)
Changed in juju:
status: In Progress → Fix Committed
Harry Pidcock (hpidcock)
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers