TRT-2516: Revert #594 "OCPBUGS-65634: add service account to curl job"

[sosiouxme]

Reverts #594 ; tracked by TRT-2516

Per OpenShift policy, we are (possibly!) reverting this (possibly!) breaking change to get CI and/or nightly payloads flowing again.

It might be related to payload failures; ref. https://redhat-internal.slack.com/archives/C01CQA76KMX/p1768943539791609

To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of these jobs to confirm the fix has corrected the problem:

run payload job with /payload-aggregate periodic-ci-openshift-release-master-nightly-4.22-e2e-aws-ovn-upgrade-fips 10

(It does not fail every time, but 3 or 4 out of 10)

CC: @ehearne-redhat

PR created by Revertomatic^™️

[openshift-ci-robot]

@sosiouxme: This pull request references TRT-2516 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Reverts #594 ; tracked by TRT-2516

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

might be related to payload failures; ref. https://redhat-internal.slack.com/archives/C01CQA76KMX/p1768943539791609

To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of these jobs to confirm the fix has corrected the problem:

run payload job with /payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial 10

CC: @ehearne-redhat

PR created by Revertomatic^™️

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]

@sosiouxme: This pull request references TRT-2516 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Reverts #594 ; tracked by TRT-2516

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

might be related to payload failures; ref. https://redhat-internal.slack.com/archives/C01CQA76KMX/p1768943539791609

To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of these jobs to confirm the fix has corrected the problem:

run payload job with /payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial 10

CC: @ehearne-redhat

PR created by Revertomatic^™️

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]

@sosiouxme: This pull request references TRT-2516 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Reverts #594 ; tracked by TRT-2516

Per OpenShift policy, we are (possibly!) reverting this (possibly!) breaking change to get CI and/or nightly payloads flowing again.

It might be related to payload failures; ref. https://redhat-internal.slack.com/archives/C01CQA76KMX/p1768943539791609

To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of these jobs to confirm the fix has corrected the problem:

run payload job with /payload-aggregate periodic-ci-openshift-release-master-nightly-4.22-e2e-aws-ovn-upgrade-fips 10

(It does not fail every time, but 3 or 4 out of 10)

CC: @ehearne-redhat

PR created by Revertomatic^™️

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]

@sosiouxme: The following test 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/verify-commits	fca635b	link	true	/test verify-commits

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

[sosiouxme]

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.22-e2e-aws-ovn-upgrade-fips 10

[openshift-ci]

@sosiouxme: 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.22-e2e-aws-ovn-upgrade-fips

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/feb21870-f64b-11f0-9307-19dc73c6a32f-0

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grokspawn, sosiouxme

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:

• DOWNSTREAM_OWNERS [grokspawn]

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

[kuiwang02]

/verified by @kuiwang02

[openshift-ci-robot]

@kuiwang02: This PR has been marked as verified by @kuiwang02.

Details

In response to this:

/verified by @kuiwang02

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.