Bug 705708 - Save virtual machine with blank name, the vm has no response, without any error info pop-up
Summary: Save virtual machine with blank name, the vm has no response, without any err...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-manager
Version: 5.7
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: ---
: 5.7
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-18 08:01 UTC by Huming Jiang
Modified: 2011-07-12 23:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-12 23:54:25 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Huming Jiang 2011-05-18 08:01:35 UTC
Description of problem:
There is a running vm guest, click "Virtual Machine->Save", leave "name" edit box blank, and click "Save" button, the vm has no response, without any error info pop-up.

Version-Release number of selected component (if applicable):
kernel-xen-2.6.18-261.el5
xen-3.0.3-131.el5
libvirt-0.8.2-20.el5
virt-manager-0.6.1-14.el5

How reproducible:
Always

Steps to Reproduce:
Make sure there exists a running vm guest.
1."Virtual Machine->Save"
2.leave ""name" edit box blank, and click "Save" button.

  
Actual results:
The vm has no response, without any error info pop-up

Expected results:
There should be an error info pop-up to tell the user the name box could not be blank.

Additional info:

Comment 1 Huming Jiang 2011-05-18 08:23:31 UTC
Similar phenomenon has existed in the process of "Take Screenshot".

Comment 2 RHEL Program Management 2011-06-21 05:27:36 UTC
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.7 and Red Hat does not plan to fix this issue the currently developed update.

Contact your manager or support representative in case you need to escalate this bug.

Comment 4 Cole Robinson 2011-07-12 23:54:25 UTC
Since this has pretty low impact I don't think it's worth fixing at this point in RHEL5. Closing as WONTFIX


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