Bug 503982 - If virt guest creation fails, guest still reported as being present in virtualization details list
If virt guest creation fails, guest still reported as being present in virtua...
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Virtualization (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Devan Goodwin
Brandon Perkins
Depends On:
  Show dependency treegraph
Reported: 2009-06-03 12:55 EDT by Steve Salevan
Modified: 2009-06-04 12:43 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-06-04 12:43:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Steve Salevan 2009-06-03 12:55:35 EDT
Description of problem:
If a user attempts to provision a virtualized guest upon a host machine and this attempt fails, the guest will still be reported as present upon the virtualization details list located here:


Version-Release number of selected component (if applicable):
530, 5/29 build

How reproducible:

Steps to Reproduce:
1. Attempt to provision a virtualized guest, but cause this attempt to fail (there are myriad methods for accomplishing this feat, but you might try changing the virtual bridge device to something nonexistent to reproduce this issue)
2. Check /rhn/systems/details/virtualization/VirtualGuestsList.do?sid=<sid>
Actual results:
Guest appears in list

Expected results:
Guest does not appear in list

Additional info:
Comment 1 Brandon Perkins 2009-06-04 12:43:01 EDT
Closed as NOTABUG.  This functions as designed.  Any guest that ever exist should show up in the list, regardless if it completes or not.  Once a person comes back and sees that the guest failed, they can delete the system themselves.  We want to avoid the case where a kickstart is done, it fails, and then nothing shows up in the virt guest list confusing the customer into not knowing where that provisioning attempt went.

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