Re: Failed to deploy diego 0.1452.0 on openstack: database_z2/0 is not running after update
Yunata, Ricky <rickyy@...>
Hi Adrian,
I have tried it again however I still couldn't get it to work. I'm not sure what was wrong. I even re-generate all the certificates again.
Anyway, I set the "require ssl" parameter to false and it works. So, yeah definitely there's something wrong with the certificate.
I will try again to use the certificate, but for now I can run Diego successfully. Thanks a lot for your help and people at pivotal team.
Ricky Yunata
Please consider the environment before printing this email
toggle quoted message
Show quoted text
I have tried it again however I still couldn't get it to work. I'm not sure what was wrong. I even re-generate all the certificates again.
Anyway, I set the "require ssl" parameter to false and it works. So, yeah definitely there's something wrong with the certificate.
I will try again to use the certificate, but for now I can run Diego successfully. Thanks a lot for your help and people at pivotal team.
Ricky Yunata
Please consider the environment before printing this email
-----Original Message-----
From: Adrian Zankich [mailto:azankich(a)pivotal.io]
Sent: Saturday, 2 April 2016 3:57 AM
To: cf-dev(a)lists.cloudfoundry.org
Subject: [cf-dev] Re: Re: Re: Re: Re: Re: Re: Re: Failed to deploy diego 0.1452.0 on openstack: database_z2/0 is not running after update
Hi Ricky,
We deconstructed the certs you provided in your manifest and think that you may have missed a step when you generated your peer ssl cert. Your peer cert is missing the DNS wildcard entry '*.etcd.service.cf.internal`, it will show up like this if you deconstruct your cert
X509v3 Subject Alternative Name:
DNS:*.etcd.service.cf.internal, DNS:etcd.service.cf.internal
If you regenerate your peer ssl cert with:
$ certstrap --depot-path peer request-cert --common-name "etcd.service.cf.internal" --domain "*.etcd.service.cf.internal,etcd.service.cf.internal"
It is detailed in https://github.com/cloudfoundry-incubator/diego-release#generating-tls-certificates step #8.
That should fix the ssl error you're experiencing.
- Adrian
Disclaimer
The information in this e-mail is confidential and may contain content that is subject to copyright and/or is commercial-in-confidence and is intended only for the use of the above named addressee. If you are not the intended recipient, you are hereby notified that dissemination, copying or use of the information is strictly prohibited. If you have received this e-mail in error, please telephone Fujitsu Australia Software Technology Pty Ltd on + 61 2 9452 9000 or by reply e-mail to the sender and delete the document and all copies thereof.
Whereas Fujitsu Australia Software Technology Pty Ltd would not knowingly transmit a virus within an email communication, it is the receiver’s responsibility to scan all communication and any files attached for computer viruses and other defects. Fujitsu Australia Software Technology Pty Ltd does not accept liability for any loss or damage (whether direct, indirect, consequential or economic) however caused, and whether by negligence or otherwise, which may result directly or indirectly from this communication or any files attached.
If you do not wish to receive commercial and/or marketing email messages from Fujitsu Australia Software Technology Pty Ltd, please email unsubscribe(a)fast.au.fujitsu.com
From: Adrian Zankich [mailto:azankich(a)pivotal.io]
Sent: Saturday, 2 April 2016 3:57 AM
To: cf-dev(a)lists.cloudfoundry.org
Subject: [cf-dev] Re: Re: Re: Re: Re: Re: Re: Re: Failed to deploy diego 0.1452.0 on openstack: database_z2/0 is not running after update
Hi Ricky,
We deconstructed the certs you provided in your manifest and think that you may have missed a step when you generated your peer ssl cert. Your peer cert is missing the DNS wildcard entry '*.etcd.service.cf.internal`, it will show up like this if you deconstruct your cert
X509v3 Subject Alternative Name:
DNS:*.etcd.service.cf.internal, DNS:etcd.service.cf.internal
If you regenerate your peer ssl cert with:
$ certstrap --depot-path peer request-cert --common-name "etcd.service.cf.internal" --domain "*.etcd.service.cf.internal,etcd.service.cf.internal"
It is detailed in https://github.com/cloudfoundry-incubator/diego-release#generating-tls-certificates step #8.
That should fix the ssl error you're experiencing.
- Adrian
Disclaimer
The information in this e-mail is confidential and may contain content that is subject to copyright and/or is commercial-in-confidence and is intended only for the use of the above named addressee. If you are not the intended recipient, you are hereby notified that dissemination, copying or use of the information is strictly prohibited. If you have received this e-mail in error, please telephone Fujitsu Australia Software Technology Pty Ltd on + 61 2 9452 9000 or by reply e-mail to the sender and delete the document and all copies thereof.
Whereas Fujitsu Australia Software Technology Pty Ltd would not knowingly transmit a virus within an email communication, it is the receiver’s responsibility to scan all communication and any files attached for computer viruses and other defects. Fujitsu Australia Software Technology Pty Ltd does not accept liability for any loss or damage (whether direct, indirect, consequential or economic) however caused, and whether by negligence or otherwise, which may result directly or indirectly from this communication or any files attached.
If you do not wish to receive commercial and/or marketing email messages from Fujitsu Australia Software Technology Pty Ltd, please email unsubscribe(a)fast.au.fujitsu.com