Skip to content

Conversation

@sebsoto
Copy link
Contributor

@sebsoto sebsoto commented Sep 30, 2025

Addresses a missing timeout and improves job error output.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 30, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sebsoto

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 30, 2025
@jrvaldes
Copy link
Contributor

/retitle Add timeout to metrics query and cleanup job failure logs in e2e test

@openshift-ci openshift-ci bot changed the title e2e improvements Add timeout to metrics query and cleanup job failure logs in e2e test Sep 30, 2025
@mansikulkarni96
Copy link
Member

changes lgtm, will cherry-pick this and wait for test results.

Copy link
Contributor

@jrvaldes jrvaldes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly LGTM, PTAL at the comments

TLSClientConfig: &tls.Config{InsecureSkipVerify: true},
}
client := &http.Client{Transport: tr}
client := &http.Client{Transport: tr, Timeout: 30 * time.Second}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

30s may be too much for this request, consider 5s

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather wait a bit longer than needed than too little to help flakes.
I know vSphere has historically had a very slow network

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

@sebsoto sebsoto Sep 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as a compromise i'll do 15 seconds 👍

}
req.Header.Set("Authorization", "Bearer "+token)
tr := &http.Transport{
// InsecureSkipVerify is required to avoid errors due to bad certificate
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

consider usign context.WithTimeout to control the timeout per request in ef239e2#diff-41354c8d32cc5449ea0e5de5e5f28928103f9d2642b034f4b6e8474d487d656fL261

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for example:

    ctx, cancel := context.WithTimeout(context.Background(), 5*time.Second)
    defer cancel()

    req, err := http.NewRequestWithContext(ctx, "GET", url, nil)
   

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't know if that really helps here, theres only one request at the moment, and I can't think of a reason of we would need to tweak individual timeouts for different requests in the case we need to add another.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, disregard.

Prevents client.Do from blocking indefinitely.
When a job fails a wall of text is dumped in the test job logs,
including the full job spec as well as all events associated with it.
This hasn't proven to be useful for debugging, and makes the errors
harder to read.

All of this information can be found elsewhere in the artifact
directory.
@jrvaldes
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 30, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD db80e2a and 2 for PR HEAD 92ec5dc in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD e729729 and 1 for PR HEAD 92ec5dc in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6b6ff1b and 0 for PR HEAD 92ec5dc in total

@openshift-ci-robot
Copy link

/hold

Revision 92ec5dc was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 1, 2025
@jrvaldes
Copy link
Contributor

jrvaldes commented Oct 1, 2025

/test gcp-e2e-operator

@jrvaldes
Copy link
Contributor

jrvaldes commented Oct 1, 2025

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 1, 2025
@jrvaldes
Copy link
Contributor

jrvaldes commented Oct 1, 2025

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6b6ff1b and 2 for PR HEAD 92ec5dc in total

@mansikulkarni96
Copy link
Member

/override ci/prow/nutanix-e2e-operator

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 1, 2025

@mansikulkarni96: Overrode contexts on behalf of mansikulkarni96: ci/prow/nutanix-e2e-operator

In response to this:

/override ci/prow/nutanix-e2e-operator

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
Copy link
Contributor

openshift-ci bot commented Oct 1, 2025

@sebsoto: 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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit e32582b into openshift:master Oct 1, 2025
18 checks passed
@mansikulkarni96
Copy link
Member

/cherry-pick release-4.20

@openshift-cherrypick-robot

@mansikulkarni96: new pull request created: #3389

In response to this:

/cherry-pick release-4.20

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.

@mansikulkarni96
Copy link
Member

/cherry-pick release-4.19 release-4.18 release-4.17

@openshift-cherrypick-robot

@mansikulkarni96: new pull request created: #3390

In response to this:

/cherry-pick release-4.19 release-4.18 release-4.17

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.

@mansikulkarni96
Copy link
Member

/cherry-pick release-4.18
/cherry-pick release-4.17

@openshift-cherrypick-robot

@mansikulkarni96: #3378 failed to apply on top of branch "release-4.17":

Applying: Add timeout to metrics query
Applying: Cleanup job failure logs
Using index info to reconstruct a base tree...
M	test/e2e/network_test.go
Falling back to patching base and 3-way merge...
Auto-merging test/e2e/network_test.go
CONFLICT (content): Merge conflict in test/e2e/network_test.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0002 Cleanup job failure logs

In response to this:

/cherry-pick release-4.18
/cherry-pick release-4.17

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants