Bug 1659376
Summary: | [Next_gen_installer]apiserver pod cannot be running in multitenant plugin mode | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | zhaozhanqi <zzhao> |
Component: | Networking | Assignee: | Casey Callendrello <cdc> |
Status: | CLOSED ERRATA | QA Contact: | zhaozhanqi <zzhao> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.1.0 | CC: | aos-bugs, bbennett, bmeng, cdc, sponnaga, wsun |
Target Milestone: | --- | Keywords: | TestBlocker |
Target Release: | 4.1.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:41:16 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
zhaozhanqi
2018-12-14 08:19:33 UTC
Good catch! Looks like we might need to set up some default joins. Either this code will need to be in the operator or the controller. Jacob, can you take a look at this? Dan Winship can help figure out how to fix it. Created SDN-284 to track this. This is not a beta blocker since the default network plugin for 4.0 is the network policy one, and that one works. The guidance is "if the problem does not get exposed by the high-touch beta lab manual (https://docs.google.com/document/d/1wcOglOXsfHjcXearZhxnWnyeCJ_y1c3qC4_ZE18b00c/edit#) then it is a bug, but not a beta blocker". This is fixed in https://github.com/openshift/cluster-network-operator/pull/82 PR is merged, ready for QA. this issue had been fixed on 4.0.0-0.nightly-2019-02-18-224151 this bug can be verified. Tested this issue on 4.0.0-0.nightly-2019-02-18-224151,it had been fixed. this bug can be verified. Verified this bug according to comment#8 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-2019:0758 |