mike.mcclurg at gmail
Jul 5, 2012, 9:55 AM
Post #2 of 2
On Thu, Jul 5, 2012 at 3:21 AM, George Shuklin <george.shuklin [at] gmail> wrote:
Re: [Pkg-xen-devel] Bug#678923: Acknowledgement (xcp-xapi: host-disable and host-reboot make host disable forever)
[In reply to]
> I've done some additional research on that bug.
> Brief bug description:
> xe host-disable; xe host-reboot make host disabled endlessly after reboot
> without chances to be enabled:
> xe host-enable uuid=
> The specified host is disabled and cannot be re-enabled until after it
> has rebooted
> What I found:
> 1) That settings (host_disabled_until_reboot) is stored in
> Stopping xcp-xapi, removing that file and starting xcp-xapi back works . But
> ugly hack.
> 2) That attribute is written during reboot, initiated by xe host-reboot.
> Question is: what change that value in XCP? xapi or some other startup
Okay, I think that the problem is that we forgot to call xapi with the
-onsystemboot flag in the xcp-xapi.init script. Here is an untested
patch that you should be able to manually apply (as in edit the init
file by hand) to test if this fixes the issue.
I'll push a proper patch to my github soon.
diff --git a/debian/xcp-xapi.init b/debian/xcp-xapi.init
index 055e17b..b3c5959 100755
@@ -23,7 +23,7 @@ PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC="The XenAPI server"
-DAEMON_ARGS="-daemon -writereadyfile $XAPI_STARTUP_COOKIE
+DAEMON_ARGS="-daemon -writereadyfile $XAPI_STARTUP_COOKIE
-writeinitcomplete $XAPI_INIT_COMPLETE_COOKIE -onsystemboot"
Xen-api mailing list
Xen-api [at] lists