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 1834671: Acknowledge strategies when computing if VM is running #5619

Merged
merged 1 commit into from May 29, 2020

Conversation

atiratree
Copy link
Member

  • fix statuses
  • fix visibility of VM action like Restart/Start/Stop
  • disable details edit and nic/disks CRUD actions when VM is running

@openshift-ci-robot openshift-ci-robot added the component/kubevirt Related to kubevirt-plugin label May 28, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 28, 2020
- fix statuses
- fix visibility of VM action like Restart/Start/Stop
- disable details edit and nic/disks CRUD  actions when VM is running
@atiratree atiratree changed the title Acknowledge strategies when computing if VM is running Bug 1834671: Acknowledge strategies when computing if VM is running May 28, 2020
@openshift-ci-robot openshift-ci-robot added bugzilla/severity-high Referenced Bugzilla bug's severity is high 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. labels May 28, 2020
@openshift-ci-robot
Copy link
Contributor

@suomiy: This pull request references Bugzilla bug 1834671, 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.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1834671: Acknowledge strategies when computing if VM is running

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.

Copy link
Contributor

@pcbailey pcbailey left a comment

Choose a reason for hiding this comment

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

One nitpick, but nothing worth holding up the PR.

/lgtm

// according to https://github.com/kubevirt/kubevirt/blob/master/pkg/virt-api/rest/subresource.go
const isFinalPhase =
!vmiPhase || [VMIPhase.Unknown, VMIPhase.Failed, VMIPhase.Succeeded].includes(vmiPhase);
const isVMError = (vm: VMKind): VMStatusBundle => {
Copy link
Contributor

Choose a reason for hiding this comment

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

Nitpick that doesn't need to be addressed now.

Typically, when I see a function that starts with 'is', I expect a boolean return type. I think we should eventually change these function names to better match what they're doing, such as getStoppingStatus. If we need boolean tests for them, it would be trivial to create functions that coerce the return values of these functions to a boolean. Just my two cents.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes I agree. I think we should refactor the whole logic of this file to make more sense. And not be it one dimensional array of ifs. And test it as well.

Nevertheless, I think we should not do it here in this bug fix but a bit later.

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 28, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pcbailey, suomiy

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

@atiratree
Copy link
Member Author

/retest

1 similar comment
@atiratree
Copy link
Member Author

/retest

@openshift-bot
Copy link
Contributor

/retest

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

3 similar comments
@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-merge-robot openshift-merge-robot merged commit 7d1e177 into openshift:master May 29, 2020
@openshift-ci-robot
Copy link
Contributor

@suomiy: All pull requests linked via external trackers have merged: openshift/console#5619, openshift/console#5405. Bugzilla bug 1834671 has been moved to the MODIFIED state.

In response to this:

Bug 1834671: Acknowledge strategies when computing if VM is running

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.

@spadgett spadgett added this to the v4.5 milestone Jun 1, 2020
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-high Referenced Bugzilla bug's severity is high 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. component/kubevirt Related to kubevirt-plugin 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

7 participants