[Xen-bugs] [Bug 1679] New: Documentation for on_powerdown doesn't match actual options

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1679

           Summary: Documentation for on_powerdown doesn't match actual
                    options
           Product: Xen
           Version: unspecified
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: cmattair@xxxxxxx


Didn't see my configuration on the pulldowns but SuSE claims it to be
3.3.1_18546_23_0.4.13-i1586, OpenSuSE 11.1, 2.6.27.48-0.3-xen.
The example xm create scripts state
# Configure the behaviour when a domain exits.  There are three 'reasons'
# for a domain to stop: poweroff, reboot, and crash.  For each of these you
# may specify:
...
#   "preserve",       meaning that no clean-up is done until the domain is
#                     manually destroyed (using xm destroy, for example); or
...
However, if one looks in XendAPIConstants.py, you see:
   XEN_API_ON_NORMAL_EXIT = [
       'destroy',
       'restart',
   ]

'Preserve' is not an option for a normal shutdown which I think a reasonable
thing to do.  Recreating the domain each time I restart it doesn't fit well
in a /etc/init.d world.

Also, a slightly more understandable error than
  File "/usr/lib/python2.6/site-packages/xen/xm/xenapi_create.py", line 588, in
conv_chk
    raise "Invalid value: " + val
TypeError: exceptions must be classes or instances, not str
might be in order.


-- 
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