Canonical Juju

caas remote init failed

Bug #1876261 reported by Yang Kelvin Liu on 2020-05-01

This bug report is a duplicate of: Bug #1877515: init container blocks due to operator exec request got 137 error. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Canonical Juju	Triaged	High	Harry Pidcock	Canonical Juju 2.8-rc1

Bug Description

Caas caas-unit-init failed:

application-mariadb-k8s: 00:36:44 ERROR juju.worker.uniter resolver loop error: executing operation "remote init": caas-unit-init for unit "mariadb-k8s/0" failed: : command terminated with exit code 137
application-mariadb-k8s: 00:36:44 INFO juju.worker.uniter unit "mariadb-k8s/0" shutting down: executing operation "remote init": caas-unit-init for unit "mariadb-k8s/0" failed: : command terminated with exit code 137

Tags:

Yang Kelvin Liu (kelvin.liu) on 2020-05-01

Changed in juju:
milestone:	none → 2.8-rc1

Ian Booth (wallyworld) on 2020-05-05

Changed in juju:
importance:	Undecided → High
status:	New → Triaged

Harry Pidcock (hpidcock) on 2020-05-05

tags:

added: k8s

Tim Penhey (thumper) on 2020-05-05

Changed in juju:
assignee:	nobody → Yang Kelvin Liu (kelvin.liu)

Harry Pidcock (hpidcock) on 2020-05-06

Changed in juju:
assignee:	Yang Kelvin Liu (kelvin.liu) → Harry Pidcock (hpidcock)

Revision history for this message

Harry Pidcock (hpidcock) wrote on 2020-05-06:

I haven't been able to repro

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #1877515 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.