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
[release-4.14] OCPBUGS-30015: fix: convert continue
field between v1beta1 and v1alpha1
#279
[release-4.14] OCPBUGS-30015: fix: convert continue
field between v1beta1 and v1alpha1
#279
Conversation
This change converts the `continue` field between v1alpha1 and v1beta1 AlertmanagerConfig versions. When a v1beta1 AlertmanagerConfig object was created with `continue: true`, the `continue` field was always converted to `false` when stored as v1alpha1. Signed-off-by: Simon Pasquier <spasquie@redhat.com>
Signed-off-by: Simon Pasquier <spasquie@redhat.com>
@openshift-cherrypick-robot: Jira Issue OCPBUGS-29180 has been cloned as Jira Issue OCPBUGS-30015. Will retitle bug to link to clone. 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. |
continue
field between v1beta1 and v1alpha1continue
field between v1beta1 and v1alpha1
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-30015, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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. |
/label cherry-pick-approved |
@openshift-cherrypick-robot: all tests passed! 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/test-infra repository. I understand the commands that are listed here. |
/label backport-risk-assessed |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: openshift-cherrypick-robot, simonpasquier 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 |
/jira refresh |
@juzhao: This pull request references Jira Issue OCPBUGS-30015, which is valid. 6 validation(s) were run on this bug
Requesting review from QA contact: 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. |
a4b845a
into
openshift:release-4.14
@openshift-cherrypick-robot: Jira Issue OCPBUGS-30015: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-30015 has been moved to the MODIFIED state. 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. |
[ART PR BUILD NOTIFIER] This PR has been included in build prometheus-config-reloader-container-v4.14.0-202403010039.p0.ga4b845a.assembly.stream.el8 for distgit prometheus-config-reloader. |
Fix included in accepted release 4.14.0-0.nightly-2024-03-01-072112 |
This is an automated cherry-pick of #276
/assign simonpasquier