Bug 1697814
| Summary: | [network-operator]Multus pod cannot be running due to "ERROR: unknown parameter --multus-log-level" | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | zhaozhanqi <zzhao> |
| Component: | Networking | Assignee: | Douglas Smith <dosmith> |
| Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.1.0 | CC: | aos-bugs, chuyu, dosmith, xxia |
| Target Milestone: | --- | Keywords: | BetaBlocker, 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:47:18 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1690243, 1691055, 1695197, 1695209 | ||
|
Description
zhaozhanqi
2019-04-09 07:23:18 UTC
This is definitely a bug, but I don't think this is a testblocker for 1691055. What seems to be the issue there? The cause of this one is almost certainly an out of date Multus being built. If the operator has specified this parameter for log level, and the version of Multus being built doesn't have this parameter in the entrypoint script, then... This will happen. I'll dig up the details on what's being built and attempt to correct it. Details coming shortly. Looks like the commit in question is this commitish: 4aecbd21339aaa1c7874a5e71d3d9efc852fdfce I've taken a look at both https://github.com/openshift/ose-multus-cni & https://github.com/openshift/multus-cni -- apparently the openshift/ose-multus-cni:release branch does NOT have this commit. In theory, we should've been building from the openshift/multus-cni:master branch. In the meanwhile, I'm going to update the openshift/ose-multus-cni:release branch, and I'll get in touch with ART and verify where these are being built from. Ok, this is a build issue. Basically the gist is -- I need to have this commit reverted: https://github.com/openshift/ocp-build-data/commit/17e8a12042ff016191202af41484ea6bf3c79b25 This is related to this JIRA ticket @ https://jira.coreos.com/browse/ART-501 . This was closed 5 days ago, explaining why this is happening now. We submitted a PR to fix the issue in that JIRA ticket ourselves: https://github.com/openshift/ocp-build-data/pull/49 and then the referenced commit essentially un-did the changes in this PR. Should be fixed in the build, per this merged PR: https://github.com/openshift/ocp-build-data/pull/77 Verified this bug on 4.0.0-0.nightly-2019-04-10-182914 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 |