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.

Sign up for GitHub

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

Jump to bottom

VR: OpenRC may disable services if one-context starts too long #117

Closed
sk4zuzu opened this issue Jun 19, 2024 · 0 comments
Closed

VR: OpenRC may disable services if one-context starts too long #117

sk4zuzu opened this issue Jun 19, 2024 · 0 comments
Assignees
@sk4zuzu
Labels
type: bug Something isn't working

Comments

@sk4zuzu
Copy link
Contributor

sk4zuzu commented Jun 19, 2024

Description
It seems a race condition between one-context and one-failover can happen if one-context is slow to start.

To Reproduce
It's hard to reporduce in general, but using qemu hypervisor can help here (everything slows down significantly). Deploy a VR then it's possible you see OpenRC stops the one-router4 service (or maybe others as well).

Expected behavior
Every enabled service starts correctly.
@sk4zuzu sk4zuzu added the type: bug Something isn't working label Jun 19, 2024
@sk4zuzu sk4zuzu self-assigned this Jun 19, 2024
sk4zuzu added a commit that referenced this issue Jun 19, 2024
@sk4zuzu
B #117: VR: Wait for one-context to be fully started
9844528
rsmontero pushed a commit that referenced this issue Jun 19, 2024
@sk4zuzu
B #117: VR: Wait for one-context to be fully started (#118)
5315c0f
@sk4zuzu sk4zuzu closed this as completed Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sk4zuzu sk4zuzu

Labels
type: bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sk4zuzu