Bug 978407 – Problem for redefining an openvz when halted from the inside

Bug 978407 - Problem for redefining an openvz when halted from the inside

Summary:	Problem for redefining an openvz when halted from the inside

Status:	CLOSED DEFERRED

Aliases:	None

Product:	Virtualization Tools
Classification:	Community
Component:	libvirt (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	Unspecified Linux

Priority	unspecified Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Libvirt Maintainers
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2013-06-26 10:29 EDT by Manuel VIVES
Modified:	2016-04-09 19:47 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-04-09 19:47:35 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Description Manuel VIVES 2013-06-26 10:29:25 EDT

Description of problem:
When you halt an openvz container from the inside, you will be able to undefine it but then you won't be able to redefine it.

Version-Release number of selected component (if applicable):
1.0.6 (lastest debian package)

How reproducible:
Create a program using the API (The problem doesn't appear when virsh is used)

Steps to Reproduce:
1. Start an openvz container and then halt it from the inside
2. Undefine it
3. Try to redefine it without reloading your program

Actual results:
libvirt: OpenVZ Driver error : operation failed: Already an OPENVZ VM active 
with the id

Expected results:
It shoud work

Additional info:
It seems that the commit ea92a34d1d7d681d9f25dc3348513889b28cbfb5 is faulty, 
but there may be some side effects to just delete it.

Comment 1 Cole Robinson 2016-04-09 19:47:35 EDT

Sorry this didn't receive a timely response. That error string isn't even in the code anymore so I suspect this is no longer an issue. If you can still reproduce with recent libvirt, please reopen

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