Bug #43889
closed
expected MON_CLOCK_SKEW but got none
Added by Sage Weil over 4 years ago.
Updated about 4 years ago.
Description
description: rados/multimon/{clusters/6.yaml msgr-failures/many.yaml msgr/async.yaml
no_pools.yaml objectstore/bluestore-avl.yaml rados.yaml supported-random-distro$/{centos_8.yaml}
tasks/mon_clock_with_skews.yaml}
/a/sage-2020-01-28_23:42:06-rados-wip-sage-testing-2020-01-28-1413-distro-basic-smithi/4715587
these come up occasionally.
- Priority changed from High to Urgent
/a/sage-2020-01-29_20:14:58-rados-wip-sage-testing-2020-01-29-1034-distro-basic-smithi/4718133
/a/sage-2020-01-29_20:14:58-rados-wip-sage-testing-2020-01-29-1034-distro-basic-smithi/4718332
/a/sage-2020-02-07_23:51:30-rados-wip-sage2-testing-2020-02-07-1439-distro-basic-smithi/4742672
- Status changed from New to In Progress
- Assignee set to Sage Weil
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 33184
- Status changed from Fix Under Review to Pending Backport
- Backport set to nautilus,mimic
- Copied to Backport #44082: nautilus: expected MON_CLOCK_SKEW but got none added
- Copied to Backport #44083: mimic: expected MON_CLOCK_SKEW but got none added
- 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".
Also available in: Atom
PDF