OCPBUGS-60610: UPSTREAM: <carry>: Dump flow rules for debugging invalid conntrack state test

[arkadeepsen]

Enhance invalid conntrack state test by capturing ovs flow rules for debugging from the ovnk pods. This test has been sporadically failing and multiple tries of reproducing the issue has failed. This change improves logging and troubleshooting capabilities in the conntrack test.

[openshift-ci-robot]

@arkadeepsen: This pull request references Jira Issue OCPBUGS-60610, which is invalid:

• expected the bug to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Enhance invalid conntrack state test by capturing ovs flow rules for debugging from the ovnk pods. This test has been sporadically failing and multiple tries of reproducing the issue has failed. This change improves logging and troubleshooting capabilities in the conntrack test.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@arkadeepsen: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• a05ca4e|UPSTREAM: : Dump flow rules for debugging invalid conntrack state test: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: arkadeepsen
Once this PR has been reviewed and has the lgtm label, please assign bertinatto for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[arkadeepsen]

/jira refresh

[openshift-ci-robot]

@arkadeepsen: This pull request references Jira Issue OCPBUGS-60610, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.21.0) matches configured target version for branch (4.21.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@arkadeepsen: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 64fe573|UPSTREAM: : Dump flow rules for debugging invalid conntrack state test: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@arkadeepsen: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 7a0b5d5|UPSTREAM: : Dump flow rules for debugging invalid conntrack state test: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@arkadeepsen: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 73c60d1|UPSTREAM: : Dump flow rules for debugging invalid conntrack state test: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[arkadeepsen]

/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-runc

[openshift-ci]

@arkadeepsen: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-runc

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6114d6e0-8975-11f0-9140-cda4980a5203-0

[arkadeepsen]

/retest-required

[openshift-ci-robot]

@arkadeepsen: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 73c60d1|UPSTREAM: : Dump flow rules for debugging invalid conntrack state test: does not specify an upstream backport in the commit message
• fc112df|Test commit to check correctness of dumpFlowRules function: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@arkadeepsen: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 73c60d1|UPSTREAM: : Dump flow rules for debugging invalid conntrack state test: does not specify an upstream backport in the commit message
• aa4f45c|Test commit to check correctness of dumpFlowRules function: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@arkadeepsen: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 73c60d1|UPSTREAM: : Dump flow rules for debugging invalid conntrack state test: does not specify an upstream backport in the commit message
• e672221|Test commit to check correctness of dumpFlowRules function: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@arkadeepsen: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 73c60d1|UPSTREAM: : Dump flow rules for debugging invalid conntrack state test: does not specify an upstream backport in the commit message
• aad76cd|Test commit to check correctness of dumpFlowRules function: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@arkadeepsen: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 60a6cf2|Test commit to check correctness of dumpFlowRules function: does not specify an upstream backport in the commit message
• 73c60d1|UPSTREAM: : Dump flow rules for debugging invalid conntrack state test: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[arkadeepsen]

Using the test commit 60a6cf2, was able to print the the output for ovs-dpctl dump-flows for the nodes where the server and client pods are running.

Some examples:

• k8s-e2e-gcp-ovn: output
• e2e-aws-ovn-cgroupsv2: output
• e2e-aws-ovn-runc: output

[openshift-ci-robot]

@arkadeepsen: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 1fab4d3|UPSTREAM: : Dump flow rules for debugging invalid conntrack state test: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[arkadeepsen]

/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-proxy
/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-runc

[openshift-ci]

@arkadeepsen: trigger 2 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-proxy
• periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-runc

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/51e4bb10-8cb1-11f0-9c32-1d842dc5bd75-0

[openshift-ci]

@arkadeepsen: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-techpreview-serial	1fab4d3	link	false	/test e2e-aws-ovn-techpreview-serial
ci/prow/okd-scos-e2e-aws-ovn	1fab4d3	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-hypershift	1fab4d3	link	true	/test e2e-aws-ovn-hypershift
ci/prow/e2e-aws-ovn-techpreview	1fab4d3	link	false	/test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-ovn-serial	1fab4d3	link	true	/test e2e-aws-ovn-serial
ci/prow/e2e-metal-ipi-ovn-ipv6	1fab4d3	link	true	/test e2e-metal-ipi-ovn-ipv6

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[arkadeepsen]

/close

The issue has been identified as an upstream bug and is being tracked here: kubernetes#134116

[openshift-ci]

@arkadeepsen: Closed this PR.

In response to this:

/close

The issue has been identified as an upstream bug and is being tracked here: kubernetes#134116

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci-robot]

@arkadeepsen: This pull request references Jira Issue OCPBUGS-60610. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

In response to this:

Enhance invalid conntrack state test by capturing ovs flow rules for debugging from the ovnk pods. This test has been sporadically failing and multiple tries of reproducing the issue has failed. This change improves logging and troubleshooting capabilities in the conntrack test.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.