[release-4.10] Bug 2101412: fix bug where Cluster update modal errors weren't displa… #11765

openshift-cherrypick-robot · 2022-06-27T12:16:29Z

This is an automated cherry-pick of #11762

/assign rhamilto

…ying

rhamilto · 2022-06-27T12:17:29Z

/backport-risk-assessed

/lgtm

openshift-ci · 2022-06-27T12:17:53Z

@openshift-cherrypick-robot: Bugzilla bug 2096350 has been cloned as Bugzilla bug 2101412. Retitling PR to link against new bug.
/retitle [release-4.10] Bug 2101412: fix bug where Cluster update modal errors weren't displa…

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 kubernetes/test-infra repository.

openshift-ci · 2022-06-27T12:18:09Z

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2101412, which is invalid:

expected dependent Bugzilla bug 2096350 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

openshift-ci · 2022-06-27T12:19:53Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, rhamilto

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:

~~frontend/OWNERS~~ [rhamilto]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci · 2022-06-27T12:19:54Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, rhamilto

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:

~~frontend/OWNERS~~ [rhamilto]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-bot · 2022-06-28T01:00:38Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-06-28T01:00:43Z

@openshift-bot: This pull request references Bugzilla bug 2101412, which is invalid:

expected dependent Bugzilla bug 2096350 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

openshift-bot · 2022-06-29T01:01:17Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-06-29T01:01:29Z

@openshift-bot: This pull request references Bugzilla bug 2101412, which is invalid:

expected dependent Bugzilla bug 2096350 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

openshift-bot · 2022-06-30T01:01:15Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-06-30T01:01:45Z

@openshift-bot: This pull request references Bugzilla bug 2101412, which is invalid:

expected dependent Bugzilla bug 2096350 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

openshift-bot · 2022-07-01T01:01:09Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-01T01:03:18Z

@openshift-bot: This pull request references Bugzilla bug 2101412, which is invalid:

expected dependent Bugzilla bug 2096350 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

openshift-bot · 2022-07-02T01:00:41Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-02T01:01:06Z

@openshift-bot: This pull request references Bugzilla bug 2101412, which is invalid:

expected dependent Bugzilla bug 2096350 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

openshift-bot · 2022-07-03T01:00:40Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-03T01:01:03Z

@openshift-bot: This pull request references Bugzilla bug 2101412, which is invalid:

expected dependent Bugzilla bug 2096350 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

openshift-bot · 2022-07-04T01:00:42Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-04T01:01:10Z

@openshift-bot: This pull request references Bugzilla bug 2101412, which is invalid:

expected dependent Bugzilla bug 2096350 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

openshift-ci · 2022-07-21T01:01:24Z

@openshift-bot: This pull request references Bugzilla bug 2101412, which is invalid:

expected dependent Bugzilla bug 2104951 to target a release in 4.11.0, but it targets "4.11.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

openshift-bot · 2022-07-22T01:00:32Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-22T01:00:47Z

@openshift-bot: This pull request references Bugzilla bug 2101412, which is invalid:

expected dependent Bugzilla bug 2104951 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2104951 to target a release in 4.11.0, but it targets "4.11.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

openshift-bot · 2022-07-23T01:00:37Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-23T01:00:59Z

@openshift-bot: This pull request references Bugzilla bug 2101412, which is invalid:

expected dependent Bugzilla bug 2104951 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2104951 to target a release in 4.11.0, but it targets "4.11.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

openshift-bot · 2022-07-24T01:00:38Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-24T01:01:02Z

@openshift-bot: This pull request references Bugzilla bug 2101412, which is invalid:

expected dependent Bugzilla bug 2104951 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2104951 to target a release in 4.11.0, but it targets "4.11.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

openshift-bot · 2022-07-25T01:00:41Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-25T01:01:06Z

@openshift-bot: This pull request references Bugzilla bug 2101412, which is invalid:

expected dependent Bugzilla bug 2104951 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2104951 to target a release in 4.11.0, but it targets "4.11.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

openshift-bot · 2022-07-26T01:00:38Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-26T01:00:55Z

@openshift-bot: This pull request references Bugzilla bug 2101412, which is invalid:

expected dependent Bugzilla bug 2104951 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2104951 to target a release in 4.11.0, but it targets "4.11.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

rhamilto · 2022-07-26T12:05:40Z

/bugzilla refresh

openshift-ci · 2022-07-26T12:05:53Z

@rhamilto: This pull request references Bugzilla bug 2101412, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.10.z) matches configured target release for branch (4.10.z)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 2104951 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
dependent Bugzilla bug 2104951 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
bug has dependents

Requesting review from QA contact:
/cc @yapei

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 kubernetes/test-infra repository.

rhamilto · 2022-07-26T12:06:33Z

/cherry-pick release-4.9

openshift-cherrypick-robot · 2022-07-26T12:06:35Z

@rhamilto: once the present PR merges, I will cherry-pick it on top of release-4.9 in a new PR and assign it to you.

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 kubernetes/test-infra repository.

yapei · 2022-07-27T07:11:26Z

upgrade errors are shown in the modal /label qe-approved

rhamilto · 2022-08-01T11:23:14Z

/cherry-pick release-4.9

openshift-cherrypick-robot · 2022-08-01T11:23:15Z

@rhamilto: once the present PR merges, I will cherry-pick it on top of release-4.9 in a new PR and assign it to you.

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 kubernetes/test-infra repository.

yapei · 2022-08-03T03:09:05Z

/label cherry-pick-approved

openshift-ci-robot · 2022-08-03T05:12:51Z

/retest-required

Remaining retests: 2 against base HEAD dee1944 and 8 for PR HEAD 1dd4582 in total

openshift-ci · 2022-08-03T07:50:51Z

@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.

openshift-ci · 2022-08-03T07:53:41Z

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

openshift/console#11765

Bugzilla bug 2101412 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 kubernetes/test-infra repository.

openshift-cherrypick-robot · 2022-08-03T07:54:44Z

@rhamilto: #11765 failed to apply on top of branch "release-4.9":

Applying: Bug 2096350: fix bug where Cluster update modal errors weren't displaying
Using index info to reconstruct a base tree...
M	frontend/public/components/modals/cluster-update-modal.tsx
Falling back to patching base and 3-way merge...
Auto-merging frontend/public/components/modals/cluster-update-modal.tsx
CONFLICT (content): Merge conflict in frontend/public/components/modals/cluster-update-modal.tsx
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Bug 2096350: fix bug where Cluster update modal errors weren't displaying
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

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 kubernetes/test-infra repository.

Bug 2096350: fix bug where Cluster update modal errors weren't displa…

1dd4582

…ying

openshift-cherrypick-robot mentioned this pull request Jun 27, 2022

Bug 2096350: fix bug where Cluster update modal errors weren't displa… #11762

Merged

openshift-ci bot assigned rhamilto Jun 27, 2022

openshift-ci bot changed the title ~~[release-4.10] Bug 2096350: fix bug where Cluster update modal errors weren't displa…~~ [release-4.10] Bug 2101412: fix bug where Cluster update modal errors weren't displa… Jun 27, 2022

openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jun 27, 2022

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 27, 2022

openshift-ci bot requested review from dtaylor113 and jhadvig June 27, 2022 12:19

openshift-ci bot added the component/core Related to console core functionality label Jun 27, 2022

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 27, 2022

openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jul 26, 2022

openshift-ci bot requested a review from yapei July 26, 2022 12:05

openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jul 27, 2022

openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Aug 3, 2022

openshift-ci bot merged commit 52487b0 into openshift:release-4.10 Aug 3, 2022

rhamilto mentioned this pull request Aug 3, 2022

[release-4.9] Bug 2114863: fix bug where Cluster update modal errors weren't displa… #11926

Merged

[release-4.10] Bug 2101412: fix bug where Cluster update modal errors weren't displa… #11765

[release-4.10] Bug 2101412: fix bug where Cluster update modal errors weren't displa… #11765

Conversation

openshift-cherrypick-robot commented Jun 27, 2022

rhamilto commented Jun 27, 2022

openshift-ci bot commented Jun 27, 2022

openshift-ci bot commented Jun 27, 2022

openshift-ci bot commented Jun 27, 2022

openshift-ci bot commented Jun 27, 2022

openshift-bot commented Jun 28, 2022

openshift-ci bot commented Jun 28, 2022

openshift-bot commented Jun 29, 2022

openshift-ci bot commented Jun 29, 2022

openshift-bot commented Jun 30, 2022

openshift-ci bot commented Jun 30, 2022

openshift-bot commented Jul 1, 2022

openshift-ci bot commented Jul 1, 2022

openshift-bot commented Jul 2, 2022

openshift-ci bot commented Jul 2, 2022

openshift-bot commented Jul 3, 2022

openshift-ci bot commented Jul 3, 2022

openshift-bot commented Jul 4, 2022

openshift-ci bot commented Jul 4, 2022

openshift-ci bot commented Jul 21, 2022

openshift-bot commented Jul 22, 2022

openshift-ci bot commented Jul 22, 2022

openshift-bot commented Jul 23, 2022

openshift-ci bot commented Jul 23, 2022

openshift-bot commented Jul 24, 2022

openshift-ci bot commented Jul 24, 2022

openshift-bot commented Jul 25, 2022

openshift-ci bot commented Jul 25, 2022

openshift-bot commented Jul 26, 2022

openshift-ci bot commented Jul 26, 2022

rhamilto commented Jul 26, 2022

openshift-ci bot commented Jul 26, 2022

rhamilto commented Jul 26, 2022

openshift-cherrypick-robot commented Jul 26, 2022

yapei commented Jul 27, 2022

rhamilto commented Aug 1, 2022

openshift-cherrypick-robot commented Aug 1, 2022

yapei commented Aug 3, 2022

openshift-ci-robot commented Aug 3, 2022

openshift-ci bot commented Aug 3, 2022

openshift-ci bot commented Aug 3, 2022

openshift-cherrypick-robot commented Aug 3, 2022