In my ceph osd conversion task for one of our customer, I used juju run-action in my script.
I have `set -xue` at the top of script, and was expecting that if any cmd failed, exit and don't run next ones, which is important for ceph/osd/bacahe/disk operations.
However, that didn't work as expected, and I figured out that juju run-action still return 0 even the action failed, which was a surprise to me.
So I strongly agree with the issue mentioned in this case, juju run-action should care about the actual retcode of underneath task and let the caller know.
In my ceph osd conversion task for one of our customer, I used juju run-action in my script. bacahe/ disk operations.
I have `set -xue` at the top of script, and was expecting that if any cmd failed, exit and don't run next ones, which is important for ceph/osd/
However, that didn't work as expected, and I figured out that juju run-action still return 0 even the action failed, which was a surprise to me.
So I strongly agree with the issue mentioned in this case, juju run-action should care about the actual retcode of underneath task and let the caller know.