Actions
Bug #65235
openupgrade/reef-x/stress-split: "OSDMAP_FLAGS: noscrub flag(s) set" warning in cluster log
% Done:
0%
Source:
Q/A
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
/a/teuthology-2024-03-29_02:08:11-upgrade-squid-distro-default-smithi/7629127
2024-03-29T06:44:20.321 INFO:teuthology.orchestra.run.smithi045.stdout:2024-03-29T05:10:00.000191+0000 mon.a (mon.0) 1714 : cluster 3 [WRN] OSDMAP_FLAGS: noscrub flag(s) set
Likely needs to be whitelisted.
Updated by Laura Flores 23 days ago
There are many instances of this flag getting set in the test run intentionally, so it makes sense to whitelist.
/a/yuriw-2024-04-09_14:58:21-upgrade-wip-yuri4-testing-2024-04-08-1432-distro-default-smithi/7648856$ cat teuthology.log | grep "osd set" | grep "nodeep-scrub"
2024-04-10T02:27:05.258 DEBUG:teuthology.orchestra.run.smithi062:> sudo /home/ubuntu/cephtest/cephadm --image quay.ceph.io/ceph-ci/ceph:reef shell --fsid c02b312e-f6dc-11ee-b64a-cb9ed24678a4 -- ceph osd set nodeep-scrub
2024-04-10T02:27:18.827 INFO:journalctl@ceph.mon.a.smithi062.stdout:Apr 10 02:27:18 smithi062 bash[80906]: audit 2024-04-10T02:27:18.270108+0000 mon.a (mon.0) 1416 : audit 1 from='client.? 172.21.15.62:0/1866068261' entity='client.admin' cmd=[{"prefix": "osd set", "key": "nodeep-scrub"}]: dispatch
2024-04-10T02:27:18.827 INFO:journalctl@ceph.mon.c.smithi062.stdout:Apr 10 02:27:18 smithi062 bash[83329]: audit 2024-04-10T02:27:18.270108+0000 mon.a (mon.0) 1416 : audit 1 from='client.? 172.21.15.62:0/1866068261' entity='client.admin' cmd=[{"prefix": "osd set", "key": "nodeep-scrub"}]: dispatch
2024-04-10T02:27:19.138 INFO:journalctl@ceph.mon.b.smithi129.stdout:Apr 10 02:27:18 smithi129 bash[67507]: audit 2024-04-10T02:27:18.270108+0000 mon.a (mon.0) 1416 : audit 1 from='client.? 172.21.15.62:0/1866068261' entity='client.admin' cmd=[{"prefix": "osd set", "key": "nodeep-scrub"}]: dispatch
Updated by Laura Flores 17 days ago
/a/yuriw-2024-04-11_17:03:54-rados-wip-yuri6-testing-2024-04-02-1310-distro-default-smithi/7652474
msgr-failures/few rados thrashers/mapgap thrashosds-health workloads/radosbench} duration: 4465.95135641098 failure_reason: '"2024-04-12T01:10:00.000098+0000 mon.a (mon.0) 1265 : cluster [WRN] Health detail: HEALTH_WARN noscrub flag(s) set" in cluster log' flavor: default owner: scheduled_yuriw@teuthology success: false
Updated by Brad Hubbard 17 days ago
- Category set to Tests
- Assignee changed from Laura Flores to Brad Hubbard
- Source set to Q/A
Updated by Laura Flores 17 days ago
- Related to Cleanup #65521: Add expected warnings in cluster log to ignorelists added
Updated by Brad Hubbard 11 days ago
Unfortunately, noscrub and nodeep-scrub are not the only warnings we would need to mask for the thrashosds-health test as there appear to be many others. Looking into this further.
Updated by Laura Flores 4 days ago
@Brad Hubbard perhaps we can address just the warnings reported in this Tracker, and address additional warnings in a Part 2.
Actions