Revert "OCPBUGS-32108: stop loading legacy schemes on global scheme "

[dgoodwin]

Reverts #1775

This will not be merged, we're trying to find a PR that fixed something which is still happening in 4.16. This PR is in the list of 4 when the problem dissappeared in 4.17.

[openshift-ci-robot]

@dgoodwin: This pull request references Jira Issue OCPBUGS-32108, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Reverts #1775

This will not be merged, we're trying to find a PR that fixed something which is still happening in 4.16. This PR is in the list of 4 when the problem dissappeared in 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 openshift-eng/jira-lifecycle-plugin repository.

[dgoodwin]

/payload-job periodic-ci-openshift-release-master-ci-4.17-e2e-gcp-ovn
/payload-job periodic-ci-openshift-release-master-ci-4.17-e2e-gcp-ovn
/payload-job periodic-ci-openshift-release-master-ci-4.17-e2e-gcp-ovn

/hold

[openshift-ci]

@dgoodwin: trigger 3 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.17-e2e-gcp-ovn
• periodic-ci-openshift-release-master-ci-4.17-e2e-gcp-ovn
• periodic-ci-openshift-release-master-ci-4.17-e2e-gcp-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8d29bcf0-3250-11ef-984e-78501d802096-0

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dgoodwin
Once this PR has been reviewed and has the lgtm label, please assign ardaguclu for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[rphillips]

Maybe try this once more... Looks like a CI issue.

/payload-job periodic-ci-openshift-release-master-ci-4.17-e2e-gcp-ovn
/payload-job periodic-ci-openshift-release-master-ci-4.17-e2e-gcp-ovn
/payload-job periodic-ci-openshift-release-master-ci-4.17-e2e-gcp-ovn

[openshift-ci]

@rphillips: trigger 3 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.17-e2e-gcp-ovn
• periodic-ci-openshift-release-master-ci-4.17-e2e-gcp-ovn
• periodic-ci-openshift-release-master-ci-4.17-e2e-gcp-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/19f8aa20-3264-11ef-9ac3-35a367096689-0

[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