[release-4.10] Make log test more resilient

[openshift-cherrypick-robot]

This is an automated cherry-pick of #1214

/assign mansikulkarni96

[mansikulkarni96]

/lgtm

[sebsoto]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [sebsoto]

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD fade8d8 and 2 for PR HEAD 3b23824 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 76d1e79 and 1 for PR HEAD 3b23824 in total

[aravindhp]

/retest-required

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

 Error: error powering on virtual machine: powerOn task for vm "/SDDC-Datacenter/vm/ci-op-xzfscnmv-a0553/lb-0" failed: Insufficient resources to satisfy configured failover level for vSphere HA.
  on vm/main.tf line 1, in resource "vsphere_virtual_machine" "vm":
   1: resource "vsphere_virtual_machine" "vm" { 

Looks like a resource issue. Needs to be reported if this happens again.

[aravindhp]

/retest-required

platform-none-vsphere-e2e-operator failing because DNS record already exists. This is odd given that cluster names are unique:

 Error: [ERR]: Error building changeset: InvalidChangeBatch: [Tried to create resource record set [name='ci-op-xzfscnmv-a0553.vmc-ci.devcluster.openshift.com.', type='NS'] but it already exists]
	status code: 400, request id: 503e4adb-4aa8-4a66-a478-3026ad54fc49
  on cluster_domain/main.tf line 15, in resource "aws_route53_record" "name_server":
  15: resource "aws_route53_record" "name_server" { 

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 428c6a6 and 0 for PR HEAD 3b23824 in total

[openshift-ci-robot]

/hold

Revision 3b23824 was retested 3 times: holding

[mansikulkarni96]

/retest-required
vsphere cluster issues resolved.

[sebsoto]

/retest-required

[sebsoto]

/retest-required

[mtnbikenc]

/hold cancel
Dropping automated robot hold.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 428c6a6 and 2 for PR HEAD 3b23824 in total

[sebsoto]

/test vsphere-e2e-operator

[sebsoto]

/retest-required

[aravindhp]

/retest-required

vsphere-e2e-operator is failing in pre-install phase

 govc: Post "https://ibmvcenter.vmc-ci.devcluster.openshift.com/sdk": EOF
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"k8s.io/test-infra/prow/entrypoint/run.go:79","func":"k8s.io/test-infra/prow/entrypoint.Options.Run","level":"error","msg":"Error executing test process","severity":"error","time":"2023-03-22T21:20:44Z"}
error: failed to execute wrapped command: exit status 1 
INFO[2023-03-22T21:20:44Z] Step vsphere-e2e-operator-ipi-conf-vsphere-check failed after 8s. 
INFO[2023-03-22T21:20:44Z] Step phase pre failed after 8s.    

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD b3d56b3 and 1 for PR HEAD 3b23824 in total

[aravindhp]

/retest-required

Early install failure:

INFO[2023-03-28T20:58:12Z] Running step aws-e2e-operator-ipi-conf.      
INFO[2023-03-28T20:58:12Z] Step aws-e2e-operator-ipi-conf failed after 0s. 
INFO[2023-03-28T20:58:12Z] Step phase pre failed after 0s.   

[openshift-ci]

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.