I tried: [OSEv3:vars] ansible_ssh_user=root deployment_type=origin openshift_pkg_version=-1.2.0 openshift_image_tag=-1.2.0
But it installed a release canidad and not v1.2.0 oc v1.2.0-rc1-13-g2e62fab kubernetes v1.2.0-36-g4a3f9c5 From: [email protected] To: [email protected] Subject: RE: define openshift origin version (stable 1.2.0) for Ansible install Date: Wed, 22 Jun 2016 12:51:18 +0000 CC: [email protected] Thanks for your fast reply This is the beginning of my playbook: [OSEv3:vars] ansible_ssh_user=root deployment_type=origin openshift_pkg_version=v1.2.0 openshift_image_tag=v1.2.0 But I got an error: TASK [openshift_master_ca : Install the base package for admin tooling] ******** FAILED! => {"changed": false, "failed": true, "msg": "No Package matching 'originv1.2.0' found available, installed or updated", "rc": 0, "results": []} From: [email protected] Date: Wed, 22 Jun 2016 13:53:57 +0200 Subject: Re: define openshift origin version (stable 1.2.0) for Ansible install To: [email protected] CC: [email protected] Personally I use this options to fix OpenShift version: openshift_pkg_version=v1.2.0 openshift_image_tag=v1.2.0 2016-06-22 13:24 GMT+02:00 Den Cowboy <[email protected]>: Is it possible to define and origin version in your ansible install. At the moment we have so many issues with our newest install (while we had 1.1.6 pretty stable for some time) We want to go to a stable 1.2.0 Our issues: version = oc v1.2.0-rc1-13-g2e62fab So images are pulled with tag oc v1.2.0-rc1-13-g2e62fab which doesn't exist in openshift. Okay we have a workaround by editing the master and node config's and using 'i--image' but whe don't like this approach logs on our nodes: level=error msg="Error reading loginuid: open /proc/27182/loginuid: no such file or directory" level=error msg="Error reading loginuid: open /proc/27182/loginuid: no such file or directory" We started a mysql instance. We weren't able to use the service name to connect: mysql -u test -h mysql -p did NOT work mysql -u test -h 172.30.x.x (service ip) -p did work.. So we have too many issues on this version of OpenShift. We've deployed in a team several times and are pretty confident with the setup and it was always working fine for us. But now this last weird versions seem really bad for us. _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users -- Stéphane Klein <[email protected]> blog: http://stephane-klein.info cv : http://cv.stephane-klein.info Twitter: http://twitter.com/klein_stephane _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
