Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upPrometheus v2.0.0-rc.0 "Opening storage failed" when used with k8s StatefulSets #3256
Comments
This comment has been minimized.
This comment has been minimized.
|
Have you purged the storage after migrating from beta.5 to rc.0? There were incompatible storage changes. |
This comment has been minimized.
This comment has been minimized.
|
@grobie This happens with a fresh deployment. |
This comment has been minimized.
This comment has been minimized.
|
@grobie It looks that Kubernetes kept the volumes after deleting the StatefulSets. Manually removed the persistent volumes and deployed again. Works fine, thanks! |
camilb
closed this
Oct 6, 2017
This comment has been minimized.
This comment has been minimized.
cauwulixuan
commented
Jan 17, 2018
|
I met the same issue. I removed PV manually and create PV, PVC again, still met this issue. Any suggestions? |
This comment has been minimized.
This comment has been minimized.
mclarke47
commented
Feb 2, 2018
|
@WuLeeX You can use the volume mount permissions hack until this is fixed EXAMPLE. |
This comment has been minimized.
This comment has been minimized.
omerfarukz
commented
Mar 12, 2018
|
Try yo delete or rename lock file in data directory. |
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
camilb commentedOct 6, 2017
Prometheus
v2.0.0-rc.0crashes when it is deployed in Kubernetes using StatefulSets.This happens due the presence of
lost+founddirectory in the mounted volume. After thelost+founddirectory is removed, the pods are started normally.v2.0.0-beta.4andv2.0.0-beta.5doesn't have this issue.Logs:
lost+found