Bug 1781695 - release-openshift-ocp-installer-e2e-gcp-ovn-4.3: DaemonSet \"openshift-multus/multus-admission-controller\" is not yet scheduled on any nodes
Summary: release-openshift-ocp-installer-e2e-gcp-ovn-4.3: DaemonSet \"openshift-multus...
Keywords:
Status: CLOSED DUPLICATE of bug 1779863
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3.0
Assignee: Antonio Murdaca
QA Contact: Michael Nguyen
URL:
Whiteboard:
: 1781694 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-10 12:21 UTC by Jan Chaloupka
Modified: 2019-12-10 17:00 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-10 17:00:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Chaloupka 2019-12-10 12:21:57 UTC
Description of problem:

https://prow.svc.ci.openshift.org/job-history/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-ovn-4.3 has been failing for some time with the following log:

Installing from release registry.svc.ci.openshift.org/ocp/release:4.3.0-0.nightly-2019-12-10-103826
level=warning msg="Found override for release image. Please be warned, this is not advised"
level=info msg="Consuming Install Config from target directory"
level=info msg="Creating infrastructure resources..."
level=info msg="Waiting up to 30m0s for the Kubernetes API at https://api.ci-op-k6btpf44-f342c.origin-ci-int-gce.dev.openshift.com:6443..."
level=info msg="API v1.16.2 up"
level=info msg="Waiting up to 30m0s for bootstrapping to complete..."
level=info msg="Cluster operator network Progressing is True with Deploying: DaemonSet \"openshift-multus/multus-admission-controller\" is not yet scheduled on any nodes"
level=info msg="Pulling debug logs from the bootstrap machine"
level=info msg="Bootstrap gather logs captured here \"/tmp/artifacts/installer/log-bundle-20191210112839.tar.gz\""
level=fatal msg="Bootstrap failed to complete: failed to wait for bootstrapping to complete: timed out waiting for the condition"

Checking logs from apiserver and scheduler operators I get "0/3 nodes are available: 3 node(s) had taints that the pod didn't tolerate.". Node taints still contain NoSchedule:node.kubernetes.io/network-unavailable taint. Also, after checking 34c0ee99a5c4.log under https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-ovn-4.3/64/artifacts/e2e-gcp/installer/log-bundle-20191210112839.tar I see a lot of the following lines:

"99_openshift-machineconfig_99-master-ssh.yaml": unable to get REST mapping for "99_openshift-machineconfig_99-master-ssh.yaml": no matches for kind "MachineConfig" in version "machineconfiguration.openshift.io/v1"

Could be something wrong with the way machine config CRDs are deployed?

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-12-10-103826

How reproducible:
Always

Steps to Reproduce:
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-ovn-4.3/64

Actual results:
DaemonSet \"openshift-multus/multus-admission-controller\" is not yet scheduled on any nodes

Expected results:
DaemonSet \"openshift-multus/multus-admission-controller\" is scheduled

Additional info:

Comment 1 Jan Chaloupka 2019-12-10 12:26:07 UTC
*** Bug 1781694 has been marked as a duplicate of this bug. ***

Comment 2 Jan Chaloupka 2019-12-10 17:00:31 UTC

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


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