-
Notifications
You must be signed in to change notification settings - Fork 41
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
Add a new nvidia-gpu-services.target to ensure proper startup order #105
Add a new nvidia-gpu-services.target to ensure proper startup order #105
Conversation
@klueska Can you please assign some reviewers to this? I do not seem to have the correct permissions. |
Is this still up to date based on the latest internal discussions? |
fec6679
to
ac269f9
Compare
ac269f9
to
3f9e54b
Compare
Fixes: #103 |
3f9e54b
to
51e2a45
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.
Thanks for your patience on the round of reviews. Looks good now.
Ah, one caveat -- we can't merget this unless you sign your commit with:
|
51e2a45
to
de09fc9
Compare
Signed-off-by: KeithMnemonic <[email protected]>
de09fc9
to
98bc2a5
Compare
This PR adds a new systemd target to ensure the proper startup order for nvidia-mig-manager. The current settings cause a cyclical dependency on systemd-resolved. This results in broken name resolution after the system is rebooted. The systemd-resolved service needs to be manually restarted for name resolution to work properly.