[release-4.11] WINC-983: [e2e] Ensure required log files are non-empty

[openshift-cherrypick-robot]

This is an automated cherry-pick of #1421

/assign mansikulkarni96

[openshift-ci-robot]

@openshift-cherrypick-robot: An error was encountered cloning bug for cherrypick for bug WINC-983 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message.

request failed. Please analyze the request body for more details. Status code: 400: {"errorMessages":["Number value expected as the Sprint id."],"errors":{}}

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to this:

This is an automated cherry-pick of #1421

/assign mansikulkarni96

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.

[mansikulkarni96]

/lgtm

[mansikulkarni96]

/cherry-pick release-4.10

[openshift-cherrypick-robot]

@mansikulkarni96: once the present PR merges, I will cherry-pick it on top of release-4.10 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.10

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.

[aravindhp]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aravindhp, openshift-cherrypick-robot

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 [aravindhp]

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

[aravindhp]

/cherry-pick release-4.10

@mansikulkarni96 Please cherry pick from master for non bug PRs

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD bc6ce07 and 2 for PR HEAD 0838689 in total

[aravindhp]

/retest-required

azure-e2e-operator is failing because the VM is taking a long time to be configured. This is a flake we have seen in the past on Azure.

platform-none-vsphere-e2e-operator failed with:

INFO[2023-03-07T21:02:19Z] 2023-03-07 21:02:14+00:00 - Creating govc.sh file...
2023-03-07 21:02:14+00:00 - Creating vsphere_context.sh file...
2023-03-07 21:02:14+00:00 - Find virtual machines attached to ci-segment-58 and destroy
govc: POST "/sdk": 503 Service Unavailable 

which looks like a flake.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 9729b36 and 1 for PR HEAD 0838689 in total

[sebsoto]

Cluster install failure
/retest-required

[openshift-ci]

@openshift-cherrypick-robot: all tests passed!

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

@mansikulkarni96: #1463 failed to apply on top of branch "release-4.10":

Applying: Ensure required log files are non-empty
Using index info to reconstruct a base tree...
M	test/e2e/logs_test.go
Falling back to patching base and 3-way merge...
Auto-merging test/e2e/logs_test.go
CONFLICT (content): Merge conflict in test/e2e/logs_test.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 Ensure required log files are non-empty
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.10

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.