Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1992242

Summary: [sig-node] Managed cluster should report ready nodes the entire duration of the test run [Late] [Skipped:Disconnected] [Suite:openshift/conformance/parallel]
Product: OpenShift Container Platform Reporter: Gabe Montero <gmontero>
Component: NodeAssignee: Harshal Patil <harpatil>
Node sub component: Kubelet QA Contact: Sunil Choudhary <schoudha>
Status: CLOSED DUPLICATE Docs Contact:
Severity: unspecified    
Priority: unspecified CC: aos-bugs, sippy
Version: 4.9   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
[sig-node] Managed cluster should report ready nodes the entire duration of the test run [Late] [Skipped:Disconnected] [Suite:openshift/conformance/parallel]
Last Closed: 2021-08-20 02:23:53 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 Gabe Montero 2021-08-10 19:48:29 UTC
test:
[sig-node] Managed cluster should report ready nodes the entire duration of the test run [Late] [Skipped:Disconnected] [Suite:openshift/conformance/parallel] 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-node%5C%5D+Managed+cluster+should+report+ready+nodes+the+entire+duration+of+the+test+run+%5C%5BLate%5C%5D+%5C%5BSkipped%3ADisconnected%5C%5D+%5C%5BSuite%3Aopenshift%2Fconformance%2Fparallel%5C%5D


Apologies on the sub component.  Total guess on my part.

See https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/26384/pull-ci-openshift-origin-master-e2e-aws-single-node/1425131401899937792

Log snippet:

fail [github.com/openshift/origin/test/extended/machines/cluster.go:98]: Unexpected error:
    <errors.aggregate | len:1, cap:1>: [
        {
            s: "promQL query returned unexpected results:\n(min_over_time((max by (node) (kube_node_status_condition{condition=\"Ready\",status=\"true\"} offset 1m) and (((max by (node) (kube_node_status_condition offset 1m))) and (0*max by (node) (kube_node_status_condition offset 7m)) and (0*max by (node) (kube_node_status_condition))))[40m24s:1s])) < 1\n[\n  {\n    \"metric\": {\n      \"node\": \"ip-10-0-183-76.ec2.internal\"\n    },\n    \"value\": [\n      1628617927.427,\n      \"0\"\n    ]\n  }\n]",
        },
    ]
    promQL query returned unexpected results:
    (min_over_time((max by (node) (kube_node_status_condition{condition="Ready",status="true"} offset 1m) and (((max by (node) (kube_node_status_condition offset 1m))) and (0*max by (node) (kube_node_status_condition offset 7m)) and (0*max by (node) (kube_node_status_condition))))[40m24s:1s])) < 1
    [
      {
        "metric": {
          "node": "ip-10-0-183-76.ec2.internal"
        },
        "value": [
          1628617927.427,
          "0"
        ]
      }
    ]
occurred

Comment 1 Francesco Romani 2021-08-11 09:43:17 UTC
this doesn't seem related to the topology manager at all - and the topology manager tests don't run in the parallel suite anyway.

Comment 2 Gabe Montero 2021-08-11 12:35:55 UTC
(In reply to Francesco Romani from comment #1)
> this doesn't seem related to the topology manager at all - and the topology
> manager tests don't run in the parallel suite anyway.

figured I guessed at the wrong sub component :-/

thanks for correcting Francesco

Comment 3 Harshal Patil 2021-08-20 02:23:53 UTC

*** This bug has been marked as a duplicate of bug 1995609 ***