Bug 1691600

Summary:	false failure in kube-scheduler operator update
Product:	OpenShift Container Platform	Reporter:	Ryan Cook <rcook>
Component:	Node	Assignee:	Seth Jennings <sjenning>
Status:	CLOSED DUPLICATE	QA Contact:	Jianwei Hou <jhou>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	4.1.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:	2019-03-26 03:14:02 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 Ryan Cook 2019-03-22 02:43:26 UTC

Description of problem: Preformed full OpenShift update using console from .6 -> .7 but only one update failed kube-scheduler


Version-Release number of selected component (if applicable):


How reproducible: Deploy new cluster of .6 and then patch to .7


Steps to Reproduce:
1. login to the console
2. administration -> cluster settings
3. click update

Actual results:

kube-scheduler states failed NodeInstallerFailing: 0 nodes are failing on revision 1: NodeInstallerFailing:

Expected results: Not failed


Additional info:
8m        8m        1         openshift-kube-scheduler-operator.158e26fc7230b9bf   Deployment             Normal    SecretUpdated               openshift-cluster-kube-scheduler-operator   Updated Secret/kube-scheduler-client-cert-key-1 -n openshift-kube-scheduler because it changed
8m        8m        1         openshift-kube-scheduler-operator.158e26fc73295884   Deployment             Normal    RevisionCreate              openshift-cluster-kube-scheduler-operator   Revision 0 created because configmap "kube-scheduler-pod-0" not found
8m        8m        1         openshift-kube-scheduler-operator.158e26fd5419a05a   Deployment             Normal    ConfigMapUpdated            openshift-cluster-kube-scheduler-operator   Updated ConfigMap/kube-scheduler-pod -n openshift-kube-scheduler: cause by changes in data.pod.yaml
8m        8m        1         openshift-kube-scheduler-operator.158e26fd5466b5a3   Deployment             Normal    RevisionTriggered           openshift-cluster-kube-scheduler-operator   new revision 2 triggered by "configmap/kube-scheduler-pod has changed"
8m        8m        1         openshift-kube-scheduler-operator.158e26fd83ca13ed   Deployment             Normal    ConfigMapUpdated            openshift-cluster-kube-scheduler-operator   Updated ConfigMap/revision-status-2 -n openshift-kube-scheduler: cause by changes in data.status
8m        8m        1         openshift-kube-scheduler-operator.158e26fdb5264808   Deployment             Normal    NodeTargetRevisionChanged   openshift-cluster-kube-scheduler-operator   Updating node "ip-10-0-153-76.ec2.internal" from revision 0 to 1

oc get pods -n openshift-kube-scheduler-operator
NAME                                                 READY     STATUS    RESTARTS   AGE
openshift-kube-scheduler-operator-5f48c796c5-rm9th   1/1       Running   0          13m

Comment 1 Xingxing Xia 2019-03-26 03:14:02 UTC


*** This bug has been marked as a duplicate of bug 1690153 ***