similar to: Processed: pending upload

Package: xcp-xapi Version: 1.3.2-8 Severity: important Tags: patch Found race condition (specific only to slave hosts): xcp-xapi can start earlier than xcp-networkd due lack of dependency in init.d script. Syptoms: After reboot slave's xcp does not work: xe (anything): The host failed to acquire an IP address on its management interface and therefore cannot contact the master. log:

Accepted: libxenapi-ocaml-dev_1.3.2-9_amd64.deb to main/x/xen-api/libxenapi-ocaml-dev_1.3.2-9_amd64.deb python-xenapi_1.3.2-9_all.deb to main/x/xen-api/python-xenapi_1.3.2-9_all.deb xcp-networkd_1.3.2-9_amd64.deb to main/x/xen-api/xcp-networkd_1.3.2-9_amd64.deb xcp-squeezed_1.3.2-9_amd64.deb to main/x/xen-api/xcp-squeezed_1.3.2-9_amd64.deb xcp-v6d_1.3.2-9_amd64.deb to

Package: xcp-xapi Version: 1.3.2-6 Severity: important Looks like on Wheezy, /etc/default/xen is not created by xen-utils-common. Since xcp-xapi depends on its existence and further declaration of the toolstack in it, it should take extra care to ensure that it is present. root at debian:~# aptitude install xcp-xapi The following NEW packages will be installed: blktap-dkms{a} blktap-utils{a}

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sat, 03 Nov 2012 19:12:36 +0000 Source: xen-api Binary: xcp-xapi python-xenapi xcp-squeezed xcp-v6d libxenapi-ocaml-dev xcp-xapi-debug xcp-xe xcp-networkd Architecture: source amd64 all Version: 1.3.2-13 Distribution: unstable Urgency: low Maintainer: Pkg Xen <pkg-xen-devel at lists.alioth.debian.org> Changed-By:

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Thu, 27 Dec 2012 13:05:06 +0000 Source: xen-api Binary: xcp-xapi python-xenapi xcp-squeezed xcp-v6d libxenapi-ocaml-dev xcp-xapi-debug xcp-xe xcp-networkd Architecture: source amd64 all Version: 1.3.2-14 Distribution: unstable Urgency: low Maintainer: Pkg Xen <pkg-xen-devel at lists.alioth.debian.org> Changed-By:

libxenapi-ocaml-dev_1.3.2-2_amd64.deb to main/x/xen-api/libxenapi-ocaml-dev_1.3.2-2_amd64.deb python-xenapi_1.3.2-2_all.deb to main/x/xen-api/python-xenapi_1.3.2-2_all.deb (new) xcp-networkd_1.3.2-2_amd64.deb extra admin daemon to manage network configuration for xcp-xapi The Xen Cloud Platform (XCP) is an open source enterprise-ready server virtualization and cloud computing platform, with

Package: xcp-xapi Version: 1.3.2-8 Severity: minor During upgrade from 1.3.2-7 to 1.3.2-8 got follwing message on slave host (upgrade was simulatanious on slave and master): ... Setting up xcp-xapi (1.3.2-8) ... The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: INTERNAL_ERROR: [

Dear Debian maintainer, On Thursday, March 15, 2012, I sent you a notification about the beginning of a review action on debconf templates for xen-api. Then, I sent you a bug report with rewritten templates and announcing the beginning of the second phase of this action: call for translation updates. Translators have been working hard and here is now the result of their efforts. Please

Package: xcp-xapi Version: 1.3.2-7 Severity: normal xcp-xapi fails to eject host from pool with following error: xe pool-eject host-uuid=a6806a39-442d-f17d-b7a0-59161d18f56f 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,

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream /usr/lib/xcp/bin/xe-edit-bootloader failing with following message: /usr/lib/xcp/bin/xe-edit-bootloader -u 19f66083-e776-70d1-1808-3712688ad138 Creating dom0 VBD: 0fdb952e-92ff-4b53-dd49-8d54b2268787 Plugging VBD: Waiting for /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/963afb9a-9ceb-410f-8554-8be9fb70e7e0: . done

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Function wait_for_xapi in /etc/init.d/xcp-xapi does not work as intented. Symptoms: (on slave) /etc/init.d/xcp-xapi restart [....] Restarting The XenAPI server: xapiThe host toolstack is still initialising. Please wait. Cause: Line 'xe pif-scan host-uuid=${INSTALLATION_UUID}' called before xapi is fully synced with master.

Package: xcp-xapi Version: 1.3.2-6 Severity: important I done normal reboot: xe host-disable host=this_host xe host-reboot host=this_host After reboot host stays in 'disable' state and when I've tried to make it enable I got: xe host-enable uuid=ab523ee3-0546-5400-e2db-32f340292fff The specified host is disabled and cannot be re-enabled until after it has rebooted. host:

Package: xcp-xapi Version: 1.3.2-6 Severity: important Configuration: Two xcp-xapi hosts (default sid/xcp-xapi installation) in single pool. Network backend is bridge. After migration of 'idle' (doning nothing) virtual machine it stops to reply to ping for long time. AFAIK that caused by mac-learning table on upper level (hardware) switch, which route all frames to wrong port

Package: xcp-networkd Version: 1.3.2-11 Severity: normal Given that openvswitch is one of the networking modes, it should be in the Recommends: than being in the Depends: -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Hi guys, Just a couple of things I noticed running through /usr/share/doc/xcp-xapi/README.Debian.gz as referenced by http://wiki.debian.org/XCP In "4/ Configuring Xen and XCP": sed -i "s/TOOLSTACK=/TOOLSTACK=xapi/" /etc/default/xen should be sed -i "s/TOOLSTACK=.*/TOOLSTACK=xapi/" /etc/default/xen Otherwise

Processing commands for control at bugs.debian.org: > severity 675052 normal Bug #675052 [xcp-xapi] xcp-xapi: xe vm-memory-target-set does not write target to xenstore Severity set to 'normal' from 'important' > severity 678923 normal Bug #678923 [xcp-xapi] xcp-xapi: host-disable and host-reboot make host disable forever Severity set to 'normal' from

Hi I install the xcp from the http://wiki.xen.org/wiki/XAPI_on_Ubuntu. But I got this error while configuring xcp-xapi: xcp-networkd (1.3.2-1ubuntu1~oneiric1) wird eingerichtet ... Starting the XCP networking daemon: .............................. * failed to start xcp-networkd. invoke-rc.d: initscript xcp-networkd, action "start" failed. when I comment the

Package: xcp-xapi Version: 1.3.2-8 Severity: important During startup /etc/init.d/xendomains script is called. That script is installed with xen-utils-common witch xcp-xapi is depends on. That script calls /usr/sbin/xen as xen list &> /dev/null This 'xen' seems to call xapi: xen list ^Z [1]+ Stopped xen list root at lab-xh3:~# ps f PID TTY STAT TIME

Package: xcp-xapi Version: 1.3.2-6 Severity: normal After some time of rebooting and toolstack restart found very funny output in 'xe pif-lis': xe pif-list params=currently-attached,device device ( RO) : vif2.0 currently-attached ( RO): false device ( RO) : vif211.0 currently-attached ( RO): false device ( RO) : eth1

Package: xcp-xapi Version: 1.3.2-6 Severity: minor Tags: upstream Builin utility for lowlevel vm boot repairment xe-edit-bootloader contains wrong path to xe. IS: XE="/usr/lib/xcp/bin/xe" MUST BE: XE="/usr/bin/xe" -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux