Bug 1748268 - [ci] vSphere UPI cluster is not ready for e2e test
Summary: [ci] vSphere UPI cluster is not ready for e2e test
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.3.0
Assignee: Stefan Schimanski
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-03 09:09 UTC by Wenjing Zheng
Modified: 2019-11-06 13:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-06 13:13:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Wenjing Zheng 2019-09-03 09:09:03 UTC
Description of problem:
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/canary-openshift-ocp-installer-e2e-vsphere-upi-4.2/31
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/canary-openshift-ocp-installer-e2e-vsphere-upi-4.2/38

vSphere UPI cluster is not ready for e2e test:
openshift-cluster-version/cluster-version-operator\" (8 of 416): the server does not recognize this resource, check extension API servers\n* Could not update servicemonitor \"openshift-controller-manager-operator/openshift-controller-manager-operator\" (415 of 416): the server does not recognize this resource, check extension API servers\n* Could not update servicemonitor \"openshift-image-registry/image-registry\" (381 of 416): the server does not recognize this resource, check extension API servers\n* Could not update servicemonitor \"openshift-kube-apiserver-operator/kube-apiserver-operator\" (392 of 416): the server does not recognize this resource, check extension API servers\n* Could not update servicemonitor \"openshift-kube-controller-manager-operator/kube-controller-manager-operator\" (396 of 416): the server does not recognize this resource, check extension API servers\n* Could not update servicemonitor \"openshift-kube-scheduler-operator/kube-scheduler-operator\" (400 of 416): the server does not recognize this resource, check extension API servers\n* Could not update servicemonitor \"openshift-machine-api/cluster-autoscaler-operator\" (151 of 416): the server does not recognize this resource, check extension API servers\n* Could not update servicemonitor \"openshift-machine-api/machine-api-operator\" (402 of 416): the server does not recognize this resource, check extension API servers\n* Could not update servicemonitor \"openshift-operator-lifecycle-manager/olm-operator\" (405 of 416): the server does not recognize this resource, check extension API servers\n* Could not update servicemonitor \"openshift-service-catalog-apiserver-operator/openshift-service-catalog-apiserver-operator\" (384 of 416): the server does not recognize this resource, check extension API servers\n* Could not update servicemonitor \"openshift-service-catalog-controller-manager-operator/openshift-service-catalog-controller-manager-operator\" (387 of 416): the server does not recognize this resource, check extension API servers"

I checked latest four below accepted build, this issue happens twice:
4.2.0-0.nightly-2019-09-02-172410 (Yes)
4.2.0-0.nightly-2019-09-02-162943 (No)
4.2.0-0.nightly-2019-08-31-102058 (Yes)
4.2.0-0.nightly-2019-08-31-063119 (No)

Version-Release number of the following components:

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Additional info:

Comment 1 Abhinav Dahiya 2019-09-03 16:20:00 UTC
The kube-controller-manager and kube-scheduler are degraded.

Comment 6 Michal Fojtik 2019-09-04 09:17:28 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1748798 looks to have similar errors in etcd?


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