Bug 490673 - Reactivating a virt guest does not update virt info (UUID, virt memory, etc..)
Reactivating a virt guest does not update virt info (UUID, virt memory, etc..)
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Registration (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Todd Sanders
Red Hat Satellite QA List
: FutureFeature
Depends On:
Blocks: 462714
  Show dependency treegraph
Reported: 2009-03-17 11:41 EDT by Justin Sherrill
Modified: 2014-05-09 06:39 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-05-09 06:39:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

  None (edit)
Description Justin Sherrill 2009-03-17 11:41:31 EDT
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 11:42:19 EDT
Created attachment 335540 [details]
Comment 2 Justin Sherrill 2009-03-17 12:17:26 EDT
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 06:39:00 EDT
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.


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