monthrash has spurious PG_AVAILABILITY etc warnings
no osd thrashing, but not fully peered and healthy before mons start thrashing, which makes peering slow enough to trigger a health warning. saw this on another run today too.
can probably fix by making the wait_for_healthy also wait for unknown pgs? and/or also flush the pg stats?
#2 Updated by Sage Weil over 1 year ago
Ok, I've addressed one soruce of this, but there is another, see
The problem is that with at-end.yaml we set require-osd-release luminous, which with the peering deletes triggers a new peering interval and the PG_AVAILABILITY+PG_DEGRADED warning.