Bug 1907691
Summary: | [CNV] Configuring NodeNetworkConfigurationPolicy caused "Internal error occurred" for creating datavolume | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Container Native Virtualization (CNV) | Reporter: | Yan Du <yadu> | ||||||||||
Component: | Networking | Assignee: | Petr Horáček <phoracek> | ||||||||||
Status: | CLOSED ERRATA | QA Contact: | Ofir Nash <onash> | ||||||||||
Severity: | high | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 2.6.0 | CC: | cnv-qe-bugs, onash, ycui | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | 2.6.0 | ||||||||||||
Hardware: | Unspecified | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | kubernetes-nmstate-handler-container-v2.6.0-14 | Doc Type: | If docs needed, set a value | ||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2021-03-10 11:22:41 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: |
|
Description
Yan Du
2020-12-15 02:08:01 UTC
Yan, thanks for reporting this. Could you please share contents of `oc get nns -o yaml` before and after the configuration of NNCP? Would you also record on which nodes are CDI and HCO running? Created attachment 1739619 [details]
pod status in openshift-cnv ns
Created attachment 1739621 [details]
nns contents after configuration
Hi, Petr I attached the pod status and nns contents of post-configuration in attachment (I have preserved the cluster for debugging if needed). For the nns contents before configuration, is it ok to attach a fresh installed cluster's nns? Petr, may be related to https://bugzilla.redhat.com/show_bug.cgi?id=1904889 I don't think we got the fix for CNV yet. Thanks Yan, Meni. I just (re-)attached the fixed version of nmstate to D/S. It should be soon available in errata as kubernetes-nmstate-handler-container-v2.6.0-11. Could we retry once it is available and see if this issue persists? Verified. Checked Scenario: 1. Config the NNCP (attached nncp.yaml). 2. Apply the NNCP - `oc apply -f nncp.yaml` 3. Get Status of NNCP- Success: [cnv-qe-jenkins@network03-9n2rz-executor bug-nncp-dv]$ oc get nncp NAME STATUS br3-nncp SuccessfullyConfigured 4. Create dv from attached dv.yaml - `oc create -f dv.yaml` 5. DV created successfully with NNCP configured and no errors: [cnv-qe-jenkins@network03-9n2rz-executor bug-nncp-dv]$ oc create -f dv.yaml datavolume.cdi.kubevirt.io/import-dv-http created 6. Checked also that hco-webhook and hco-operator pods are running after the creation. * Checked also that VM creation works (came up from the orginal bug). Created attachment 1744329 [details]
NNCP Example for Verification
Created attachment 1744330 [details]
DV Example for Verification
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 (Moderate: OpenShift Virtualization 2.6.0 security and bug fix update), 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/RHSA-2021:0799 |