|  |  | 
  
    |  |  | 
 
  |   |  | 
  
    |  |  | 
  
    |  |  | 
  
    |   xen-bugs
[Xen-bugs] [Bug 315]  New: xm block-detach returns stack trace 
| http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=315
           Summary: xm block-detach returns stack trace
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: lge@xxxxxxxxxx
                CC: pl@xxxxxxxxxx
Changeset: 7308
Actually I have seen 04_block-destroy_nonattached_neg.test failed on all my xen
builds when running xm-test.
Instead of returning a nice error message, xm detach-block command return stack
trace when attempting removal pf non-attached device from live domain:
[root@lamb5 block-destroy]# xm block-detach
04_block-destroy_nonattached_neg-1129058039 sda1
Traceback (most recent call last):
  File "/usr/sbin/xm", line 10, in ?
    main.main(sys.argv)
  File "/tmp/xen-unstable.hg/dist/install/usr/lib/python/xen/xm/main.py", line
706, in main
    handle_xend_error(argv[1], args[0], ex)
  File "/tmp/xen-unstable.hg/dist/install/usr/lib/python/xen/xm/main.py", line
174, in handle_xend_error
    raise ex
xen.xend.XendProtocol.XendError: Exception: invalid literal for int(): sda1
-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs
 | 
 
| <Prev in Thread] | Current Thread | [Next in Thread> |  | 
[Xen-bugs] [Bug 315]  New: xm block-detach returns stack trace,
bugzilla-daemon <=
 |  |  | 
  
    |  |  |