Actions
Bug #58688
closed[test] rbd_mirror_bootstrap.sh "rx-only direction" test fails sporadically
% Done:
0%
Source:
Tags:
backport_processed
Backport:
pacific,quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Description
2023-02-03T16:44:22.394 INFO:tasks.workunit.cluster1.client.mirror.smithi129.stderr:+ testlog 'TEST: verify rx-only direction' 2023-02-03T16:44:22.394 INFO:tasks.workunit.cluster1.client.mirror.smithi129.stderr:+ tee -a /tmp/tmp.Sw6UgKwrMO/rbd-mirror.test.log 2023-02-03T16:44:22.394 INFO:tasks.workunit.cluster1.client.mirror.smithi129.stderr:++ date '+%F %T' 2023-02-03T16:44:22.395 INFO:tasks.workunit.cluster1.client.mirror.smithi129.stderr:+ echo 2023-02-03 16:44:22 TEST: verify rx-only direction 2023-02-03T16:44:22.395 INFO:tasks.workunit.cluster1.client.mirror.smithi129.stderr:2023-02-03 16:44:22 TEST: verify rx-only direction 2023-02-03T16:44:22.396 INFO:tasks.workunit.cluster1.client.mirror.smithi129.stderr:++ rbd --cluster cluster1 --pool mirror mirror pool info --format xml 2023-02-03T16:44:22.396 INFO:tasks.workunit.cluster1.client.mirror.smithi129.stderr:++ xmlstarlet sel -t -v '//mirror/peers/peer[1]/uuid' 2023-02-03T16:44:22.646 INFO:tasks.workunit.cluster1.client.mirror.smithi129.stderr:+ '[' 7ad335f8-e1e5-4f94-9a1c-af5f4ffecf35 = '' ']' 2023-02-03T16:44:22.647 INFO:tasks.workunit.cluster1.client.mirror.smithi129.stderr:+ cleanup 1
start_mirrors ${CLUSTER1}
start_mirrors ${CLUSTER2}
testlog "TEST: verify rx-only direction"
[ "$(rbd --cluster ${CLUSTER1} --pool ${POOL} mirror pool info --format xml |
${XMLSTARLET} sel -t -v '//mirror/peers/peer[1]/uuid')" = "" ]
The test appears to be bogus since a tx-only peer is expected to show up after the remote rbd-mirror daemon pings the local cluster.
Updated by Ilya Dryomov over 1 year ago
Doesn't easily reproduce:
https://pulpito.ceph.com/dis-2023-02-09_17:31:37-rbd-main-distro-default-smithi/
https://pulpito.ceph.com/dis-2023-02-09_17:33:49-rbd-main-distro-default-smithi/
I'm think the reason it passes most of the time is because
${XMLSTARLET} sel -t -v '//mirror/peers/peer[1]/uuid'
just fails and the wrongly expected empty string is produced out of thin air ("set -e" doesn't pick up such command substitution failures).Updated by Ilya Dryomov over 1 year ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 50071
Updated by Ilya Dryomov over 1 year ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot over 1 year ago
- Copied to Backport #58704: quincy: [test] rbd_mirror_bootstrap.sh "rx-only direction" test fails sporadically added
Updated by Backport Bot over 1 year ago
- Copied to Backport #58705: pacific: [test] rbd_mirror_bootstrap.sh "rx-only direction" test fails sporadically added
Updated by Backport Bot about 1 year ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions