[release-4.22] OCPBUGS-84216: Fix create visual connector in Topology by openshift-cherrypick-robot · Pull Request #16314 · openshift/console

openshift-cherrypick-robot · 2026-04-22T07:37:59Z

This is an automated cherry-pick of #16241

/assign vikram-raj

openshift-ci-robot · 2026-04-22T07:38:04Z

@openshift-cherrypick-robot: An error was encountered cloning bug for cherrypick for bug OCPBUGS-78365 on the Jira server at https://redhat.atlassian.net. No known errors were detected, please see the full error message for details.

Full error message.


request failed. Please analyze the request body for more details. Status code: 400: {"errorMessages":["QA Contact: User 'Ya Dan Pei' is not valid for this user picker."],"errors":{"customfield_10470":"User 'Ya Dan Pei' is not valid for this user picker."}}

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

Details

In response to this:

This is an automated cherry-pick of #16241

/assign vikram-raj

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 · 2026-04-22T13:39:56Z

/jira refresh

openshift-ci-robot · 2026-04-22T13:40:04Z

@vikram-raj: This pull request references Jira Issue OCPBUGS-78365, which is invalid:

expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-78365 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

/jira refresh

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 · 2026-04-23T07:59:21Z

/retitle [release-4.22] OCPBUGS-84216: Fix create visual connector in Topology

openshift-ci-robot · 2026-04-23T07:59:40Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-84216, which is invalid:

expected dependent Jira Issue OCPBUGS-78365 to target a version in 5.0.0, but it targets "4.22.0" instead

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

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #16241

/assign vikram-raj

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 · 2026-04-23T08:00:51Z

/jira refresh

openshift-ci-robot · 2026-04-23T08:00:59Z

@vikram-raj: This pull request references Jira Issue OCPBUGS-84216, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
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-78365 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
dependent Jira Issue OCPBUGS-78365 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
bug has dependents

Requesting review from QA contact:
/cc @yapei

Details

In response to this:

/jira refresh

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.

openshift-ci · 2026-04-23T08:01:02Z

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: yapei.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

@vikram-raj: This pull request references Jira Issue OCPBUGS-84216, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

bug is open, matching expected state (open)

bug target version (4.22.0) matches configured target version for branch (4.22.0)

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-78365 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)

dependent Jira Issue OCPBUGS-78365 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0

bug has dependents

Requesting review from QA contact:
/cc @yapei

In response to this:

/jira refresh

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.

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.

vikram-raj · 2026-04-23T08:01:18Z

/retest

vikram-raj · 2026-04-23T08:01:59Z

/label backport-risk-assessed

vikram-raj

/approve

openshift-merge-robot · 2026-04-23T19:08:14Z

Fix included in release 5.0.0-0.nightly-2026-04-21-191046

vikram-raj · 2026-04-28T06:59:41Z

/retest

vikram-raj

/lgtm

/verified by @vikram-raj

vikram-raj · 2026-04-28T10:15:08Z

/cherry-pick release-4.21

openshift-ci · 2026-04-28T10:15:10Z

[APPROVALNOTIFIER] This PR is APPROVED

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

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~frontend/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

openshift-cherrypick-robot · 2026-04-28T10:15:11Z

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

Details

In response to this:

/cherry-pick release-4.21

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.

vikram-raj · 2026-04-28T11:40:45Z

/verified by @vikram-raj

openshift-ci-robot · 2026-04-28T11:40:56Z

@vikram-raj: This PR has been marked as verified by @vikram-raj.

Details

In response to this:

/verified by @vikram-raj

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.

openshift-ci · 2026-04-28T12:23:15Z

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

openshift-ci-robot · 2026-04-28T12:29:51Z

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-84216
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-84216 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

This is an automated cherry-pick of #16241

/assign vikram-raj

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.

openshift-cherrypick-robot · 2026-04-28T12:30:37Z

@vikram-raj: #16314 failed to apply on top of branch "release-4.21":

Applying: Fix create visual connector in Topology
Using index info to reconstruct a base tree...
M	frontend/packages/console-dynamic-plugin-sdk/src/extensions/topology-types.ts
M	frontend/packages/topology/src/behavior/withCreateConnector.tsx
M	frontend/packages/topology/src/components/graph-view/components/nodes/BaseNode.tsx
M	frontend/packages/topology/src/components/graph-view/components/nodes/WorkloadNode.tsx
Falling back to patching base and 3-way merge...
Auto-merging frontend/packages/topology/src/components/graph-view/components/nodes/WorkloadNode.tsx
CONFLICT (content): Merge conflict in frontend/packages/topology/src/components/graph-view/components/nodes/WorkloadNode.tsx
Auto-merging frontend/packages/topology/src/components/graph-view/components/nodes/BaseNode.tsx
CONFLICT (content): Merge conflict in frontend/packages/topology/src/components/graph-view/components/nodes/BaseNode.tsx
Auto-merging frontend/packages/topology/src/behavior/withCreateConnector.tsx
CONFLICT (content): Merge conflict in frontend/packages/topology/src/behavior/withCreateConnector.tsx
Auto-merging frontend/packages/console-dynamic-plugin-sdk/src/extensions/topology-types.ts
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Fix create visual connector in Topology

Details

In response to this:

/cherry-pick release-4.21

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.

openshift-merge-robot · 2026-04-29T18:00:10Z

Fix included in release 4.22.0-0.nightly-2026-04-29-114113

Fix create visual connector in Topology

711fcca

openshift-cherrypick-robot assigned vikram-raj Apr 22, 2026

openshift-cherrypick-robot mentioned this pull request Apr 22, 2026

OCPBUGS-78365: Fix create visual connector in Topology #16241

Merged

openshift-ci Bot requested review from sg00dwin and stefanonardo April 22, 2026 07:38

openshift-ci Bot added component/sdk Related to console-plugin-sdk component/topology Related to topology plugin-api-changed Categorizes a PR as containing plugin API changes labels Apr 22, 2026

openshift-ci Bot assigned jhadvig, logonoff, spadgett and vojtechszocs Apr 22, 2026

openshift-ci Bot changed the title ~~[release-4.22] OCPBUGS-78365: Fix create visual connector in Topology~~ [release-4.22] OCPBUGS-84216: Fix create visual connector in Topology Apr 23, 2026

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 23, 2026

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Apr 23, 2026

openshift-ci Bot assigned sanketpathak Apr 23, 2026

vikram-raj approved these changes Apr 23, 2026

View reviewed changes

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 23, 2026

jhadvig added plugin-api-approved Indicates a PR with plugin API changes has been approved by an API reviewer and removed plugin-api-changed Categorizes a PR as containing plugin API changes labels Apr 28, 2026

vikram-raj reviewed Apr 28, 2026

View reviewed changes

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 28, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 28, 2026

openshift-merge-bot Bot merged commit 5608753 into openshift:release-4.22 Apr 28, 2026
7 checks passed

Conversation

openshift-cherrypick-robot commented Apr 22, 2026

Uh oh!

openshift-ci-robot commented Apr 22, 2026

Uh oh!

vikram-raj commented Apr 22, 2026

Uh oh!

openshift-ci-robot commented Apr 22, 2026

Uh oh!

vikram-raj commented Apr 23, 2026

Uh oh!

openshift-ci-robot commented Apr 23, 2026

Uh oh!

vikram-raj commented Apr 23, 2026

Uh oh!

openshift-ci-robot commented Apr 23, 2026

Uh oh!

openshift-ci Bot commented Apr 23, 2026

Uh oh!

vikram-raj commented Apr 23, 2026

Uh oh!

vikram-raj commented Apr 23, 2026

Uh oh!

vikram-raj left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-merge-robot commented Apr 23, 2026

Uh oh!

vikram-raj commented Apr 28, 2026

Uh oh!

vikram-raj left a comment

Choose a reason for hiding this comment

Uh oh!

vikram-raj commented Apr 28, 2026

Uh oh!

openshift-ci Bot commented Apr 28, 2026

Uh oh!

openshift-cherrypick-robot commented Apr 28, 2026

Uh oh!

vikram-raj commented Apr 28, 2026

Uh oh!

openshift-ci-robot commented Apr 28, 2026

Uh oh!

openshift-ci Bot commented Apr 28, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Apr 28, 2026

Uh oh!

openshift-cherrypick-robot commented Apr 28, 2026

Uh oh!

openshift-merge-robot commented Apr 29, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

9 participants