[Pkg-xen-devel] Bug#680102: More fixes for xen-api in Wheezy

[Mike McClurg]

On Sat, Jul 7, 2012 at 11:01 PM, George Shuklin
<george.shuklin at gmail.com> wrote:
> Here results:
> # mkdir  /etc/firstboot.d/
> # mkdir  /etc/firstboot.d/data
> # xe pool-eject host-uuid=a6806a39-442d-f17d-b7a0-59161d18f562
>
> WARNING: Ejecting a host from the pool will reinitialise that host's local
> SRs.
> WARNING: Any data contained with the local SRs will be lost.
> Type 'yes' to continue
> yes
> The server failed to handle your request, due to an internal error. The
> given message may give details useful for debugging the problem.
> message: Failure("Error while calling xen-cmdline script")
>
>
> log snippet:
>
> [20120707T21:55:24.695Z|debug|lab-xh3|699 INET 127.0.0.1:80|pool.eject
> R:a16c35a5d1d4|xapi] Raised at forkhelpers.ml:181.30-76 ->
> pervasiveext.ml:22.2-9
> [20120707T21:55:24.695Z|debug|lab-xh3|699 INET 127.0.0.1:80|pool.eject
> R:a16c35a5d1d4|backtrace] Raised at pervasives.ml:22.22-33 ->
> list.ml:57.20-23 -> xapi_pool.ml:830.9-125 -> rbac.ml:229.16-23
> [20120707T21:55:24.697Z|debug|lab-xh3|699 INET 127.0.0.1:80|pool.eject
> R:a16c35a5d1d4|backtrace] Raised at rbac.ml:238.10-15 ->
> server_helpers.ml:72.10-22
> [20120707T21:55:24.697Z|debug|lab-xh3|699 INET 127.0.0.1:80|pool.eject
> R:a16c35a5d1d4|dispatcher] Server_helpers.exec exception_handler: Got
> exception INTERNAL_ERROR: [ Failure("Error while calling xen-cmdline
> script")
>

Thanks for testing this, George. Can you attach a copy of the logs
from the point that you issued the pool-eject command, up to this
line? I need a little more context.

>
> My opinion about 'eject' on debian:
> 1) Clear running VM's
> 2) Unplug all VBD
> 3) Unplug all PIF's but management
> 4) Wipe /var/lib/xcp/state.db
> 5) Wipe /var/lib/xcp/local.db
> 6) Keep only management interface data in /var/xcp/network.db
> 7) restart all xcp services.
>
> During playing with bug lack of '-onsystemboot' flag for xcp I've done that
> operation many times, seems it working without specific problems.
>
> It even works fine without host reboot.

I'll see if I can track down exactly what's happening on pool-eject,
and cut it down to the minimum necessary. Thanks again,

Mike