Bug 787497 - "New volume wizard" not being launched/displayed by virt-manager in KDE
Summary: "New volume wizard" not being launched/displayed by virt-manager in KDE
Keywords:
Status: CLOSED DUPLICATE of bug 749928
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 16
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-05 19:22 UTC by Raul Cheleguini
Modified: 2014-02-24 23:48 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-05 19:29:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Raul Cheleguini 2012-02-05 19:22:30 UTC
Description of problem:

During the storage configuration of a new VM installation process, virt-manager allow us to select an existing volume, but when you try to create a new volume using the wizard, virt-manager seems to hang and you need to close the entire application. This issue doesn't happen in upstream version.

Version-Release number of selected component (if applicable):
virt-manager-0.9.0-7.fc16.noarch

How reproducible:
Always.

Steps to Reproduce:

1. Open new VM creation process
2. In the storage configuration dialog, check "Select managed or other existing storage"
3. Select on pool and click at "New volume"
4. Dialog hangs and nothing is logged  

Actual results:
virt-manager seems to hang.

Expected results:
"New volume wizard" opens.

Current workaround:

Creating new volumes through: 

Edit > Connection Details > Storage > New volume

Additional info:

Nothing in log file.

Using debug entries in "src/virtManager/createvol.py", is possible to see that the method "show" is executed.

    def show(self, parent):
        logging.debug("Showing new volume wizard")
        self.reset_state()
        self.topwin.set_transient_for(parent)
        self.topwin.present()

Sorry but I couldn't figure out what commit in upstream version fix this issue.

Comment 1 Cole Robinson 2012-02-05 19:29:41 UTC
Pretty sure this is fixed by current packages. Please try yum --enablerepo=updates-testing update virt-manager

If you still see the issue, please reopen this bug

*** This bug has been marked as a duplicate of bug 749928 ***

Comment 2 Raul Cheleguini 2012-02-06 22:33:32 UTC
Hi Cole !

Thank you very much, the new "virt-manager-0.9.0-7.fc16.noarch" fixed both issues.

Comment 3 Raul Cheleguini 2012-02-06 22:35:30 UTC
(In reply to comment #2)
> Hi Cole !
> 
> Thank you very much, the new "virt-manager-0.9.0-7.fc16.noarch" fixed both
> issues.

Sorry, the correct package is "virt-manager-0.9.1-1.fc16.noarch".


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