Bug 1822315
Summary: | status.desiredState: doesn't pick the correct value and is null | ||
---|---|---|---|
Product: | Container Native Virtualization (CNV) | Reporter: | Geetika Kapoor <gkapoor> |
Component: | Networking | Assignee: | Quique Llorente <ellorent> |
Status: | CLOSED ERRATA | QA Contact: | Geetika Kapoor <gkapoor> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 2.3.0 | CC: | cnv-qe-bugs, ellorent, ncredi, phoracek |
Target Milestone: | --- | ||
Target Release: | 2.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | kubernetes-nmstate-handler-container-v2.4.0-31 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-28 19:09: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: |
Description
Geetika Kapoor
2020-04-08 17:37:38 UTC
Quique, would you please help me understand this issue? Is there a workaround? Should we expect it happening on production environment? What is causing it? Have we test this with latest CNV version ? we added some fixes to kubernetes-nmstate before freezy last friday. Knmstate is not rejecting the policy with a missing desiredState, looking at _types.go from policy it's not marked as optional so it's suppos to be requiered we have to investigate will be fixed at cnv 2.4 since this is not a blocker. I have apply the policy at the bug at CNV 2.4 and we validating it as expected so we can close this bug. The NodeNetworkConfigurationPolicy "nncp-default-host" is invalid: spec.desiredState: Invalid value: "null": spec.desiredState in body must be of type object: "null" Test Environment: Old versions: ============= $ oc get csv -n openshift-cnv | awk ' { print $4 } ' | tail -n1 2.3.0 1. Setup using config file mentioned in attachment. 2. Run oc apply. $ oc apply -f test.yaml nodenetworkconfigurationpolicy.nmstate.io/nncp-default-host created 3. Check status of nncp $ oc get nncp NAME STATUS nncp-default-host ConfigurationProgressing It is kind of hanged in this intermediate state. New versions: ============ $ oc get csv -n openshift-cnv | awk ' { print $4 } ' | tail -n1 2.4.0 $ oc apply -f test.yaml The NodeNetworkConfigurationPolicy "nncp-default-host" is invalid: spec.desiredState: Invalid value: "null": spec.desiredState in body must be of type object: "null" It is failing when we try to apply the policy so nncp is not getting created. Please add 'fixed in version' 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/RHSA-2020:3194 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |