OCPBUGS-35373: [release-4.16] Warn and allow CRD upgrade if validation fails but webhook is specified#781
Conversation
… CRD specifies a conversion strategy (#3209) * warn but allow CRD upgrade when validations fail but new CRD has conversion strategy Signed-off-by: everettraven <everettraven@gmail.com> * unexport validationError Signed-off-by: everettraven <everettraven@gmail.com> * updating warning message to be more descriptive, add warning event on installplan Signed-off-by: everettraven <everettraven@gmail.com> * update warning templ per review comments Signed-off-by: everettraven <everettraven@gmail.com> --------- Signed-off-by: everettraven <everettraven@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: c3e17741c5dde8d67203a9e34bba81c4ad2bddcd
|
/retitle OCPBUGS-35373: [release-4.16] Warn and allow CRD upgrade if validation fails but webhook is specified |
|
@everettraven: This pull request references Jira Issue OCPBUGS-35373, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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. |
|
/jira refresh |
|
@everettraven: This pull request references Jira Issue OCPBUGS-35373, which is invalid:
Comment DetailsIn 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. |
|
/jira refresh |
|
@everettraven: This pull request references Jira Issue OCPBUGS-35373, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn 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. |
|
/label qe-approved |
|
@everettraven: This pull request references Jira Issue OCPBUGS-35373, which is valid. 7 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn 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 |
|
/cherry-pick release-4.15 |
|
@sferich888: once the present PR merges, I will cherry-pick it on top of release-4.15 in a new PR and assign it to you. DetailsIn 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 kubernetes-sigs/prow repository. |
|
/retest |
|
@everettraven: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/label backport-risk-assessed |
|
/lgtm |
|
/label approved |
|
@perdasilva: Can not set label approved: Must be member in one of these teams: [openshift-release-oversight openshift-staff-engineers] DetailsIn 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 kubernetes-sigs/prow repository. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: everettraven, joelanford The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/label cherry-pick-approved |
|
@everettraven: Jira Issue OCPBUGS-35373: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-35373 has been moved to the MODIFIED state. DetailsIn 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. |
|
@sferich888: new pull request created: #789 DetailsIn 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 kubernetes-sigs/prow repository. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build operator-lifecycle-manager-container-v4.16.0-202406180607.p0.g66ef61a.assembly.stream.el9 for distgit operator-lifecycle-manager. |
|
Fix included in accepted release 4.16.0-0.nightly-2024-06-18-130927 |
Cherry pick of b017f92 to 4.16