console
console copied to clipboard
[release-4.14] OCPBUGS-33145: Fix "Auto deploy when new image is available" becomes unchecked when editing a deployment from web console
manual cherry-pick of https://github.com/openshift/console/pull/14177 and https://github.com/openshift/console/pull/13783
@vikram-raj: This pull request references Jira Issue OCPBUGS-33145, which is valid. The bug has been moved to the POST state.
9 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.14.z) matches configured target version for branch (4.14.z)
- 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-38764 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
- dependent bug Jira Issue OCPBUGS-32506 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
- dependent Jira Issue OCPBUGS-38764 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
- dependent Jira Issue OCPBUGS-32506 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
- bug has dependents
Requesting review from QA contact: /cc @sanketpathak
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.
@vikram-raj: This pull request references Jira Issue OCPBUGS-33145, which is valid.
9 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.14.z) matches configured target version for branch (4.14.z)
- bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
- release note type set to "Release Note Not Required"
- dependent bug Jira Issue OCPBUGS-38764 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
- dependent bug Jira Issue OCPBUGS-32506 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
- dependent Jira Issue OCPBUGS-38764 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
- dependent Jira Issue OCPBUGS-32506 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
- bug has dependents
Requesting review from QA contact: /cc @sanketpathak
In response to this:
manual cherry-pick of https://github.com/openshift/console/pull/14177 and https://github.com/openshift/console/pull/13783
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.
@vikram-raj: you cannot LGTM your own PR.
In response to this:
Verified
https://github.com/user-attachments/assets/48733b07-4b9e-42e8-a707-bf42b58285b3
/lgtm
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.
/label backport-risk-assessed
/assign @lokanandaprabhu
Assigning for lgtm
@vikram-raj: GitHub didn't allow me to assign the following users: lokanandaprabhu.
Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
In response to this:
/assign @lokanandaprabhu
Assigning for lgtm
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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: lokanandaprabhu, vikram-raj
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~frontend/packages/dev-console/OWNERS~~ [vikram-raj]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/label cherry-pick-approved
/label qe-approved
@vikram-raj: This pull request references Jira Issue OCPBUGS-33145, which is valid.
9 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.14.z) matches configured target version for branch (4.14.z)
- bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
- release note type set to "Release Note Not Required"
- dependent bug Jira Issue OCPBUGS-32506 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
- dependent bug Jira Issue OCPBUGS-38764 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
- dependent Jira Issue OCPBUGS-32506 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
- dependent Jira Issue OCPBUGS-38764 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
- bug has dependents
Requesting review from QA contact: /cc @sanketpathak
In response to this:
manual cherry-pick of https://github.com/openshift/console/pull/14177 and https://github.com/openshift/console/pull/13783
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.
@vikram-raj: 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-sigs/prow repository. I understand the commands that are listed here.
@vikram-raj: Jira Issue OCPBUGS-33145: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-33145 has been moved to the MODIFIED state.
In response to this:
manual cherry-pick of https://github.com/openshift/console/pull/14177 and https://github.com/openshift/console/pull/13783
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]
Distgit: openshift-enterprise-console This PR has been included in build openshift-enterprise-console-container-v4.14.0-202501171105.p0.g8a923f6.assembly.stream.el8. All builds following this will include this PR.
Fix included in accepted release 4.14.0-0.nightly-2025-01-17-123058