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
Bug 1856155: Fixes deletion of node connected to a split node #5934
Bug 1856155: Fixes deletion of node connected to a split node #5934
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewballantyne, rohitkrai03 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 |
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@andrewballantyne: All pull requests linked via external trackers have merged: . Bugzilla bug 1856155 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. |
/cherry-pick release-4.5 |
@andrewballantyne: new pull request created: #5955 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. |
Fixes:
https://issues.redhat.com/browse/ODC-3931
Analysis / Root cause:
When the original logic of Pipeline Builder was written, the code failed to properly handle a deletion of a node that had a runAfter (single or more) and was part of a runAfter that had multiple references. Essentially it just failed to carry over the removal node's runAfters to the the node that was connected to it... thus causing the break.
Solution Description:
Merge the runAfters together so it keeps all the data needed to hold the graph together.
Screen shots / Gifs for design review:
Error:
Fix:
Unit test coverage report:
Will be part of #4805
Test setup:
Crude diagram:
Browser conformance: