Bug 1821429

Summary: WSU fails for v1.18.0-rc.1 kubernetes version
Product: OpenShift Container Platform Reporter: sumehta
Component: Windows ContainersAssignee: Mansi Kulkarni <mankulka>
Status: CLOSED ERRATA QA Contact: gaoshang <sgao>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.5CC: aos-bugs, gmarkley, rgudimet
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:25:52 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:

Description sumehta 2020-04-06 19:44:09 UTC
Description of problem:
WSU run fails for intermediate Kubernetes version like alpha or rc versions

Version-Release number of selected component (if applicable):
Server Version: 4.5.0-0.ci-2020-04-06-102537
Kubernetes Version: v1.18.0-rc.1

How reproducible:
Always

Steps to Reproduce:
1. Bring up a cluster with rc or alpha kube version like 4.5.0-0.ci-2020-04-06-102537
2. Bring up a Windows node
3. Run WSU

Actual results:
TASK [Get kube node binary SHA] **************************************************************************************************************************************************************************************************************
[WARNING]: Consider using the get_url or uri module rather than running 'curl'.  If you need to use command because get_url or uri is insufficient you can add 'warn: false' to this command task or set 'command_warnings=False' in
ansible.cfg to get rid of this message.
fatal: [localhost]: FAILED! => {"changed": true, "cmd": "curl -s \"https://github.com/kubernetes/kubernetes/blob/release-1.18.0-rc/CHANGELOG/CHANGELOG-1.18.0-rc.md\" | grep -A 1 \"v1.18.0-rc.1\" | grep -A 1 node-windows | tail -n 1 | sed -e 's/.*<code>\\(.*\\)<\\/code>.*/\\1/'\n", "delta": "0:00:00.558143", "end": "2020-04-06 15:09:23.196796", "failed_when_result": true, "rc": 0, "start": "2020-04-06 15:09:22.638653", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}


Expected results:
Playbook run completes successfully

Additional info:
WSU tries to hit the changelog url for checking the kube node SHA. For intermediary versions, this causes a problem because it is looking at https://github.com/kubernetes/kubernetes/blob/release-1.18.0-rc/CHANGELOG/CHANGELOG-1.18.0-rc.md instead of https://github.com/kubernetes/kubernetes/blob/release-1.18/CHANGELOG/CHANGELOG-1.18.md

Comment 3 gaoshang 2020-04-16 02:42:04 UTC
This bug has been verified and passed on OCP 4.5.0-0.nightly-2020-04-14-204706, thanks.

Version-Release number of selected component (if applicable):
Server Version: 4.5.0-0.nightly-2020-04-14-204706
Kubernetes Version: v1.18.0-rc.1
windows-machine-config-bootstrapper git commit: c003b7146a931bab0b9a306557f4d782c3556c7f

Steps:
1. Bring up a cluster with rc or alpha kube version like OCP 4.5.0-0.nightly-2020-04-14-204706
# oc version
Client Version: openshift-clients-4.2.0-201910041700
Server Version: 4.5.0-0.nightly-2020-04-14-204706
Kubernetes Version: v1.18.0-rc.1

2. Bring up a Windows node
3. Run WSU
Playbook run completes successfully

# oc get nodes
NAME                                         STATUS   ROLES    AGE     VERSION
ip-10-0-131-131.us-east-2.compute.internal   Ready    worker   22h     v1.17.1
ip-10-0-139-180.us-east-2.compute.internal   Ready    master   22h     v1.17.1
ip-10-0-154-255.us-east-2.compute.internal   Ready    master   22h     v1.17.1
ip-10-0-157-96.us-east-2.compute.internal    Ready    worker   22h     v1.17.1
ip-10-0-162-212.us-east-2.compute.internal   Ready    worker   22h     v1.17.1
ip-10-0-166-18.us-east-2.compute.internal    Ready    master   22h     v1.17.1
ip-10-0-33-191.us-east-2.compute.internal    Ready    worker   7h18m   v1.18.0-rc.1

Comment 4 errata-xmlrpc 2020-07-13 17:25:52 UTC
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-2020:2409