Re: `api_z1/0' is not running after update to CF v231


Wayne Ha <wayne.h.ha@...>
 

Zach,

After using the latest stemcell, I got a successful deployment. But after that, cf login fails:

vagrant(a)agent-id-bosh-0:~$ cf login -a api.bosh-lite.com -u admin -p admin
API endpoint: api.bosh-lite.com
FAILED
Invalid SSL Cert for api.bosh-lite.com
TIP: Use 'cf login --skip-ssl-validation' to continue with an insecure API endpoint

vagrant(a)agent-id-bosh-0:~$ cf login -a api.bosh-lite.com -u admin -p admin --skip-ssl-validation
API endpoint: api.bosh-lite.com
FAILED
Error performing request: Get https://login.bosh-lite.com/login: stopped after 1 redirect
API endpoint: https://api.bosh-lite.com (API version: 2.51.0)
Not logged in. Use 'cf login' to log in.

I saw the following in uaa.log:

root(a)d142fabc-f823-40df-b9ea-97d306bf7209:/var/vcap/sys/log/uaa# grep -A9 -i error uaa.log | cut -c 65-650
DEBUG --- AntPathRequestMatcher: Checking match of request : '/login'; against '/error'
DEBUG --- AntPathRequestMatcher: Checking match of request : '/login'; against '/email_sent'
DEBUG --- AntPathRequestMatcher: Checking match of request : '/login'; against '/create_account*'
DEBUG --- AntPathRequestMatcher: Checking match of request : '/login'; against '/accounts/email_sent'
DEBUG --- AntPathRequestMatcher: Checking match of request : '/login'; against '/invalid_request'
DEBUG --- AntPathRequestMatcher: Checking match of request : '/login'; against '/saml_error'
DEBUG --- UaaRequestMatcher: [loginAuthenticateRequestMatcher] Checking match of request : '/login'; '/authenticate' with parameters={} and headers {Authorization=[bearer ], accept=[application/json]}
DEBUG --- AntPathRequestMatcher: Checking match of request : '/login'; against '/authenticate/**'
DEBUG --- UaaRequestMatcher: [loginAuthorizeRequestMatcher] Checking match of request : '/login'; '/oauth/authorize' with parameters={source=login} and headers {accept=[application/json]}
DEBUG --- UaaRequestMatcher: [loginTokenRequestMatcher] Checking match of request : '/login'; '/oauth/token' with parameters={source=login, grant_type=password, add_new=} and headers {Authorization=[bearer ], accept=[application/json]}
DEBUG --- UaaRequestMatcher: [loginAuthorizeRequestMatcherOld] Checking match of request : '/login'; '/oauth/authorize' with parameters={login={} and headers {accept=[application/json]}
DEBUG --- AntPathRequestMatcher: Checking match of request : '/login'; against '/password_*'
DEBUG --- AntPathRequestMatcher: Checking match of request : '/login'; against '/email_*'
DEBUG --- AntPathRequestMatcher: Checking match of request : '/login'; against '/oauth/token/revoke/**'
DEBUG --- UaaRequestMatcher: [passcodeTokenMatcher] Checking match of request : '/login'; '/oauth/token' with parameters={grant_type=password, passcode=} and headers {accept=[application/json, application/x-www-form-urlencoded]}

But I don't know what the above mean.

Thanks,

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.