Skip to content
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

Merged
merged 2 commits into from
Feb 20, 2023

Conversation

joamaki
Copy link
Contributor

@joamaki joamaki commented Feb 20, 2023

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")

@joamaki joamaki requested a review from a team as a code owner February 20, 2023 09:33
@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Feb 20, 2023
@joamaki joamaki added the release-note/misc This PR makes changes that have no direct user impact. label Feb 20, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Feb 20, 2023
@joamaki joamaki requested a review from a team as a code owner February 20, 2023 09:39
@joamaki
Copy link
Contributor Author

joamaki commented Feb 20, 2023

/test

Copy link
Member

@pchaigno pchaigno left a 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>
@joamaki joamaki force-pushed the pr/joamaki/fix-hive-interrupt-log branch from 5075383 to ed75220 Compare February 20, 2023 10:42
@joamaki
Copy link
Contributor Author

joamaki commented Feb 20, 2023

/test

@pchaigno
Copy link
Member

The changes are reviewed and they are trivial enough that compile test plus smoke tests should cover them. Merging.

@pchaigno pchaigno merged commit bb9d074 into cilium:master Feb 20, 2023
@gandro
Copy link
Member

gandro commented Apr 18, 2023

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).

@joamaki joamaki added the needs-backport/1.13 This PR / issue needs backporting to the v1.13 branch label Apr 19, 2023
@nbusseneau nbusseneau mentioned this pull request Apr 20, 2023
15 tasks
@nbusseneau nbusseneau added backport-pending/1.13 The backport for Cilium 1.13.x for this PR is in progress. and removed needs-backport/1.13 This PR / issue needs backporting to the v1.13 branch labels Apr 20, 2023
@sayboras sayboras added backport-done/1.13 The backport for Cilium 1.13.x for this PR is done. and removed backport-pending/1.13 The backport for Cilium 1.13.x for this PR is in progress. labels Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-done/1.13 The backport for Cilium 1.13.x for this PR is done. release-note/misc This PR makes changes that have no direct user impact.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI: K8sDatapathConfig Etcd Check connectivity
5 participants