-
Notifications
You must be signed in to change notification settings - Fork 24
no-jira: Machine Api Operator GCP must search for the GCP Custom Endpoints Installer feature gate #128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no-jira: Machine Api Operator GCP must search for the GCP Custom Endpoints Installer feature gate #128
Conversation
** go.mod and go.sum updates. ** Vendor Updates.
@barbacbd: This pull request explicitly references no jira issue. In response to this:
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. |
/retest-required |
1 similar comment
/retest-required |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
Happy to approve this
@barbacbd anyone from your team that has context on this and can drop an LGTM, ty
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: damdo 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 |
/retest |
2 similar comments
/retest |
/retest |
/lgtm |
/assign @sunzhaohua2 @huali9 @miyadav Are we happy with the regressions and to put the verified label? |
All gcp cluster installations failed, some operators degrade. machine-controller show panic |
/lgtm cancel |
You probably need to change this:
and any other potential occurrences too |
** Update the references from FeatureGateGCPCustomAPIEndpoints to FeatureGateGCPCustomAPIEndpointsInstall due to new procedures. This inidcates that the feature gate originates as an openshift installer feature gate. cloud/gcp/actuators/machineset: ** Update the references from FeatureGateGCPCustomAPIEndpoints to FeatureGateGCPCustomAPIEndpointsInstall due to new procedures. This inidcates that the feature gate originates as an openshift installer feature gate.
7357af1
to
f4bf1e2
Compare
@barbacbd: The following test failed, say
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. |
/verified by @sunzhaohua2 Tried day2 enable featuregate GCPCustomAPIEndpointsInstall, cluster looks good.
Fix the regression run failed cases in pr https://github.com/openshift/openshift-tests-private/pull/27161 |
@sunzhaohua2: This PR has been marked as verified by In response to this:
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. |
/lgtm |
55e308a
into
openshift:main
Update the reference from FeatureGateGCPCustomAPIEndpoints to FeatureGateGCPCustomAPIEndpointsInstall due to new procedures. This indicates that the feature gate originates as an OpenShift installer feature gate.