-
Notifications
You must be signed in to change notification settings - Fork 212
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
cf-warden-diego failing state #46
Comments
We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/95699292. |
What does this mean? |
Hi, @charyorde, Can you provide any more information about the state of your local system before those bosh-lite 'VMs' started failing? Has this happened again since the first time you reported it? If you had other deployments, were they also failing in a similar way? I've occasionally had problems with Virtualbox on OS X pausing the bosh-lite VM based on the system's energy conservation settings, such that the bosh-lite containers would fail to be reported as running after the system awoke and resumed the VM. A Thanks, |
Closing this. This occurred just after I deployed diego. At that moment, I didn't understand how the diego deployment was going to work. So when diego was failing, I didn't realize that diego is dependent on some |
[finishes #src/code.cloudfoundry.org/buildpackapplifecycle] Submodule src/code.cloudfoundry.org/buildpackapplifecycle 605f4db90..8f2039f5b: > Merge pull request cloudfoundry#45 from cloudfoundry/PR-contributing > Merge pull request cloudfoundry#46 from cloudfoundry/fix-expiring-certs
Is this correct?
The text was updated successfully, but these errors were encountered: