test/e2e/upgrade: Do not force updates

[wking]

We've been forcing since 429521d (#22645). Back then we were maybe not signing CI releases then? We're currently trusting (and hopefully signing) CI releases with a CI key, and signing nightlies with the beta 2 or release keys. Blocking nightly -> CI updates would be good, and we don't need to run those jobs. CI -> nightly updates would be allowed if we landed something like openshift/cluster-update-keys#16, but we can also get by without any update jobs connecting CI and nightly trust.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: wking
To complete the pull request process, please assign bparees after the PR has been reviewed.
You can assign the PR to them by writing /assign @bparees in a comment when ready.

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

Details

Needs approval from an approver in each of these files:

• test/OWNERS

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

[openshift-ci]

@wking: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws-serial	011a695	link	/test e2e-aws-serial
ci/prow/e2e-aws-fips	011a695	link	/test e2e-aws-fips
ci/prow/e2e-aws-csi	011a695	link	/test e2e-aws-csi
ci/prow/e2e-metal-ipi-ovn-ipv6	011a695	link	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-gcp	011a695	link	/test e2e-gcp
ci/prow/e2e-gcp-upgrade	011a695	link	/test e2e-gcp-upgrade
ci/prow/e2e-gcp-csi	011a695	link	/test e2e-gcp-csi
ci/prow/e2e-gcp-disruptive	011a695	link	/test e2e-gcp-disruptive
ci/prow/e2e-aws-disruptive	011a695	link	/test e2e-aws-disruptive
ci/prow/e2e-agnostic-cmd	011a695	link	/test e2e-agnostic-cmd
ci/prow/e2e-aws-jenkins	011a695	link	/test e2e-aws-jenkins

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.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.