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

Suspend action allowed for powered-off VM, it should not be allowed. #1653

Open
dmetzger57 opened this issue Jun 24, 2020 · 3 comments
Open

Comments

@dmetzger57
Copy link

Original BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1704221

Description of problem:
Suspend action is allowed for powered off VMs in SSUI. This should be disabled, as we can't suspend powered off VMs.

In OPS UI, when trying to suspend powered off VM, it throws: "Suspend action does not apply to selected items".

Suspend action is allowed for powered off VMs in SSUI. This should be disabled, as we can't suspend powered off VMs.

In OPS UI, when trying to suspend powered off VM, it throws: "Suspend action does not apply to selected items".

This worked properly in Hammer.

How reproducible:
Always

Steps to Reproduce:

  1. Have a service that provisions a VM. Shut it down so the VM enters Powered OFF state.
  2. In SSUI, check different ways to manipulate with VM power:
  • from My Services page
  • from service details page
  • from VM details page - here is the Suspend action disabled, which is correct

Actual results:
Suspend action enabled for powered off VMs

Expected results:
Suspend action should be disabled for powered off VMs, as seen in VM details page in SSUI

@dmetzger57 dmetzger57 added the bug label Jun 24, 2020
@h-kataria
Copy link
Contributor

@himdel do you know if this is still an issue?

@himdel
Copy link
Contributor

himdel commented Jun 25, 2020

Ah, I have an almost-fix for this one #1580

I'll try to get it ready :)

@himdel himdel self-assigned this Jun 25, 2020
@himdel himdel removed their assignment Oct 10, 2022
@miq-bot miq-bot added the stale label Feb 27, 2023
@miq-bot
Copy link
Member

miq-bot commented Feb 27, 2023

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

@Fryguy Fryguy removed the stale label Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants