-
Notifications
You must be signed in to change notification settings - Fork 78
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
Problem with grootfs store for unprivileged causes garden failure #66
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/156314215 The labels on this github issue will be updated when the story is started. |
Thanks for opening the issue with us. The most suspicious output here is the I/O error and the very strange directory listing for the
Preliminary investigations would suggest a problem in your cluster with the backing data store: https://unix.stackexchange.com/questions/39905/input-output-error-when-accessing-a-directory/39908 I can't really imagine anything that GrootFS could do to result in this, the kernel is seems unable to get the right information from disk. As we discussed on Slack, let's see if deleting the cell in the IAAS and letting BOSH bring it back results in a healthy VM. It might be worth doing some disk diagnostics on your cluster regardless. |
@sparameswaran Sounds like from further investigation, the IAAS delete resolved this. Do you think you need anything more in Garden or can we close this out? |
Deleting the vm from iaas and redeploying appears to have fixed the problem. We can close this issue. Thanks. |
Garden job fails to come up with Pivotal App Service Tile v2.0.8 due to grootfs issue:
Underlying problem with the grootfs unprivileged store:
Running on vsphere with Ops Mgr build 2.0-build-269, PAS v2.0.8, NSX-T tile v2.1 integration
Steps to reproduce
PAS deployment fails to come up with the garden job in diego_cell failing.
Logs
See above
Cause
We believe the root cause was an underlying issue with the IaaS.
Resolution
Recreating the diego_cell didnt work. cannot delete the folder as there is no permission. This was actually resolved by deleting the VM from the IaaS and redeploying.
The text was updated successfully, but these errors were encountered: