Skip to content
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 2058172: Add plan status icon update for succeeded rollback #1447

Merged
merged 2 commits into from Jun 15, 2022

Conversation

ibolton336
Copy link
Contributor

@ibolton336 ibolton336 requested a review from a team June 14, 2022 21:11
@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. labels Jun 14, 2022
@openshift-ci
Copy link

openshift-ci bot commented Jun 14, 2022

@ibolton336: This pull request references Bugzilla bug 2058172, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

2 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (xjiang@redhat.com), skipping review request.

In response to this:

Bug 2058172: Add plan status icon update for succeeded rollback

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 openshift-ci bot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Jun 14, 2022
@@ -82,6 +84,12 @@ const PlanStatusIcon: React.FunctionComponent<IProps> = ({ plan }) => {
<ResourcesAlmostEmptyIcon />
</span>
);
} else if (latestAction === 'rollback' && hasSucceededCondition) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ibolton336 you're gonna kill me, but I double checked and there is already a hasSucceededRollback on the plan?.PlanStatus that you can use instead of this line, just like hasSucceededStage and hasSuccededCutover above. See https://github.com/konveyor/mig-ui/blob/master/src/app/plan/duck/selectors.ts#L189-L198

I think that's actually more accurate than this because hasSucceededCondition is based on conditions on the plan and not the migration (I'm not sure if the plan gets a success condition when a rollback succeeds but the rollback's migmigration definitely does)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My thought process here was ok.. maybe there was a succeeded rollback somewhere in the Migration history. But maybe that would be falsely triggered if they re run a migration after the said rollback. I need to look back again and see if that is a valid concern. Wanted to make sure the latest action was a rollback before showing that message. Does that make sense?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops, I see that hasSucceededRollback checks that the latest action is a rollback.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah it's not the best naming :)

Copy link
Collaborator

@mturley mturley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

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

openshift-ci bot commented Jun 15, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ibolton336, mturley

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot merged commit 4c98f07 into migtools:master Jun 15, 2022
@openshift-ci
Copy link

openshift-ci bot commented Jun 15, 2022

@ibolton336: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with /bugzilla refresh.

Bugzilla bug 2058172 has not been moved to the MODIFIED state.

In response to this:

Bug 2058172: Add plan status icon update for succeeded rollback

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants