Bug 1819726
| Summary: | Bridge network interface only created on one node, and not another. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Tomasz Barański <tbaransk> | ||||||||
| Component: | Networking | Assignee: | Quique Llorente <ellorent> | ||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Meni Yakove <myakove> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 2.3.0 | CC: | cnv-qe-bugs, ncredi, phoracek | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | future | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2020-09-03 12:12:47 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: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 1675388 [details]
Node network config policy
Created attachment 1675389 [details]
Longs fro nmstate-handler-worker
Thanks Tomasz! Since this is not the only issue with reporting on knmstate, we may be able to piggy-pack it to 2.3. We will need an ack for blocker though. Taking a second look. This happened only on virtualized provider and we were not able to reproduce it. I'm moving it to future and keeping this in case we reproduce it on D/S. should this move back to NEW? Please feel to reopen this if it happens again. |
Created attachment 1675387 [details] netutil daemonset spec Description of problem: I'm running cnv-tests on a local kubevirtci cluster using k8s-1.17 provider. A lot of networking test fails due to failure creating bridge network. I was able to narrow down the problem to failure in applying the following policy: {'apiVersion': 'nmstate.io/v1alpha1', 'kind': 'NodeNetworkConfigurationPolicy', 'metadata': {'name': 'test-network-operator'}, 'spec': {'desiredState': {'interfaces': [{'name': 'br1test', 'type': 'linux-bridge', 'state': 'up', 'bridge': {'options': {'stp': {'enabled': False}}, 'port': []}}]}}} How reproducible: 100% Steps to Reproduce: 1. Start kubevirt cluster (cd kubevirtci; make cluster-up; cd cnv-tests; UPSTREAM=1 make cluster-install-hco) 2. Create netutils daemonset (kubectl create -f netutil-deamon-set.yaml, attached) 3. Create namespace (kubectl create namespace cluster-addons-operator-test-network-addons-operator) 4. Create policy (kubectl create -f node-network-config.yaml, attached) Actual results: Interface br1test created on node01 but not on node02. Expected results: Interface br1test created on node01 and node02. Additional info: $ export | grep KUBE declare -x KUBEVIRT_NUM_NODES="2" declare -x KUBEVIRT_NUM_SECONDARY_NICS="1" declare -x KUBEVIRT_PROVIDER="k8s-1.17"