[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: build fail due to time or cert issue? Peer's Certificate has expired.



Thanks for that! Currently had it setup with wildcard*.example.com and {master,nodeX}.test.example.com so that wouldn't be safe either. Will re-deploy and try again.

Cheers.

On 13 August 2015 at 21:55, Jordan Liggitt <jliggitt redhat com> wrote:
Looks like an issue we saw where all URLs were resolving to the master from within pods. Obviously the master doesn't have a valid cert for github.com

Copied from another email thread:

NetworkManager / dhcp is adding the host's domain name to the search
path. If your host's domain name matches the wildcard path then you'll
end up with these problems.

wildcard *.apps.example.com  and {master,nodeX}.example.com is safe

wildcard *.example.com and {master,nodeX}.example.com is not

The problem exhibits itself in 3.0.1 because kubernetes changed the
ndots value to 5 in order to allow for dns lookups on SRV lookup names
like _dns._udp.kube-dns.default.svc to be considered relative and
follow the search path.



On Aug 13, 2015, at 7:29 AM, Andrew Lau <andrew andrewklau com> wrote:

Hi,

Has anyone ran into this, causing builds to fail on openshift 3?

git.go:127] fatal: unable to access 'https://github.com/openshift/nodejs-ex/': Peer's Certificate has expired.

I'm guessing it's related to a time drift within the container? or are certs not up to date? Suggestions would be much appreciated.

Regards,
Andrew.
_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]