Hello,
It's time for our weekly PaaS SIG sync-up meeting
Time: 1700 UTC - Wednesdays (date -d "1700 UTC")
Date: Tomorrow Wednesday, September 12 2018
Where: IRC- Freenode - #centos-devel
Agenda:
- OpenShift Current Status
-- rpms
-- automation
- Open Floor
Minutes from last meeting:
https://www.
Thanks for the reply. I was pinning the release only because I was updating
a working inventory from 3.9 and forgot that I had pinned that release to
avoid upgrading to 3.10. I've updated the inventory to set
openshift_release="3.10" and commented out openshift_image_tag and
openshift_pkg_version s
Hi Peter,
Is there a reason behind pinning the release, image_tag and pkg_version
variables to this release version? I would recommend you use just 3.10,
this will ensure that you get the latest version of Openshift installed
Futhermore I found several bugreports with this issue:
https://github.
I am attempting to use the openshift-ansible installer for 3.10 to deploy
openshift on 1 master and 3 minions. I am using the same inventory I have
been using for 3.9 with the changes shown below. I'm consistently hitting a
problem with the control plane pods not appearing. Looking in to it, it
see
We're having problems with the ansible service broker with the etcd
rejecting the certificate of the ansible service broker.
In the logs of the asb-etcd pod I see this:
2018-09-11 09:13:26.779392 I | embed: rejected connection from
"127.0.0.1:50656" (error "tls: failed to verify client's certif
