Closed voelzmo closed 5 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/163622067
The labels on this github issue will be updated when the story is started.
seems like this message is a red herring: looks like an error, but everything is actually fine. Agent unresponsiveness was caused by something else in our system. Closing.
The agent on a VM errors out with this
It seems that
/dev/disk/by-id/
doesn't exist:The persistent disk seems already to be mounted at
/var/vcap/store
, though, see agent output above. The VM was resurrected at some point and is exposing this behavior since. Initial deploy worked fine and did not show any issues.Instance type is r4.4xlarge on AWS, CPI is v73, stemcell is v170.24