[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: OKD 3.9 to 3.10 upgrade failure on CentOS

Hi Dharmit,

What you're experiencing looks a lot like a problem I had with the upgrade. I ended up doing a fresh install.

I've tried fiddling around with the ansible config and as I was trying to get my head about what was happening I discovered an issue about node names. With this reply from Michael Gugino that shed some light on the matter: https://github.com/openshift/openshift-ansible/issues/9935#issuecomment-423268110

Basically my problem was that the upgrade playbook of OKD 3.10 expected that the node names from the previously isntalled version be the short name versions and not the FQDN.

I guess I was precisely in your position and I really didn't know what else to try except doing a fresh install. I have no idea if there is a way of changing node names of a running cluster. Maybe someone who knows more about the internals could be of help in this respect...

Since I see your installation is also a fresh one, maybe it would worth uninstalling 3.9 and installing the 3.10. Or maybe have a try at the newest 3.11.

Hope it helps,


On 20.11.2018 04:38, Dharmit Shah wrote:

I'm trying to upgrade my OKD 3.9 cluster to 3.10 using
openshift-ansible. I have already described the problem in detail and
provided logs on the GitHub issue [1].

I could really use some help on this issue!


[1] https://github.com/openshift/openshift-ansible/issues/10690

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]