Skip to content

Commit 7d954ce

Browse files
committed
qa: add a YAML to ignore MGR_DOWN warning
RCA showed that it is not the NFS code that lead to the warning since the warning occurred before the test cases started to execute, later on after some discussion with the venky and greg, it was found that there were some clog changes made recently which leads to this warning being added to the clog. Digging more further, it was found that the warning is generated when mgr fail is run when there is no mgr available. The reason for unavailability is when `setup_mgrs()` in class `MgrTestCase` stops the mgr daemons, sometimes the mgr just crashes - `mgr handle_mgr_signal *** Got signal Terminated ***` and after which `mgr fail` (again part of `setup_mgrs()`) is run and the `MGR_DOWN` warning is generated. This warning is only evident in nfs is because this is the only fs suite that makes use of class `MgrTestCase`. To support my analysis, I had ran about eight jobs in teuthology and I could not reproduce this warning. Since this is not harming the NFS test cases execution and the logs do mention that the mgr daemon did get restarted (`INFO:tasks.cephadm.mgr.x:Restarting mgr.x (starting--it wasn't running)...`), it is good to conclude that ignoring this warning is the simplest solution. Fixes: https://tracker.ceph.com/issues/65265 Signed-off-by: Dhairya Parmar <[email protected]>
1 parent fe870ff commit 7d954ce

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# When the NFS test class is constructed, the `MgrTestCase.setup_mgrs` invokes
2+
# `mgr fail` to restart the MGR which sometimes crashes the daemon and the
3+
# warning `MGR_DOWN` is generated. This is an intermittent failure which is
4+
# irrelevant to the NFS suite, and therefore should be ignored.
5+
6+
overrides:
7+
ceph:
8+
log-ignorelist:
9+
- MGR_DOWN

0 commit comments

Comments
 (0)