| 2020-02-28 15:58:52 |
Dmitrii Shcherbakov |
bug |
|
|
added bug |
| 2020-02-28 16:09:47 |
Dmitrii Shcherbakov |
summary |
relation-set --app -r <num> k=v does not return a non-zero exit code but errors are raised in a unit log on commit |
relation-set --app -r <num> k=v does not return a non-zero exit code but errors are raised in a unit log on commit (for peer relations) |
|
| 2020-02-28 16:10:02 |
Dmitrii Shcherbakov |
description |
`relation-set --app` does not fail for non-leader units in hook executions. The error is only surfaced after the charm process exits and the control is returned back to the unit agent.
juju run --unit nats/1 'relation-ids cluster'
cluster:0
# This should return a non-zero exit code:
juju run --unit nats/1 'relation-set -r 0 --app x=1 ; echo $?'
0
juju debug-log -i nats/1:
unit-nats-1: 16:53:35 ERROR juju.worker.uniter.context could not write settings from "juju-run" to relation 0: permission denied
unit-nats-1: 16:53:35 ERROR juju.worker.uniter resolver loop error: executing operation "run action 4": running action "juju-run": could not write settings from "juju-run" to relation 0: permission denied
unit-nats-1: 16:53:35 ERROR juju.worker.dependency "uniter" manifold worker returned unexpected error: executing operation "run action 4": running action "juju-run": could not write settings from "juju-run" to relation 0: permission denied
nats/1 is not a leader at the time of the call:
juju status
Model Controller Cloud/Region Version SLA Timestamp
default localhost-localhost localhost/localhost 2.7.2 unsupported 16:52:26+01:00
App Version Status Scale Charm Store Rev OS Notes
nats active 3 nats local 0 ubuntu
Unit Workload Agent Machine Public address Ports Message
nats/0* active idle 0 10.209.240.36
nats/1 active idle 1 10.209.240.214
nats/2 active idle 2 10.209.240.157
Machine State DNS Inst id Series AZ Message
0 started 10.209.240.36 juju-b48e3c-0 bionic Running
1 started 10.209.240.214 juju-b48e3c-1 bionic Running
2 started 10.209.240.157 juju-b48e3c-2 bionic Running |
`relation-set --app` does not fail for non-leader units in hook executions. The error is only surfaced after the charm process exits and the control is returned back to the unit agent.
# peer (!) relation
juju run --unit nats/1 'relation-ids cluster'
cluster:0
# This should return a non-zero exit code:
juju run --unit nats/1 'relation-set -r 0 --app x=1 ; echo $?'
0
juju debug-log -i nats/1:
unit-nats-1: 16:53:35 ERROR juju.worker.uniter.context could not write settings from "juju-run" to relation 0: permission denied
unit-nats-1: 16:53:35 ERROR juju.worker.uniter resolver loop error: executing operation "run action 4": running action "juju-run": could not write settings from "juju-run" to relation 0: permission denied
unit-nats-1: 16:53:35 ERROR juju.worker.dependency "uniter" manifold worker returned unexpected error: executing operation "run action 4": running action "juju-run": could not write settings from "juju-run" to relation 0: permission denied
nats/1 is not a leader at the time of the call:
juju status
Model Controller Cloud/Region Version SLA Timestamp
default localhost-localhost localhost/localhost 2.7.2 unsupported 16:52:26+01:00
App Version Status Scale Charm Store Rev OS Notes
nats active 3 nats local 0 ubuntu
Unit Workload Agent Machine Public address Ports Message
nats/0* active idle 0 10.209.240.36
nats/1 active idle 1 10.209.240.214
nats/2 active idle 2 10.209.240.157
Machine State DNS Inst id Series AZ Message
0 started 10.209.240.36 juju-b48e3c-0 bionic Running
1 started 10.209.240.214 juju-b48e3c-1 bionic Running
2 started 10.209.240.157 juju-b48e3c-2 bionic Running |
|
| 2020-02-28 16:10:24 |
Dmitrii Shcherbakov |
description |
`relation-set --app` does not fail for non-leader units in hook executions. The error is only surfaced after the charm process exits and the control is returned back to the unit agent.
# peer (!) relation
juju run --unit nats/1 'relation-ids cluster'
cluster:0
# This should return a non-zero exit code:
juju run --unit nats/1 'relation-set -r 0 --app x=1 ; echo $?'
0
juju debug-log -i nats/1:
unit-nats-1: 16:53:35 ERROR juju.worker.uniter.context could not write settings from "juju-run" to relation 0: permission denied
unit-nats-1: 16:53:35 ERROR juju.worker.uniter resolver loop error: executing operation "run action 4": running action "juju-run": could not write settings from "juju-run" to relation 0: permission denied
unit-nats-1: 16:53:35 ERROR juju.worker.dependency "uniter" manifold worker returned unexpected error: executing operation "run action 4": running action "juju-run": could not write settings from "juju-run" to relation 0: permission denied
nats/1 is not a leader at the time of the call:
juju status
Model Controller Cloud/Region Version SLA Timestamp
default localhost-localhost localhost/localhost 2.7.2 unsupported 16:52:26+01:00
App Version Status Scale Charm Store Rev OS Notes
nats active 3 nats local 0 ubuntu
Unit Workload Agent Machine Public address Ports Message
nats/0* active idle 0 10.209.240.36
nats/1 active idle 1 10.209.240.214
nats/2 active idle 2 10.209.240.157
Machine State DNS Inst id Series AZ Message
0 started 10.209.240.36 juju-b48e3c-0 bionic Running
1 started 10.209.240.214 juju-b48e3c-1 bionic Running
2 started 10.209.240.157 juju-b48e3c-2 bionic Running |
`relation-set --app` does not fail for non-leader units in hook executions. The error is only surfaced after the charm process exits and the control is returned back to the unit agent.
# a peer (!) relation is available
juju run --unit nats/1 'relation-ids cluster'
cluster:0
# This should return a non-zero exit code:
juju run --unit nats/1 'relation-set -r 0 --app x=1 ; echo $?'
0
juju debug-log -i nats/1:
unit-nats-1: 16:53:35 ERROR juju.worker.uniter.context could not write settings from "juju-run" to relation 0: permission denied
unit-nats-1: 16:53:35 ERROR juju.worker.uniter resolver loop error: executing operation "run action 4": running action "juju-run": could not write settings from "juju-run" to relation 0: permission denied
unit-nats-1: 16:53:35 ERROR juju.worker.dependency "uniter" manifold worker returned unexpected error: executing operation "run action 4": running action "juju-run": could not write settings from "juju-run" to relation 0: permission denied
nats/1 is not a leader at the time of the call:
juju status
Model Controller Cloud/Region Version SLA Timestamp
default localhost-localhost localhost/localhost 2.7.2 unsupported 16:52:26+01:00
App Version Status Scale Charm Store Rev OS Notes
nats active 3 nats local 0 ubuntu
Unit Workload Agent Machine Public address Ports Message
nats/0* active idle 0 10.209.240.36
nats/1 active idle 1 10.209.240.214
nats/2 active idle 2 10.209.240.157
Machine State DNS Inst id Series AZ Message
0 started 10.209.240.36 juju-b48e3c-0 bionic Running
1 started 10.209.240.214 juju-b48e3c-1 bionic Running
2 started 10.209.240.157 juju-b48e3c-2 bionic Running |
|
| 2020-03-24 05:05:25 |
Tim Penhey |
tags |
|
hook-tools jujuc relation-set |
|
| 2020-03-24 05:05:28 |
Tim Penhey |
juju: status |
New |
Triaged |
|
| 2020-03-24 05:05:31 |
Tim Penhey |
juju: importance |
Undecided |
Medium |
|
| 2022-11-03 21:44:03 |
Canonical Juju QA Bot |
juju: importance |
Medium |
Low |
|
| 2022-11-03 21:44:04 |
Canonical Juju QA Bot |
tags |
hook-tools jujuc relation-set |
expirebugs-bot hook-tools jujuc relation-set |
|
