-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mgr/cephadm: don't mark daemons created/removed in the last minute as stray #56957
Conversation
e663b1c
to
e7a9292
Compare
… stray There is sometimes a slight delay between when the core mgr knows a daemon has been created/removed and when cephadm knows it as been created/removed. This can cause stray daemon warnings to pop up for a few seconds at a time. This patch tries to avoid that by not marking daemons as stray that it knows it just created/removed in the past minute. Signed-off-by: Adam King <adking@redhat.com>
Was adding a line to serve.py that did if ((datetime_now() - t).total_seconds() < 60) and this was causing the remote_executables test to fail with ValueError: _names: unexpected type: <ast.BinOp object at 0x7f0985c8d670> where it seems the (datetime_now() - t) was resolving to an ast.BinOp node which had no case in _names. This patch makes it so the remote_executables test can also handle these BinOp nodes and the binary operations that could be within the node Signed-off-by: Adam King <adking@redhat.com>
e7a9292
to
d28aabd
Compare
jenkins test make check |
Most failures were Besides that, failures were:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
failures:
Overall, nothing unexpected in the run For this PR in particular, only stray daemon warnings from the run were related to |
There is sometimes a slight delay between when the core
mgr knows a daemon has been removed and when cephadm knows
it as been removed. This can cause stray daemon warnings
to pop up for a few seconds at a time. This patch tries
to avoid that by not marking daemons as stray that it
knows it just removed in the past minute.
This will be inherently tested by the check for any CEPHADM_STRAY_DAEMON
warnings that is already happening in the tests, which we know are currently
present (and has been confirmed to happen when removing nfs and osd daemons
on occasion)
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
x
between the brackets:[x]
. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins retest this please
jenkins test classic perf
jenkins test crimson perf
jenkins test signed
jenkins test make check
jenkins test make check arm64
jenkins test submodules
jenkins test dashboard
jenkins test dashboard cephadm
jenkins test api
jenkins test docs
jenkins render docs
jenkins test ceph-volume all
jenkins test ceph-volume tox
jenkins test windows
jenkins test rook e2e