Is Ansible not available in EPEL or not recommended? 
The last time I installed; I got 2.6 version.

I do turn off the EPEL repo after Ansible is installed when installing OpenShift.


On Oct 18, 2018 11:11 AM, "Daniel Comnea" <comnea.dani@gmail.com> wrote:
PSB

On Thu, Oct 18, 2018 at 6:17 PM Rich Megginson <rmeggins@redhat.com> wrote:
On 10/17/18 3:38 AM, Daniel Comnea wrote:
> Hi,
>
> We would like to announce that OKD v3.11 rpms are available for testing at [1].
>
> As such we are calling for help from community to start testing and let us know if there are issues with the rpms and its dependencies.
>
> And in the spirit of transparency see below the plan to promote the rpms to mirror.centos.org repo:
>
>  1. in the next few days the packages should be promoted to the test repo [2] (currently it does not exist, we are waiting to be sync'ed in the background)
>  2. in one/two weeks time if we haven't heard any issues/ blockers we are going to promote to [3] repo (currently it doesn't exist, it will once the rpm will be promoted and signed)
>
>
> Please note the ansbile version use (and supported) /*must be*/ 2.6.x and not 2.7, if you opt to ignore the warning you will run into issues.
>
> On a different note the CentOS Infra team are working hard (thanks !) to package and release a centos-ansible rpm which we'll promote in our PaaS repos.


So does that mean we cannot test OKD v3.11 yet, unless we build our own version of ansible 2.6.x?
[DC]: so i've been waiting for Infra guys to build the rpm but they are traveling and as such i went ahead and tagged ansible 2.6. and it should appear [1] in next 15/20 min. That should unblock you all from testing it.


What will happen if we attempt to use ansible 2.7?  I my testing, I get stuck at deploying the control plane pods - it seems the virtual networking was not set up by openshift-ansible.
[DC]: there been few issues reported on this topic and since they were already know we made it clear which ansible version is supported (read - it works) and which not.

>
> The rational is to bring more control around the ansible version used/ required by OpenShift-ansible installer and not rely on the latest ansbile version pushed to epel repo we caused
> friction recently (reflected on our CI as well as users reporting issues)
>
>
> Thank you,
> PaaS SiG team
>
> [1] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/
> [2] https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/
> [3] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/
>
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel@centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel


_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
https://lists.centos.org/mailman/listinfo/centos-devel