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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 2101335: Clone action enabled for CrashLoopBackOff #738

Merged
merged 1 commit into from Jul 7, 2022

Conversation

glekner
Copy link
Contributor

@glekner glekner commented Jul 6, 2022

馃摑 Description

Add a brief description

馃帴 Demo

Please add a video or an image of the behavior/changes

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 6, 2022

@glekner: This pull request references Bugzilla bug 2101335, 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.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.12.0) matches configured target release for branch (4.12.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @gouyang

In response to this:

Bug 2101335: Clone action enabled for CrashLoopBackOff

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 approved This issue is something we want to fix label Jul 6, 2022
@openshift-ci openshift-ci bot requested a review from gouyang July 6, 2022 15:11
@avivtur
Copy link
Member

avivtur commented Jul 6, 2022

/lgtm

1 similar comment
@metalice
Copy link
Member

metalice commented Jul 6, 2022

/lgtm

@openshift-ci openshift-ci bot added the lgtm Passed code review, ready for merge label Jul 6, 2022
Copy link
Member

@hstastna hstastna left a comment

Choose a reason for hiding this comment

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

Looks like the fix does not include other error-like states. What about them? There is the additional info in the BZ:

Additional info: Also reproduced with other error states like ErrImagePull or ImagePullBackOff.

Seems to me that there may be more states we should take care of. Maybe it would be good to check/include all possible error-like states. If there are too many such states, maybe it worth to fix this the opposite way: to create an array with the states that are okay for cloning and then to check if the actual state is in that array. And if not, then to disable cloning.

@openshift-ci openshift-ci bot removed the lgtm Passed code review, ready for merge label Jul 6, 2022
@@ -21,6 +21,7 @@ export const printableVMStatus = {
Terminating: 'Terminating',
Failed: 'Failed',
Unknown: 'Unknown',
CrashLoopBackOff: 'CrashLoopBackOff',
Copy link
Member

@upalatucci upalatucci Jul 6, 2022

Choose a reason for hiding this comment

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

This will add a new filter in the VM list

Screenshot from 2022-07-06 18-31-45

I suggest to filter it here or creating a different array/object for the filters

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@upalatucci @hstastna thanks, ill take a look

@glekner
Copy link
Contributor Author

glekner commented Jul 7, 2022

@avivtur @upalatucci @hstastna

please note all the possible vm statuses here

I fixed isFailedPrintableStatus and clone is now only enabled if the vm is paused to stopped

@upalatucci
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Passed code review, ready for merge label Jul 7, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 7, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: avivtur, glekner, metalice, upalatucci

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:
  • OWNERS [avivtur,glekner,metalice]

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

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci openshift-ci bot merged commit d1d41db into kubevirt-ui:main Jul 7, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 7, 2022

@glekner: All pull requests linked via external trackers have merged:

Bugzilla bug 2101335 has been moved to the MODIFIED state.

In response to this:

Bug 2101335: Clone action enabled for CrashLoopBackOff

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 This issue is something we want to fix bugzilla/severity-high bugzilla/valid-bug lgtm Passed code review, ready for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants