Description of problem: Upgrade ocp v3.10.45 to latest v3.10 failed at task [Read node config] due to original /etc/origin/node/node-config.yaml was removed and renamed to bootstrap-node-config.yaml in previous task [openshift_node : Remove non-bootstrap configuration]. Failure summary: 1. Hosts: compute-1 Play: Initialize cluster facts Task: Read node config Message: file not found: /etc/origin/node/node-config.yaml TASK [openshift_node : Remove non-bootstrap configuration] ********************* task path: /usr/share/ansible/openshift-ansible/roles/openshift_node/tasks/upgrade/bootstrap_changes.yml:38 Tuesday 16 October 2018 07:47:17 +0000 (0:00:01.546) 0:12:44.340 ******* changed: [compute-1] => (item=/etc/origin/node/node.kubeconfig) => {"changed": true, "failed": false, "item": "/etc/origin/node/node.kubeconfig", "path": "/etc/origin/node/node.kubeconfig", "state": "absent"} changed: [compute-1] => (item=/etc/origin/node/node-config.yaml) => {"changed": true, "failed": false, "item": "/etc/origin/node/node-config.yaml", "path": "/etc/origin/node/node-config.yaml", "state": "absent"} <--snip--> TASK [Read node config] ******************************************************** task path: /usr/share/ansible/openshift-ansible/playbooks/init/cluster_facts.yml:75 Tuesday 16 October 2018 08:03:47 +0000 (0:00:00.082) 0:29:14.727 ******* fatal: [compute-1]: FAILED! => {"changed": false, "failed": true, "msg": "file not found: /etc/origin/node/node-config.yaml"} [root@ip-172-18-7-37 ~]# ls -la /etc/origin/node/|grep node -rw-r--r--. 1 root root 1607 Oct 16 07:47 bootstrap-node-config.yaml -rw-------. 1 root root 1946 Oct 16 07:48 node.kubeconfig Version-Release number of the following components: openshift-ansible-3.10.57-1.git.0.787bf7c.el7.noarch How reproducible: always Steps to Reproduce: 1. Upgrade old version ocp v3.10(for example,latest release version v3.10.45) to latest v3.10 2. 3. Actual results: Upgrade failed. Expected results: Upgrade succeed. Additional info: Please attach logs from ansible-playbook with the -vvv flag
This is due to race condition or faulty sync pod. Investigating.
Hi, Ran into the same issue as at 3.9 had ansible service broker and during upgrade to 3.10 the combined upgrade playbook failed at upgrading the ASB. When tried to re-run the upgrade playbook it failed with the following error as well: {"changed": false, "msg": "file not found: /etc/origin/node/node-config.yaml"} It must have been some tmp/cached ansible playbook on the hosts/nodes or something similar as after I rebooted all VM hosts in the OCP infra and re-run the playbook it now carries on with the upgrade... I hope this helps. BTW: If you ran the upgrade playbook and it reached a certain point but failed it would mean that the file node-config.yaml is no longer there as your node info is now in node.kubeconfig... Thanks, @lo3k
https://github.com/openshift/openshift-ansible/pull/10734
Verified on openshift-ansible-3.10.82-1.git.0.fcfab8f.el7.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3743
Hi, the target release of this BZ is 3.11 but the original issue was reported with 3.10.72. According to the c#12, this fix will be included at the next 3.10.z release, after 3.10.82?
Verified on openshift-ansible-3.11.51-1.git.0.51c90a3.el7.noarch too. So this fix should be available for both latest release v3.11 and next release 3.10(after v3.10.82). According to bz1653446, it will be tracked in this bug for next release 3.10.z.