-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.13.z, 4.12.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Low
-
No
-
None
-
None
-
CNF Compute Sprint 281, CNF Compute Sprint 282
-
2
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
A test failed to find expected NRO object's Status aligned with NRO object's Spec:
[2023-07-10T14:43:50.510Z] [serial][disruptive][slow] numaresources configuration management [2023-07-10T14:43:50.510Z] /go/src/github.com/openshift-kni/numaresources-operator/test/e2e/serial/tests/configuration.go:64 [2023-07-10T14:43:50.510Z] cluster has at least one suitable node [2023-07-10T14:43:50.510Z] /go/src/github.com/openshift-kni/numaresources-operator/test/e2e/serial/tests/configuration.go:100 [2023-07-10T14:43:50.510Z] [It] should report the NodeGroupConfig in the status [2023-07-10T14:43:50.510Z] /go/src/github.com/openshift-kni/numaresources-operator/test/e2e/serial/tests/configuration.go:629 [2023-07-10T14:43:50.510Z] [2023-07-10T14:43:50.510Z] Begin Captured GinkgoWriter Output >> [2023-07-10T14:43:50.510Z] STEP: set up the test namespace "e2e-test-configuration-6151" 07/10/23 14:38:38.858 [2023-07-10T14:43:50.510Z] STEP: tearing down the test namespace "e2e-test-configuration-6151" 07/10/23 14:43:38.902 [2023-07-10T14:43:50.510Z] STEP: cooldown by verifying NRTs data is settled to the initial state (interval=5s timeout=1m0s) 07/10/23 14:43:44.923 [2023-07-10T14:43:50.510Z] << End Captured GinkgoWriter Output [2023-07-10T14:43:50.510Z] [2023-07-10T14:43:50.510Z] failed to check the NodeGroupConfig status for "/numaresourcesoperator" [2023-07-10T14:43:50.510Z] Unexpected error: [2023-07-10T14:43:50.510Z] <*errors.errorString | 0xc000428ee0>: { [2023-07-10T14:43:50.510Z] s: "timed out waiting for the condition", [2023-07-10T14:43:50.510Z] } [2023-07-10T14:43:50.510Z] timed out waiting for the condition [2023-07-10T14:43:50.510Z] occurred [2023-07-10T14:43:50.510Z] In [It] at: /go/src/github.com/openshift-kni/numaresources-operator/test/e2e/serial/tests/configuration.go:684 [2023-07-10T14:43:50.510Z] ------------------------------
Sample log of the failed step:
[2023-07-10T14:43:39.116Z] I0710 14:43:38.894696 9 configuration.go:644] getting: "/numaresourcesoperator" [2023-07-10T14:43:39.116Z] I0710 14:43:38.901728 9 configuration.go:656] fetched NRO Object "/numaresourcesoperator" [2023-07-10T14:43:39.116Z] I0710 14:43:38.901913 9 configuration.go:678] NRO Object "/numaresourcesoperator" status {"podsFingerprinting":"Enabled","infoRefreshMode":"PeriodicAndEvents","infoRefreshPeriod":"10s"} spec {"podsFingerprinting":"Enabled","infoRefreshMode":"Periodic","infoRefreshPeriod":"10s"} match false
The Status reporting of the operator object should be aligned with the spec settings.
There is a chance that this is caused because of misalignment of the operator build and the tests image, we can know for sure when a new build is published with latest updates on the NRO object. Meanwhile, this bug is opened to track this failure.
Version-Release number of selected component (if applicable):
4.13,4.12
How reproducible:
always
Steps to Reproduce:
1.install NROP 2.run the test https://github.com/openshift-kni/numaresources-operator/blob/main/test/e2e/serial/tests/configuration.go#L629 using latest tests image. 3.
Actual results:
test is failing because of misalignmentbetween Spec and Status of the operaor obbject.
Expected results:
test should pass
Additional info:
- clones
-
-
- Closed
-
- links to