Bug 629016

Summary:	[RFE] Flag images as migrated after they have been migrated on the previous host.
Product:	[Community] Virtualization Tools	Reporter:	Jóhann B. Guðmundsson <johannbg>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	berrange, crobinso, hbrock, jforbes, virt-maint, xen-maint
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-07 23:56:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jóhann B. Guðmundsson 2010-08-31 17:00:01 UTC

Description of problem:
 
After a user has ( Live ) migrated vm image to another server flag that image ( perhaps new icon instead of the shutdown one ) and warn the user and/or prevent him to start the migrated image ( unless overwritten ) on the host that the image just got live migrated from.

Version-Release number of selected component (if applicable):

virt-manager-0.8.5-1.fc13

How reproducible:

Always

Steps to Reproduce:
1. Live migrate vm to another host
2. Run the vm that just got migrated and is mark as shutoff on the previous host 
3.
  
Actual results:

The user can run the image again on the previous host.

Expected results:

User not being able to run the newly migrated image which is already running on the new host on the previous host.

Additional info:

Comment 1 Bug Zapper 2011-05-31 14:54:10 UTC

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Cole Robinson 2011-06-10 17:23:06 UTC

Moving to upstream tracker. The whole preventing guests from being started twice if they use the same storage is the goal of libvirt's locking driver stuff (fairly new so not likely to arrive until f16)

Comment 3 Cole Robinson 2012-02-07 23:56:40 UTC

I think the main problem here is that we leave the guest defined on the source host by default. We shouldn't do that. There's another bug tracking that issue

*** This bug has been marked as a duplicate of bug 733388 ***