-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
hive: Don't log interrupt signal as error #23880
hive: Don't log interrupt signal as error #23880
Conversation
/test |
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.
Approving the CODEOWNERS change as well.
Hive can be stopped by sending the process a INT or TERM signal to initiate the stop of the application. Hive was logging an error "Interrupt received" when this happened and this was causing CI jobs to fail as they were checking that no errors were logged. Since stopping via SIGINT/SIGTERM is not errornous, log the event at info level instead. Fixes: cilium#23637 Fixes: b407ffc ("hive: Reimplement on top of dig") Signed-off-by: Jussi Maki <jussi@isovalent.com>
Signed-off-by: Jussi Maki <jussi@isovalent.com>
5075383
to
ed75220
Compare
/test |
The changes are reviewed and they are trivial enough that compile test plus smoke tests should cover them. Merging. |
Should we backport this to v1.13? The error message seems to cause CI flakes on v1.13 (since any error is considered fatal by Jenkins CI). |
Hive can be stopped by sending the process a INT or TERM signal to initiate the stop of the application. Hive was logging an error "Interrupt received" when this happened and this was causing CI jobs to fail as they were checking that no errors were logged. Since stopping via SIGINT/SIGTERM is not errornous, log the event at info level instead.
Fixes: #23637
Fixes: b407ffc ("hive: Reimplement on top of dig")