783408 – adding storage disk error

Bug 783408 - adding storage disk error

Summary: adding storage disk error

Keywords:
Status:	CLOSED INSUFFICIENT_DATA
Alias:	None
Product:	Virtualization Tools
Classification:	Community
Component:	virt-manager
Sub Component:
Version:	unspecified
Hardware:	i686
OS:	Unspecified
Priority:	unspecified
Severity:	high
Target Milestone:	---
Assignee:	Cole Robinson
QA Contact:
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2012-01-20 10:33 UTC by dhiaeddine
Modified:	2012-04-02 20:40 UTC (History)
CC List:	3 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2012-04-02 20:40:58 UTC
Embargoed:
Dependent Products:

Attachments	(Terms of Use)
error screenshot (102.07 KB, image/png) 2012-01-20 10:35 UTC, dhiaeddine	no flags	Details
View All

Description dhiaeddine 2012-01-20 10:33:35 UTC

Description of problem:
when I add disk storage disk it show an error :
'NoneType' object has no attribute 'rfind'

Version-Release number of selected component (if applicable): 0.9.0


How reproducible:
add disk storage to an ubuntu 10.04 VM

Steps to Reproduce:

1.open select vm
2.add hardware
3.disk storage
4.finish
  
Actual results:
error

Expected results:


Additional info:

Comment 1 dhiaeddine 2012-01-20 10:35:04 UTC

Created attachment 556492 [details]
error screenshot

Comment 2 Cole Robinson 2012-01-25 01:47:02 UTC

Hmm, can you please provide the output of virt-manager --debug when reproducing?

Comment 3 Cole Robinson 2012-02-05 18:40:16 UTC

I'm pretty sure this was fixed upstream with the latest virtinst release. Please reopen if that's not the case.

Comment 4 dhiaeddine 2012-02-09 17:08:38 UTC

virt-manager --debug output when reproducing


$ virt-manager --debug
2012-02-09 17:58:53,938 (cli:71): virt-manager startup
2012-02-09 17:58:53,938 (virt-manager:292): Launched as: /usr/share/virt-manager/virt-manager.py --debug
2012-02-09 17:58:53,938 (virt-manager:293): GTK version: (2, 22, 0)
2012-02-09 17:58:53,939 (virt-manager:294): virtManager import: <module 'virtManager' from '/usr/share/virt-manager/virtManager/__init__.pyc'>
2012-02-09 17:58:54,233 (engine:555): No inspection thread because libguestfs is too old, not available, or libvirt is not thread safe.
2012-02-09 17:58:54,243 (engine:346): About to connect to uris ['qemu+ssh://admin/system']
2012-02-09 17:58:54,305 (libvirtglib:240): Libvirt version is not new enough for our event loop impl. Skipping registration.
2012-02-09 17:58:54,480 (engine:471): window counter incremented to 1
2012-02-09 17:59:01,292 (connection:954): Scheduling background open thread for qemu+ssh://admin/system
2012-02-09 17:59:01,293 (connection:1140): Background 'open connection' thread is running
2012-02-09 17:59:10,723 (connection:1168): Background open thread complete, scheduling notify
2012-02-09 17:59:10,724 (connection:1173): Notifying open result
2012-02-09 17:59:12,696 (connection:1180): qemu+ssh://admin/system capabilities:
<capabilities>

  <host>
    <cpu>
      <arch>x86_64</arch>
      <model>qemu32</model>
      <topology sockets='1' cores='2' threads='1'/>
      <feature name='lahf_lm'/>
      <feature name='lm'/>
      <feature name='syscall'/>
      <feature name='xtpr'/>
      <feature name='cx16'/>
      <feature name='ssse3'/>
      <feature name='tm2'/>
      <feature name='est'/>
      <feature name='vmx'/>
      <feature name='ds_cpl'/>
      <feature name='monitor'/>
      <feature name='pbe'/>
      <feature name='tm'/>
      <feature name='ht'/>
      <feature name='ss'/>
      <feature name='acpi'/>
      <feature name='ds'/>
      <feature name='clflush'/>
      <feature name='pse36'/>
      <feature name='mca'/>
      <feature name='mtrr'/>
      <feature name='vme'/>
    </cpu>
    <migration_features>
      <live/>
      <uri_transports>
        <uri_transport>tcp</uri_transport>
      </uri_transports>
    </migration_features>
    <secmodel>
      <model>apparmor</model>
      <doi></doi>
    </secmodel>
  </host>

  <guest>
    <os_type>hvm</os_type>
    <arch name='i686'>
      <wordsize>32</wordsize>
      <emulator>/usr/bin/qemu</emulator>
      <machine>pc-0.12</machine>
      <machine canonical='pc-0.12'>pc</machine>
      <machine>pc-0.11</machine>
      <machine>pc-0.10</machine>
      <machine>isapc</machine>
      <domain type='qemu'>
      </domain>
      <domain type='kvm'>
        <emulator>/usr/bin/kvm</emulator>
        <machine>pc-0.12</machine>
        <machine canonical='pc-0.12'>pc</machine>
        <machine>pc-0.11</machine>
        <machine>pc-0.10</machine>
        <machine>isapc</machine>
      </domain>
    </arch>
    <features>
      <cpuselection/>
      <pae/>
      <nonpae/>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
    </features>
  </guest>

  <guest>
    <os_type>hvm</os_type>
    <arch name='x86_64'>
      <wordsize>64</wordsize>
      <emulator>/usr/bin/qemu-system-x86_64</emulator>
      <machine>pc-0.12</machine>
      <machine canonical='pc-0.12'>pc</machine>
      <machine>pc-0.11</machine>
      <machine>pc-0.10</machine>
      <machine>isapc</machine>
      <domain type='qemu'>
      </domain>
      <domain type='kvm'>
        <emulator>/usr/bin/kvm</emulator>
        <machine>pc-0.12</machine>
        <machine canonical='pc-0.12'>pc</machine>
        <machine>pc-0.11</machine>
        <machine>pc-0.10</machine>
        <machine>isapc</machine>
      </domain>
    </arch>
    <features>
      <cpuselection/>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
    </features>
  </guest>

</capabilities>

2012-02-09 17:59:15,401 (connection:514): Connection doesn't seem to support interface APIs. Skipping all interface polling.
2012-02-09 17:59:15,531 (connection:570): Connection managed save support: False
2012-02-09 17:59:16,271 (halhelper:133): Unable to connect to HAL to list network devices: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Hal was not provided by any .service files
2012-02-09 17:59:16,271 (connection:157): Libvirt version does not support physical interface listing
2012-02-09 17:59:16,272 (connection:200): Using libvirt API for mediadev enumeration

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

(virt-manager:16162): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed

2012-02-09 17:59:31,385 (engine:471): window counter incremented to 2
2012-02-09 17:59:40,741 (error:109): Validation Error: Storage parameter error.
2012-02-09 17:59:48,924 (engine:475): window counter decremented to 1

Comment 5 Cole Robinson 2012-02-28 23:54:50 UTC

dhiaeddine, is that using latest virt-manager and python-virtinst? In your first comment you mentioned 0.9.0 which is not the newest virt-manager.

Comment 6 Cole Robinson 2012-04-02 20:40:58 UTC

No response for a month, closing. Please reopen if you are still hitting this with latest virt-manager

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