-
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
gssproxy.service failing to start on upgrade to version 40.20240504.3.0 #165
Comments
Can confirm that on my install of |
Same issue here, I just set up a fresh VM and bootstrapped from CoreOS today and issue only exists after rebasing to |
FYI the SELinux error log is:
In cockpit, there is a solution provided:
This seems to fix the gssproxy.service. |
I was able to start the service after following the command to add gssproxy auditing and installing the module in SE linux (At least that is what I gather from the above command). |
Fixes: #165 This workaround should correct the gssproxy.service failure to start by using tmpfiles to create the missing directories in /var/lib and a service to restore the selinux labels on them.
Upon upgrade to ucore:stable version 40.20240504.3.0 from 39.20240407.3.0, I'm getting a systemd error for gssproxy. I'm struggling figuring out if this is specific to ucore or a more general CoreOS issue, but I thought I'd start here since it looks like it might be brought in with
nfs-utils
.Unfortunately, I'm a noob when it comes to SELinux, but by momentarily disabling selinux and restarting gssproxy, it was able to create the necessary files/directory and now seems to run successfully. I'm not sure what the real solution would be though.
The text was updated successfully, but these errors were encountered: