Bug 1806115
| Summary: | nmstate: failed to create bridge on node | ||
|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Meni Yakove <myakove> |
| Component: | Networking | Assignee: | Quique Llorente <ellorent> |
| Status: | CLOSED ERRATA | QA Contact: | Meni Yakove <myakove> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.3.0 | CC: | aburden, atragler, cnv-qe-bugs, ncredi, phoracek, william.caban |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | 2.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | kubernetes-nmstate-handler-container-v2.3.0-24 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-04 19:10:56 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: | |||
@Petr: Does this indicate that nmstatectl had a problem applying the state or is this an internal error of kubernetes-nmstate? This issue is limited to kubernetes-nmstate, not related to nmstatectl in any way. Thanks for asking though! It seems that it may be a bug in the PSI cluster. Rhys Oxenham has tested latest CNV 2.3 on: Client Version: 4.4.0-0.nightly-2020-02-25-070402 Server Version: 4.4.0-0.nightly-2020-02-25-070402 Kubernetes Version: v1.17.1 He was successful creating a bridge via NodeNetworkConfigurationPolicy. Meni, could you test kubernetes-nmstate on a different cluster, maybe a bare-metal one? With Petr's help I was able to create a bridge on a node with an nncp. This was also using the latest cnv 2.3. Cluster is ocp 4.4 provisioned with kubevirtci: Client Version: openshift-clients-4.2.0-201910041700 Server Version: 4.4.0-0.nightly-2020-01-24-141203 Kubernetes Version: v1.17.1 tested with kubernetes-nmstate-handler-container-v2.3.0-21 still can't get NNCP to work, got the same error. verified on: container-native-virtualization-kubernetes-nmstate-handler-rhel8:v2.3.0-24 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/RHEA-2020:2011 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Description of problem: When applying: apiVersion: nmstate.io/v1alpha1 kind: NodeNetworkConfigurationPolicy metadata: name: veth-removed spec: desiredState: interfaces: - bridge: options: stp: enabled: false port: [] name: brtest1 state: up type: linux-bridge the operation failed with an error: kubernetes.client.rest.ApiException: (500) E Reason: Internal Server Error E HTTP response headers: HTTPHeaderDict({'Audit-Id': '79111695-64a8-4791-b830-c4df94244e51', 'Content-Type': 'application/json', 'Date': 'Sat, 22 Feb 2020 08:17:54 GMT', 'Content-Length': '341'}) E HTTP response body: b'{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Internal error occurred: admission plugin \\"MutatingAdmissionWebhook\\" failed to complete mutation in 13s","reason":"InternalError","details":{"causes":[{"message":"admission plugin \\"MutatingAdmissionWebhook\\" failed to complete mutation in 13s"}]},"code":500}\n' Additional info: To work around the issue we can delete mutatingwebhookconfiguration nmstate