Bug 1653446

Summary: [3.10] Upgrade failed when hostname check due to /etc/origin/node/node-config.yaml was not available
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: Cluster Version OperatorAssignee: Russell Teague <rteague>
Status: CLOSED NOTABUG QA Contact: liujia <jiajliu>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.10.0CC: akaiser, aos-bugs, cshereme, cstark, fhirtz, jdesousa, jiajliu, jkaur, jmalde, jokerman, lo3k.nfsec, mgugino, mirwin, mmccomas, openshift-bugs-escalate, pkanthal, rekhan, rhowe, sdodson, travi
Target Milestone: ---Keywords: Reopened
Target Release: 3.10.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1639655 Environment:
Last Closed: 2019-06-07 18:59:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1639655    
Bug Blocks:    

Comment 2 Scott Dodson 2018-12-12 16:25:01 UTC
In openshift-ansible-3.10.80-1 and later.

Comment 3 liujia 2018-12-13 04:03:58 UTC
Verified on openshift-ansible-3.10.82-1.git.0.fcfab8f.el7.noarch

Keep ON_QA status to wait for a available advisory including this fix.

Comment 4 Scott Dodson 2018-12-13 21:48:50 UTC
openshift-ansible-3.10.83-1.git.0.12699eb.el7 just shipped today which should include the fix, moving to closed errata based on comment 3

Comment 5 Candace Sheremeta 2018-12-13 22:18:11 UTC
https://access.redhat.com/errata/RHBA-2018:3750

Comment 6 Wojciech Orlowski 2018-12-14 15:44:16 UTC
Hi,

Thank you publishing new packages last night.

I have tested them this morning... and this issue persist.


On the task:
TASK [Read node config] ********************************************************
task path: /usr/share/ansible/openshift-ansible/playbooks/init/cluster_facts.yml:76

The upgrade_control_plane.yaml playbook still fails in condition when masters node-config.yaml has been already changed to node.kubeconfig and node-config.yaml no longer exists.

Related to my previous note... https://bugzilla.redhat.com/show_bug.cgi?id=1639655

This condition occurred for example after playbook failed first time but managed to convert (from 3.9 to 3.10) etc/controllers/api into containers, but then playbook fails and another playbook re-run causes the break on this TASK.

In version openshift-ansible-3.10.72*.rpm I tried to create a dummy empty file /etc/origin/node/node-config.yaml on my 3 masters and re-run the playbook but it failed each time.

In version openshift-ansible-3.10.83*.rpm I tried to run the patched upgrade_control_plane.yaml playbook and it failed on this TASK, however creating a dummy file again /etc/origin/node/node-config.yaml and re-running the playbook worked and my upgrade is now complete.

Perhaps the additional workaround is STILL to add dummy file (https://access.redhat.com/solutions/3712171) despite the workaround...


Thanks,
@lo3k

Comment 19 Red Hat Bugzilla 2023-09-15 00:14:13 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days