‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, January 6, 2019 11:13 PM, Joel Pearson
<[email protected]> wrote:
> It looks like the RPMs will eventually get the security fix according to the
> other reply from Daniel Comnea. But with containers you could have a fix
> within a day as opposed to waiting for new tag which still hasn’t happened
> yet and it’s been more than 1 month.
That's good to know that it will eventually get fixed but with security
vulnerabilities 1 month is already too long.
> The upgrade procedure is the same as RPMs, however you wouldn’t need to
> change the rpm repo.
That's great! So this means that the OpenShift Ansible upgrade.yml playbook
detects if the node is using CentOS+RPMs or Atomic Host+Docker and then
upgrades using the correct way? or is there any special parameter I need for
example in my Ansible inventory file to let the playbook know that I would be
using Atomic Host?
>>> On Sun, 6 Jan 2019 at 07:03, mabi <[email protected]> wrote:
>>>
>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>> On Saturday, January 5, 2019 3:57 PM, Daniel Comnea
>>>> <[email protected]> wrote:
>>>>
>>>>> [DC]: i think you are a bit confused: there are 2 ways to get the rpms
>>>>> from CentOS yum repo: using the generic repo [1] which will always have
>>>>> the latest origin release OR [2] where i've mentioned that you can
>>>>> install centos-release-openshift-origin3* rpm which will give you [3] yum
>>>>> repo
>>>>
>>>> Thank you for your precisions and yes I am confused because first of all
>>>> the upgrading documentation on the okd.io website does not mention
>>>> anything about having to manually change the yum repo.repos.d file to
>>>> match a new directory for a new version of openshift.
>>>>
>>>> Then second, this mail
>>>> (https://lists.openshift.redhat.com/openshift-archives/users/2018-November/msg00007.html)
>>>> has the following sentence, I quote:
>>>>
>>>> "Please note that due to ongoing work on releasing CentOS 7.6, the
>>>> mirror.centos.org repo is in freeze mode - see [4] and as such we have not
>>>> published the rpms to [5]. Once the freeze mode will end, we'll publish
>>>> the rpms."
>>>>
>>>> So when is the freeze mode over for this repo? I read this should have
>>>> happened after the CentOS 7.6 release but that was already one month ago
>>>> and still no version 3.11 RPMs in the
>>>> http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/ repo...
>>>>
>>>> Finally, all I want to do is to upgrade my current okd version 3.10 to
>>>> version 3.11 but I can't find any complete instructions documented
>>>> correctly. The best I can find is
>>>> https://docs.okd.io/3.11/upgrading/automated_upgrades.html which simply
>>>> mentions running the following upgrade playbook:
>>>>
>>>> ansible-playbook \
>>>> -i </path/to/inventory/file> \
>>>> playbooks/byo/openshift-cluster/upgrades/<version>/upgrade.yml
>>>>
>>>> Again here there is no mention of having to modify a yum.repos.d file
>>>> beforehand or having to install the centos-release-openshift-origin
>>>> package...
>>>>
>>>> I would be glad if someone can clarify the full upgrade process and/or
>>>> have the official documentation enhanced.
>>>> _______________________________________________
>>>> users mailing list
>>>> [email protected]
>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
> --
> Kind Regards,
>
> Joel Pearson
> Agile Digital | Senior Software Consultant
>
> Love Your Software™ | ABN 98 106 361 273
> p: [1300 858 277](tel:1300%20858%20277) | m: [0405 417 843](tel:0405417843) |
> w: [agiledigital.com.au](http://agiledigital.com.au/)
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
