Juju 3 doesn't report when action fails

Bug #2037279 reported by Dragomir Penev
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Critical
Unassigned

Bug Description

Tested on Juju 3.1 and 3.2 with the same results.

Investigated for https://github.com/canonical/postgresql-k8s-operator/issues/242
Also reproducible with a test repo https://github.com/dragomirp/action-test

When the action event is failed, there is no output indicating so when using Juju CLI:
$ juju run action-test/0 fail-action

Running operation 1 with 1 task
  - task 2 on unit-action-test-0

Waiting for task 2...

Show task produces no input:
$ juju show-task 8

In juju 2.9, both waiting for the action and seeing the report for the task will display both the failed state and the optional failed message.

The issue seems to be happening on both microk8s and lxd.

Changed in juju:
status: New → Confirmed
Changed in juju:
status: Confirmed → New
Ian Booth (wallyworld)
Changed in juju:
status: New → Triaged
importance: Undecided → Critical
milestone: none → 3.1.7
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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