Bug 34065 – Creating a snapshots is not possible, because the domain is currently suspended!

Bug 34065 - Creating a snapshots is not possible, because the domain is currently suspended!


Summary:	Creating a snapshots is not possible, because the domain is currently suspended!

Status:	CLOSED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - Virtual machines (UVMM)
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-02-06 12:51 CET by Arvid Requate
Modified:	2023-06-28 10:51 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arvid Requate

2014-02-06 12:51:36 CET

In the internal KVM test environment the follwing error condition was observed:

After opening an existing, running instance in UMC UVMM and deleting two old snapshots the follwong error message popped up when attempting to create a new snapshot:

Creating a snapshots is not possible, because the domain is currently suspended!

virsh list confirmed that the VM was running and it was accessible via virt-viewer. A manual snapshot via virsh was successfull. Yet the UMC module denies new snapshots, even after closing the module and logging out/in/reopening.

Comment 1 Stefan Gohmann

2017-06-16 20:36:34 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 2 Ingo Steuwer

2020-07-03 20:52:12 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.