OCPBUGS-31868: Add debug logging for SLB monitortest cleanup

[dgoodwin]

This test is failing periodically in some cases and we can't see when
the problem is occurring to correlate with logs or intervals because the
framework doesn't log much of anything.

[openshift-ci-robot]

@dgoodwin: This pull request references Jira Issue OCPBUGS-31868, which is invalid:

• expected the bug to target the "4.16.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:

This test is failing periodically in some cases and we can't see when
the problem is occurring to correlate with logs or intervals because the
framework doesn't log much of anything.

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dgoodwin]

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

[neisw]

/lgtm

[DennisPeriquet]

/jira refresh

[openshift-ci-robot]

@DennisPeriquet: This pull request references Jira Issue OCPBUGS-31868, 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.16.0) matches configured target version for branch (4.16.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

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]

/retest-required

Remaining retests: 0 against base HEAD ef0a1a0 and 2 for PR HEAD 79ea7f5 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a42236a and 1 for PR HEAD 79ea7f5 in total

[dgoodwin]

/override ci/prow/e2e-metal-ipi-ovn-ipv6

[openshift-ci]

@dgoodwin: Overrode contexts on behalf of dgoodwin: ci/prow/e2e-metal-ipi-ovn-ipv6

In response to this:

/override ci/prow/e2e-metal-ipi-ovn-ipv6

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/test-infra repository.

[openshift-ci]

@dgoodwin: 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-single-node-upgrade	79ea7f5	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-openstack-ovn	79ea7f5	link	false	/test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-single-node	79ea7f5	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-single-node-serial	79ea7f5	link	false	/test e2e-aws-ovn-single-node-serial

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/test-infra repository. I understand the commands that are listed here.

[openshift-trt-bot]

Job Failure Risk Analysis for sha: 79ea7f5

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6	IncompleteTests Tests for this run (98) are below the historical average (935): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

[openshift-ci-robot]

@dgoodwin: Jira Issue OCPBUGS-31868: All pull requests linked via external trackers have merged:

• openshift/origin#28697

Jira Issue OCPBUGS-31868 has been moved to the MODIFIED state.

In response to this:

This test is failing periodically in some cases and we can't see when
the problem is occurring to correlate with logs or intervals because the
framework doesn't log much of anything.

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-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-tests-container-v4.16.0-202404101645.p0.g3d444ed.assembly.stream.el8 for distgit openshift-enterprise-tests.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.16.0-0.nightly-2024-04-13-070448

[openshift-merge-robot]

Fix included in accepted release 4.16.0-0.nightly-2024-05-04-214435

[prb112]

/cherry-pick release-4.14

[prb112]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@prb112: #28697 failed to apply on top of branch "release-4.14":

Applying: Add debug logging for SLB monitortest cleanup
Using index info to reconstruct a base tree...
M	pkg/monitortestframework/impl.go
M	pkg/monitortestframework/panic.go
M	pkg/monitortests/network/disruptionserviceloadbalancer/monitortest.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/monitortests/network/disruptionserviceloadbalancer/monitortest.go
CONFLICT (content): Merge conflict in pkg/monitortests/network/disruptionserviceloadbalancer/monitortest.go
Auto-merging pkg/monitortestframework/panic.go
CONFLICT (content): Merge conflict in pkg/monitortestframework/panic.go
Auto-merging pkg/monitortestframework/impl.go
CONFLICT (content): Merge conflict in pkg/monitortestframework/impl.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add debug logging for SLB monitortest cleanup
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.14

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-cherrypick-robot]

@prb112: #28697 failed to apply on top of branch "release-4.15":

Applying: Add debug logging for SLB monitortest cleanup
Using index info to reconstruct a base tree...
M	pkg/monitortestframework/impl.go
M	pkg/monitortests/network/disruptionserviceloadbalancer/monitortest.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/monitortests/network/disruptionserviceloadbalancer/monitortest.go
CONFLICT (content): Merge conflict in pkg/monitortests/network/disruptionserviceloadbalancer/monitortest.go
Auto-merging pkg/monitortestframework/impl.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add debug logging for SLB monitortest cleanup
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.15

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.