Skip to content

Conversation

@barbacbd
Copy link
Contributor

** Remove the validation when the endpoint field is filled out in install-config. The feature has been tested and the feature gate should no longer be required.

** Remove the test for the featuregate.

** Remove the validation when the `endpoint` field is filled out in install-config.
The feature has been tested and the feature gate should no longer be required.

** Remove the test for the featuregate.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 20, 2025
@openshift-ci-robot
Copy link
Contributor

@barbacbd: This pull request explicitly references no jira issue.

In response to this:

** Remove the validation when the endpoint field is filled out in install-config. The feature has been tested and the feature gate should no longer be required.

** Remove the test for the featuregate.

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

/hold

@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 Nov 20, 2025
@patrickdillon
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 20, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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 Nov 20, 2025
@patrickdillon
Copy link
Contributor

/hold cancel
/verified by e2e-gcp-ovn

@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 Nov 20, 2025
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 20, 2025
@openshift-ci-robot
Copy link
Contributor

@patrickdillon: This PR has been marked as verified by e2e-gcp-ovn.

In response to this:

/hold cancel
/verified by e2e-gcp-ovn

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

/retest-required

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 8bb5744 and 2 for PR HEAD f256cf8 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD d0a5714 and 1 for PR HEAD f256cf8 in total

@patrickdillon
Copy link
Contributor

/skip

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0e43b96 and 0 for PR HEAD f256cf8 in total

@barbacbd
Copy link
Contributor Author

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2025

@barbacbd: The following tests 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/okd-scos-e2e-vsphere-ovn f256cf8 link false /test okd-scos-e2e-vsphere-ovn
ci/prow/e2e-gcp-ovn-byo-vpc f256cf8 link false /test e2e-gcp-ovn-byo-vpc
ci/prow/e2e-gcp-custom-dns f256cf8 link false /test e2e-gcp-custom-dns
ci/prow/e2e-gcp-secureboot f256cf8 link false /test e2e-gcp-secureboot

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.

@patrickdillon
Copy link
Contributor

/override ci/prow/e2e-aws-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2025

@patrickdillon: Overrode contexts on behalf of patrickdillon: ci/prow/e2e-aws-ovn

In response to this:

/override ci/prow/e2e-aws-ovn

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

/override ci/prow/e2e-aws-ovn ci/prow/e2e-aws-ovn-edge-zones-manifest-validation

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 22, 2025

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

  • ci/prow/e2e-aws-ovn-edge-zones-manifest-validation

Only the following failed contexts/checkruns were expected:

  • ci/prow/artifacts-images
  • ci/prow/e2e-aws-ovn
  • ci/prow/e2e-gcp-custom-dns
  • ci/prow/e2e-gcp-custom-endpoints
  • ci/prow/e2e-gcp-default-config
  • ci/prow/e2e-gcp-ovn
  • ci/prow/e2e-gcp-ovn-byo-vpc
  • ci/prow/e2e-gcp-ovn-xpn
  • ci/prow/e2e-gcp-secureboot
  • ci/prow/e2e-gcp-xpn-dedicated-dns-project
  • ci/prow/gcp-private
  • ci/prow/gofmt
  • ci/prow/golint
  • ci/prow/govet
  • ci/prow/images
  • ci/prow/okd-scos-e2e-vsphere-ovn
  • ci/prow/okd-scos-images
  • ci/prow/shellcheck
  • ci/prow/unit
  • ci/prow/verify-codegen
  • ci/prow/verify-deps
  • ci/prow/verify-vendor
  • ci/prow/yaml-lint
  • pull-ci-openshift-installer-fcos-gofmt
  • pull-ci-openshift-installer-fcos-golint
  • pull-ci-openshift-installer-fcos-govet
  • pull-ci-openshift-installer-fcos-images
  • pull-ci-openshift-installer-fcos-unit
  • pull-ci-openshift-installer-fcos-verify-codegen
  • pull-ci-openshift-installer-fcos-verify-vendor
  • pull-ci-openshift-installer-main-artifacts-images
  • pull-ci-openshift-installer-main-e2e-aws-ovn
  • pull-ci-openshift-installer-main-e2e-gcp-custom-dns
  • pull-ci-openshift-installer-main-e2e-gcp-custom-endpoints
  • pull-ci-openshift-installer-main-e2e-gcp-default-config
  • pull-ci-openshift-installer-main-e2e-gcp-ovn
  • pull-ci-openshift-installer-main-e2e-gcp-ovn-byo-vpc
  • pull-ci-openshift-installer-main-e2e-gcp-ovn-xpn
  • pull-ci-openshift-installer-main-e2e-gcp-secureboot
  • pull-ci-openshift-installer-main-e2e-gcp-xpn-dedicated-dns-project
  • pull-ci-openshift-installer-main-gcp-private
  • pull-ci-openshift-installer-main-okd-scos-e2e-vsphere-ovn
  • pull-ci-openshift-installer-main-okd-scos-images
  • pull-ci-openshift-installer-main-shellcheck
  • pull-ci-openshift-installer-main-verify-deps
  • pull-ci-openshift-installer-main-yaml-lint
  • tide

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

In response to this:

/override ci/prow/e2e-aws-ovn ci/prow/e2e-aws-ovn-edge-zones-manifest-validation

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

/override ci/prow/e2e-aws-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 22, 2025

@patrickdillon: Overrode contexts on behalf of patrickdillon: ci/prow/e2e-aws-ovn

In response to this:

/override ci/prow/e2e-aws-ovn

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 openshift-merge-bot bot merged commit 5060ac9 into openshift:main Nov 22, 2025
24 checks passed
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants