-
Notifications
You must be signed in to change notification settings - Fork 759
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
Unable to attach or mount volumes: unmounted volumes=[job-logs] #1347
Comments
|
|
@vlinxh Did you fix this mount issue? anyone can suggest, how to overcome this issue? |
no solution found |
@vlinxh , do you have a default storageclass? please paste the output of the following command |
|
@zyyw Because other services and jobservice use the same volume, different subpath |
@vlinxh from the following content you posted
the |
encountered the same problem |
in my case, just create two different specified pvc to provide the jobservice’s two service and i solve this problem . you can try it like this. |
This shouldn't be a deployment at all. This specific use-case is exactly what StatefulSet is used for - one volume per replica. |
I also met. Has the problem been solved? |
I think I'm bumping into this issue or something related. Every time the ReplicaSets have a new revision and it wants to roll the Pods, the new Pod gets stuck waiting for the volume(s) which is already attached and mounted by the old Pod. For example with
I have a default StorageClass, (the volumes are being created anyway):
I'm guessing this is because the PVC has the access mode |
@bodgit: If your PVs are RWO then it may be better to change the UpgradeStrategy type from updateStrategy:
type: Recreate |
So after reading through #1137 it turns out the StorageClass used for the jobservice and registry Deployments should ideally be one that permits the For now as I'm just experimenting with Harbor, I've applied the change suggested by @thangamani-arun which will suffice however I wouldn't deploy it this way in a production environment. |
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue. |
When installed with harbor-helm 1.10.2, harbor-jobservice is always in ContainerCreating
The text was updated successfully, but these errors were encountered: