Bug 1638521 - [3.10] Upgrade fails at "Set node schedulability"
Summary: [3.10] Upgrade fails at "Set node schedulability"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 3.10.z
Assignee: Michael Gugino
QA Contact: liujia
URL:
Whiteboard:
Depends On: 1614650
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-11 19:25 UTC by Scott Dodson
Modified: 2022-03-13 15:44 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1614650
Environment:
Last Closed: 2018-11-11 16:39:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2709 0 None None None 2018-11-11 16:40:16 UTC

Comment 3 sheng.lao 2018-10-24 13:50:20 UTC
Verified on openshift-ansible-3.10.62-1.git.0.563a1ec.el7.noarch.rpm

Scenario 3 (PASSED)

1) Scale up failed: set openshift_kubelet_name_override and get
TASK [Fail when openshift_kubelet_name_override is defined] ********************
fatal: [xxx.amazonaws.com]: FAILED! => {"changed": false, "msg": "openshift_kubelet_name_override Cannot be defined for new hosts"}
	to retry, use: --limit @~/playbooks/openshift-node/scaleup.retry


2) Scale up success: remove openshift_kubelet_name_override then play again  
and check with
  a) oc new-app centos/ruby-25-centos7~https://github.com/sclorg/ruby-ex.git -l appnew=new_node 

  b) oc get pod 
NAME              READY     STATUS      RESTARTS   AGE
ruby-ex-1-5pl8k   1/1       Running     0          41s
ruby-ex-1-build   0/1       Completed   0          1m

  c) oc get pod ruby-ex-1-5pl8k -o yaml |grep -i node
    appnew: new_node
  nodeName: ip-172-18-xxx.yyy.ec2.internal

Comment 5 errata-xmlrpc 2018-11-11 16:39:26 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/RHSA-2018:2709


Note You need to log in before you can comment on or make changes to this bug.