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

config-manager: don't crash if no runtime is found running. #180

Merged
merged 4 commits into from
Oct 26, 2023

Conversation

klihub
Copy link
Collaborator

@klihub klihub commented Oct 25, 2023

No description provided.

@klihub klihub marked this pull request as draft October 25, 2023 17:13
@klihub klihub force-pushed the fixes/config-manager branch from fd62089 to 44995dc Compare October 25, 2023 17:14
Use a single D-Bus connection for both listing and restarting
runtime units.

Signed-off-by: Krisztian Litkey <[email protected]>
@klihub klihub force-pushed the fixes/config-manager branch from 44995dc to dbe717a Compare October 25, 2023 21:06
It looks like in the case of CRI-O we need to give it some time
after we have been started up but before we kick it in the head
to restart it over D-Bus. Otherwise it will always report a 255
(-1) exit status for us. Since we run as an init-container, a
non-zero exit status would prevent other containers in our pod
from ever starting up.

It would be good to try and find out what is the exact reason
why this behavior is exhibited by CRI-O but not containerd, and
if it could be fixed in CRI-O. Until then... this.

Signed-off-by: Krisztian Litkey <[email protected]>
@klihub klihub marked this pull request as ready for review October 26, 2023 04:57
Copy link
Collaborator

@marquiz marquiz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not pretty but LGTM 😅 I wouldn't necessarily spend too much time on this

Copy link
Collaborator

@fmuyassarov fmuyassarov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Thanks @klihub . I will spend some time to really understand why is the real culprit in the CRI-O.
But for now, I also agree that this is good.

@marquiz marquiz merged commit 8832f81 into containers:main Oct 26, 2023
2 checks passed
@klihub klihub deleted the fixes/config-manager branch October 26, 2023 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants