-
Notifications
You must be signed in to change notification settings - Fork 16
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
link user from jail failed #207
Comments
@thien-lm Hi, I just checked the deployment on my environment again and didn’t see this error. We haven’t changed the settings for munge in version 1.15.4. Could you share more details about the environment, the Kubernetes version, and attach the Helm chart values in a gist that were used for the update? By the way, can you scale down replica of soperator to 0. And manually change version of munge both worker, controller and login pod on cr.eu-north1.nebius.cloud/soperator-unstable/munge:1.15.4-jammy-slurm24.05.2-dc3c3445 ? |
@thien-lm Hi. Do you still have an issue with that? |
@Uburro i used a jail image that i built by myself, i built populated_jail from jail directory in image folder. Is that directory was intended to build populated_jail image |
@thien-lm Yes, we use that image for populating jail. But am I right, that you have issue with Munge mounting? We didn't change that part of code for 4 months. We can help you, if you provide more details about your installations. May be you can show us your changes in images, your CRD, etc. Please upload them on https://gist.github.com/ or somewhere like gist |
i am trying to run Soperator version 1.15.4, then both worker, controller and login pod show logs like this:
Link users from jail
Bind-mount munge key from K8S secret
mount: /etc/munge/munge.key: bind /mnt/munge-key/..2024_11_29_07_32_20.780902427/munge.key failed.
I ran Soperator 1.14.10 before, and there were no error like that.
The text was updated successfully, but these errors were encountered: