We've deployed OKD 3.11 successfully, and haven't seen any issues yet.

--

Antonio Lorenzo
Assistant Research Scientist
Department of Hydrology and Atmospheric Sciences
University of Arizona
Environment and Natural Resources 2, Room N576
https://forecasting.energy.arizona.edu

On Wed, 2018-10-31 at 11:43 -0400, [email protected] 
wrote:

Send users mailing list submissions to

        
[email protected]<mailto:[email protected]>


To subscribe or unsubscribe via the World Wide Web, visit

        http://lists.openshift.redhat.com/openshiftmm/listinfo/users

or, via email, send a message with subject or body 'help' to

        
[email protected]<mailto:[email protected]>


You can reach the person managing the list at

        
[email protected]<mailto:[email protected]>


When replying, please edit your Subject line so it is more specific

than "Re: Contents of users digest..."



Today's Topics:


   1. Re: [CentOS PaaS SIG]: Origin v3.11 rpms available for

      testing (Ricardo Martinelli de Oliveira)



----------------------------------------------------------------------


Message: 1

Date: Wed, 31 Oct 2018 12:42:41 -0300

From: Ricardo Martinelli de Oliveira 
<[email protected]<mailto:[email protected]>>

To: [email protected]<mailto:[email protected]>

Cc: users 
<[email protected]<mailto:[email protected]>>

Subject: Re: [CentOS PaaS SIG]: Origin v3.11 rpms available for

        testing

Message-ID:

        
<CALoi_rwm6KMDgsedHp=njkijadb11a017nuusk-6wqbfz1o...@mail.gmail.com<mailto:CALoi_rwm6KMDgsedHp=njkijadb11a017nuusk-6wqbfz1o...@mail.gmail.com>>

Content-Type: text/plain; charset="utf-8"


I'd like to ask anyone who deployed OKD 3.11 successfuly if you could reply

to this thread with your ack or nack. We need this feedback in order to

promote to -candidate and then the official CentOS repos.


On Fri, Oct 19, 2018 at 5:42 PM Anton Hughes 
<[email protected]<mailto:[email protected]>>

wrote:


Thanks Phil


I was using


openshift_release="v3.11"

openshift_image_tag="v3.11"

openshift_pkg_version="-3.11"


But should have been using


openshift_release="v3.11.0"

openshift_image_tag="v3.11.0"

openshift_pkg_version="-3.11.0"




On Sat, 20 Oct 2018 at 09:23, Phil Cameron 
<[email protected]<mailto:[email protected]>> wrote:


Go to

http://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/

in your web browser and you can see the names of all available rpms. It

appears the 3.11 rpms are 3.11.0


cd /etc/yum.repos.d

create a file, centos-okd-ci.repo

[centos-okd-ci]

name=centos-okd-ci

baseurl=

http://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/

gpgcheck=0

enabled=1


yum search origin-node

will list the available rpms


On 10/19/2018 04:09 PM, Anton Hughes wrote:


Hi Daniel


Unfortunately this is still not working for me. Im trying the method of

adding the repo using the inventory file, eg,


openshift_additional_repos=[{'id': 'centos-okd-ci', 'name':

'centos-okd-ci', 'baseurl' :'

http://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/',

'gpgcheck' :'0', 'enabled' :'1'}]


but I am getting the below error.


TASK [openshift_node : Install node, clients, and conntrack packages]

**************************************************************************************************

Saturday 20 October 2018  09:04:53 +1300 (0:00:02.255)       0:03:34.602

******

FAILED - RETRYING: Install node, clients, and conntrack packages (3

retries left).

FAILED - RETRYING: Install node, clients, and conntrack packages (2

retries left).

FAILED - RETRYING: Install node, clients, and conntrack packages (1

retries left).

failed: [xxx.xxx.xxx.xxx] (item={u'name': u'origin-node-3.11'}) =>

{"attempts": 3, "changed": false, "item": {"name": "origin-node-3.11"},

"msg": "No package matching 'origin-node-3.11' found available, installed

or updated", "rc": 126, "results": ["No package matching 'origin-node-3.11'

found available, installed or updated"]}

FAILED - RETRYING: Install node, clients, and conntrack packages (3

retries left).

FAILED - RETRYING: Install node, clients, and conntrack packages (2

retries left).

FAILED - RETRYING: Install node, clients, and conntrack packages (1

retries left).

failed: [xxx.xxx.xxx.xxx] (item={u'name': u'origin-clients-3.11'}) =>

{"attempts": 3, "changed": false, "item": {"name": "origin-clients-3.11"},

"msg": "No package matching 'origin-clients-3.11' found available,

installed or updated", "rc": 126, "results": ["No package matching

'origin-clients-3.11' found available, installed or updated"]}



On Sat, 20 Oct 2018 at 03:27, Daniel Comnea 
<[email protected]<mailto:[email protected]>>

wrote:


Hi all,


First of all sorry for the late reply as well as for any confusion i may

have caused with my previous email.

I was very pleased to see the vibe and excitement around testing OKD

v3.11, very much appreciated.


Here are the latest info:


   - everyone who wants to help us with testing should use [1] repo

   which can be consumed:

      -  in the inventory as [2] or

      - by deploying your own repo file [3]

   - nobody should use the repo i've mentioned in my previous email [4]

   (CentOS Infra team corrected me on the confusion i made, once again

   apologies for that)



Regarding the ansible version here are the info following my sync up

with CentOS Infra team:


   - very likely on Monday/ latest Tuesday a new rpm called

   centos-release-ansible26 will appear in CentOs Extras

   - the above rpm will become a dependency for the

   *centos-release-openshift-origin311* rpm which will be created and

   land in CentOS Extras repo at the same time OKD v3.11 will be promoted to

   mirror.centos.org

      - note this is the same flow as it was for all versions prior to

      v3.11 ( the rpm provides the CentOS repo location for OKD rpms).


*Note*:


   1. if your flow up until now was to never use

   *centos-release-openshift-originXXX* rpm and you were creating your

   own repo files then you will need to make sure you pull as dependency the

   ansible 2.6.x (together with its own dependencies) rpm. It is up to you

   from where you are going to pull the ansible rpm: from Epel, from CentOS

   Extras etc.

   2. with the above we are trying to have a single way of solving the

   ansible dependency problem



Hopefully this brings more clarity around this topic.




Thank you,

PaaS SiG team


[1] https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/


[2]


[OSEv3:vars]

(...)

openshift_additional_repos=[{'id': 'centos-okd-ci', 'name': 'centos-okd-ci', 
'baseurl' 
:'http://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/ 
<http://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311%7D/>', 
'gpgcheck' :'0', 'enabled' :'1'}]



[3]

[centos-openshift-origin311-testing]

name=CentOS OpenShift Origin Testing

baseurl=

http://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/

<http://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311%7D/>

enabled=0

gpgcheck=0

gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-PaaS


[4] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/




On Wed, Oct 17, 2018 at 10:38 AM Daniel Comnea 
<[email protected]<mailto:[email protected]>>

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.


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/


_______________________________________________

users mailing list

[email protected]<mailto:[email protected]>

http://lists.openshift.redhat.com/openshiftmm/listinfo/users




_______________________________________________

users mailing 
[email protected]<mailto:[email protected]>://lists.openshift.redhat.com/openshiftmm/listinfo/users



_______________________________________________

users mailing list

[email protected]<mailto:[email protected]>

http://lists.openshift.redhat.com/openshiftmm/listinfo/users


_______________________________________________

users mailing list

[email protected]<mailto:[email protected]>

http://lists.openshift.redhat.com/openshiftmm/listinfo/users




_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to