Do you suggest to use a tagged version of the openshift ansible git repo combined with such parameters within the inventory ?
E.g git clone -b https://github.com/openshift/openshift-ansible/releases/tag/openshift-ansible-3.7.38-1 inventory ======= openshift_repos_enable_testing = true containerized = false openshift_release = v3.7 openshift_pkg_version = "-3.7.0-1.0.7ed6862" # See -> https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ openshift_deployment_type = origin ... ansible-playbook -i inventory openshift-ansible/playbooks/byo/config.yml On Fri, Mar 16, 2018 at 8:44 PM, Michael Gugino <[email protected]> wrote: > I would start again with new hosts, probably the easiest way forward. > I recommend using the released versions if you are not comfortable > with troubleshooting openshift-ansible. > > On Fri, Mar 16, 2018 at 3:29 PM, Charles Moulliard <[email protected]> > wrote: > > Yep. I did a mistake but I have cleaned my machine and did a new > deployment > > but we a get weird error again > > > > INSTALLER STATUS > > ************************************************************ > ************************************************************ > ************************************************************ > ******************************** > > Initialization : Complete > > Health Check : Complete > > etcd Install : Complete > > Master Install : Complete > > Master Additional Install : Complete > > Node Install : In Progress > > This phase can be restarted by running: > > playbooks/byo/openshift-node/config.yml > > > > > > > > Failure summary: > > > > > > 1. Hosts: 192.168.99.50 > > Play: Configure nodes > > Task: Install sdn-ovs package > > Message: Error: Package: origin-sdn-ovs-3.7.0-1.0.7ed6862.x86_64 > > (centos-openshift-origin37) > > Requires: origin-node = 3.7.0-1.0.7ed6862 > > Installed: > > origin-node-3.7.1-1.el7.git.0.0a2d6a1.x86_64 > > (@centos-openshift-origin37-testing) > > origin-node = 3.7.1-1.el7.git.0.0a2d6a1 > > Available: > > origin-node-v3.7.1-0.3.7.1.el7.git.0.b113c29.x86_64 > > (centos-openshift-origin37-testing) > > > > So it seems that the version calculated and downloaded from this repo > > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ > is not > > consistent > > > > Is there a way to download / install properly all the required origin > rmps > > as ansible playbook fails ? > > > > > > On Fri, Mar 16, 2018 at 8:24 PM, Michael Gugino <[email protected]> > wrote: > >> > >> Charles, > >> > >> You cannot install 3.9 from the openshift-ansible 3.7 branch. If > >> you want to install 3.9, you need to use the openshift-ansible 3.9 > >> branch, which is not officially released yet. > >> > >> There is not a testing repo for each release of openshift; just the > >> latest unreleased version. If you enable testing repos on the 3.7 > >> branch, you'll end up getting 3.9 packages which is what's happening > >> here. > >> > >> On Fri, Mar 16, 2018 at 11:32 AM, Charles Moulliard < > [email protected]> > >> wrote: > >> > Hi, > >> > > >> > Are the OpenShift Origin v3.9 rpms available from a repo ? > >> > How can we get them in order to install openshift cluster using > ansible > >> > playbook ? > >> > > >> > Regards > >> > > >> > Charles > >> > > >> > _______________________________________________ > >> > dev mailing list > >> > [email protected] > >> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > >> > > >> > >> > >> > >> -- > >> Michael Gugino > >> Senior Software Engineer - OpenShift > >> [email protected] > >> 540-846-0304 > > > > > > > > -- > Michael Gugino > Senior Software Engineer - OpenShift > [email protected] > 540-846-0304 >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
