[release-5.0] OCPBUGS-114620: Promote GCD to Default

[openshift-cherrypick-robot]

This is an automated cherry-pick of #2991

/assign barbacbd

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: CORS-4550

Details

In response to this:

This is an automated cherry-pick of #2991

/assign barbacbd

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.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: d9d8e1fb-792f-45ac-8151-dc7fcdcdb21b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

Hello @openshift-cherrypick-robot! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[barbacbd]

/retitle [release-5.0] OCPBUGS-114620: Promote GCD to Default

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-114620, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-114668 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-114668 targets the "5.1.0" version, which is one of the valid target versions: 5.1.0
• bug has dependents

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

Details

In response to this:

This is an automated cherry-pick of #2991

/assign barbacbd

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.

[barbacbd]

Move GCD to default featureset. Promoted via SBAR.

[barbacbd]

Installer PR for 5.0 found here: openshift/installer#10825

[everettraven]

/lgtm
/approve

/label backport-risk-assessed

SBAR approved for this feature backport, including with limited testing runs.
/override verify-feature-promotion

[openshift-ci]

@everettraven: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

• verify-feature-promotion

Only the following failed contexts/checkruns were expected:

• CodeRabbit
• ci/prow/build
• ci/prow/e2e-aws-ovn
• ci/prow/e2e-aws-ovn-hypershift
• ci/prow/e2e-aws-ovn-hypershift-conformance
• ci/prow/e2e-aws-ovn-techpreview
• ci/prow/e2e-aws-serial-1of2
• ci/prow/e2e-aws-serial-2of2
• ci/prow/e2e-aws-serial-techpreview-1of2
• ci/prow/e2e-aws-serial-techpreview-2of2
• ci/prow/e2e-azure
• ci/prow/e2e-gcp
• ci/prow/e2e-upgrade
• ci/prow/e2e-upgrade-out-of-change
• ci/prow/e2e-vsphere-ovn
• ci/prow/images
• ci/prow/integration
• ci/prow/lint
• ci/prow/unit
• ci/prow/verify
• ci/prow/verify-client-go
• ci/prow/verify-crd-schema
• ci/prow/verify-crdify
• ci/prow/verify-deps
• ci/prow/verify-feature-promotion
• ci/prow/verify-hypershift-integration
• pull-ci-openshift-api-master-build
• pull-ci-openshift-api-master-e2e-aws-ovn
• pull-ci-openshift-api-master-e2e-aws-ovn-hypershift
• pull-ci-openshift-api-master-e2e-aws-ovn-hypershift-conformance
• pull-ci-openshift-api-master-e2e-aws-ovn-techpreview
• pull-ci-openshift-api-master-e2e-aws-serial-1of2
• pull-ci-openshift-api-master-e2e-aws-serial-2of2
• pull-ci-openshift-api-master-e2e-aws-serial-techpreview-1of2
• pull-ci-openshift-api-master-e2e-aws-serial-techpreview-2of2
• pull-ci-openshift-api-master-e2e-azure
• pull-ci-openshift-api-master-e2e-gcp
• pull-ci-openshift-api-master-e2e-upgrade
• pull-ci-openshift-api-master-e2e-upgrade-out-of-change
• pull-ci-openshift-api-master-e2e-vsphere-ovn
• pull-ci-openshift-api-master-images
• pull-ci-openshift-api-master-integration
• pull-ci-openshift-api-master-lint
• pull-ci-openshift-api-master-unit
• pull-ci-openshift-api-master-verify
• pull-ci-openshift-api-master-verify-client-go
• pull-ci-openshift-api-master-verify-crd-schema
• pull-ci-openshift-api-master-verify-crdify
• pull-ci-openshift-api-master-verify-deps
• pull-ci-openshift-api-master-verify-feature-promotion
• tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/lgtm
/approve

/label backport-risk-assessed

SBAR approved for this feature backport, including with limited testing runs.
/override verify-feature-promotion

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-merge-bot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial-1of2
/test e2e-aws-serial-2of2
/test e2e-aws-serial-techpreview-1of2
/test e2e-aws-serial-techpreview-2of2
/test e2e-azure
/test e2e-gcp
/test e2e-upgrade
/test e2e-upgrade-out-of-change
/test e2e-vsphere-ovn

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven

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 [everettraven]

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

[everettraven]

/override ci/prow/verify-feature-promotion

[openshift-ci]

@everettraven: Overrode contexts on behalf of everettraven: ci/prow/verify-feature-promotion

Details

In response to this:

/override ci/prow/verify-feature-promotion

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.

[patrickdillon]

/verified by e2e & unit

[openshift-ci-robot]

@patrickdillon: This PR has been marked as verified by e2e & unit.

Details

In response to this:

/verified by e2e & unit

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.

[tthvo]

/test e2e-azure e2e-gcp
/tide refresh

[openshift-ci]

@openshift-cherrypick-robot: 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-feature-promotion	2b261ed	link	true	/test verify-feature-promotion

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.

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-114620: Some pull requests linked via external trackers have merged:

• openshift/api#3017

The following pull request, linked via external tracker, has not merged:

• openshift/installer#10825 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-114620 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Details

In response to this:

This is an automated cherry-pick of #2991

/assign barbacbd

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.