cf-warden-diego failing state

[charyorde]

Is this correct?

Deployment `cf-warden-diego'
+--------------------+---------+------------------+--------------+
| Job/index          | State   | Resource Pool    | IPs          |
+--------------------+---------+------------------+--------------+
| access_z1/0        | failing | access_z1        | 10.244.16.46 |
| brain_z1/0         | failing | brain_z1         | 10.244.16.6  |
| cc_bridge_z1/0     | failing | cc_bridge_z1     | 10.244.16.14 |
| cell_z1/0          | failing | cell_z1          | 10.244.16.10 |
| etcd_z1/0          | running | etcd_z1          | 10.244.16.2  |
| route_emitter_z1/0 | failing | route_emitter_z1 | 10.244.16.18 |
+--------------------+---------+------------------+--------------+

[cf-gitbot]

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.

[charyorde]

bosh cck cf-warden now brings it all up

Deployment `cf-warden-diego'
+--------------------+---------+------------------+--------------+
| Job/index          | State   | Resource Pool    | IPs          |
+--------------------+---------+------------------+--------------+
| access_z1/0        | running | access_z1        | 10.244.16.46 |
| brain_z1/0         | running | brain_z1         | 10.244.16.6  |
| cc_bridge_z1/0     | running | cc_bridge_z1     | 10.244.16.14 |
| cell_z1/0          | running | cell_z1          | 10.244.16.10 |
| etcd_z1/0          | running | etcd_z1          | 10.244.16.2  |
| route_emitter_z1/0 | running | route_emitter_z1 | 10.244.16.18 |
+--------------------+---------+------------------+--------------+

What does this mean?

[emalm]

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 bosh cck would typically bring them back.

Thanks,
Eric

[charyorde]

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 cf-warden components. Hence, I needed to check the cf-warden VMs first.