Bug 490673 - Reactivating a virt guest does not update virt info (UUID, virt memory, etc..)
Summary: Reactivating a virt guest does not update virt info (UUID, virt memory, etc..)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Registration
Version: 530
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Todd Sanders
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2009-03-17 15:41 UTC by Justin Sherrill
Modified: 2014-05-09 10:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-09 10:39:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot (175.94 KB, image/png)
2009-03-17 15:42 UTC, Justin Sherrill
no flags Details

Description Justin Sherrill 2009-03-17 15:41:31 UTC
1.  Provision a virt guest.
2.  Delete the virt guest from the host.
3.  Provision a new virt guest and activate it with a re-activation token from the first guests profile (we want the new guest to take the place of the old).


Expected results:  The virt host should only list one guest.  Instead it lists 2.  The registered systems profile with the old UUID, and the new 'virt' profile without a registered system associated.  See screenshot.

Comment 1 Justin Sherrill 2009-03-17 15:42:19 UTC
Created attachment 335540 [details]
screenshot

Comment 2 Justin Sherrill 2009-03-17 16:17:26 UTC
For clarification, "2.  Delete the virt guest from the host" means to stop the guest running on the host and delete it's configs/disk.  It DOES NOT mean delete the profile on the satellite.

Comment 89 Clifford Perry 2014-05-09 10:39:00 UTC
We have not addressed this specific bug in over 5 years years. This does not seem to have an active customer case with the bug report either. Closing out as wontfix to clear from backlog. 

Please re-open if you disagree and wish further review.

Cliff


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