-
Notifications
You must be signed in to change notification settings - Fork 894
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
fix: don't deadlock when starting network service with systemctl #5935
fix: don't deadlock when starting network service with systemctl #5935
Conversation
7736535
to
52deab4
Compare
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.
Maybe you can update your comment based on our use case and scenario
# run the second stage in 24.3+. This code therefore exists solely | ||
# for backwards compatibility so that users who think that they | ||
# need to manually start cloud-init (why?) with systemd (again, | ||
# why?) can do so. |
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.
I think I have answered the why part
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!
Proposed Commit Message
Additional Context
#5930
Test Steps
Merge type