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: /rhn/systems/details/virtualization/VirtualGuestsList.do?sid=<sid> Version-Release number of selected component (if applicable): 530, 5/29 build How reproducible: Always 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:
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.