You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BOSH Director: bump 271.0.0→271.1.0, sc 621.75→621.76
We place the Let's Encrypt root certificate (`DST Root CA X3`) in the
property `hm.director_account.ca_cert`, which gets templated in the
health_monitor job as `uaa.pem`. Previously it used the auto-generated
one.
This is a bit of a mystery why this suddenly began to fail. I suspect
that the 621.75→621.76 stemcell bump had to do with it, but it could
also have been the BOSH (director) bump.
fixes:
```
bosh create-env ...
Waiting for instance 'bosh/0' to be running... Failed (00:05:04)
Failed deploying (00:21:05)
ssh bosh-vsphere
sudo -i
monit summary
Process 'health_monitor' Does not exist
less /var/vcap/sys/log/health_monitor/health_monitor.log
I, [2020-06-21T22:34:02.593696 #23850] INFO : BOSH HealthMonitor 0.0.0 is running...
E, [2020-06-21T22:34:02.629167 #23850] ERROR : Failed to obtain token from UAA: #<CF::UAA::SSLException: Invalid SSL Cert for https://bosh-vsphere.nono.io:8443/oauth/token. Use '--skip-ssl-validation' to continue with an insecure target>
E, [2020-06-21T22:34:02.696326 #23850] ERROR : Failed to obtain token from UAA: #<CF::UAA::SSLException: Invalid SSL Cert for https://bosh-vsphere.nono.io:8443/oauth/token. Use '--skip-ssl-validation' to continue with an insecure target>
```
0 commit comments