similar to: Processed: serious - must fix the docs before wheezy release

Processing commands for control at bugs.debian.org: > severity 702337 important Bug #702337 [xcp-xapi] xen-xapi / Open vSwitch not really working Severity set to 'important' from 'serious' > thanks! Unknown command or malformed arguments to command. > I don't think this bug should be RC. Even without openvswitch, XCP works Unknown command or malformed arguments to

Package: xcp-xapi Version: 1.3.2-14 Severity: important I chose the Open vSwitch (ovs) networking mode when I installed XCP # cat /etc/xcp/network.conf openvswitch Whenever I boot a VM, I notice that the vif interface is created (e.g. vif1.0) on dom0, and the vif is added to the ovs bridge (I can see it in the output of ovs-vsctl show) However, there is no connectivity, I can't ping the

There's no date defined yet, but Wheezy freeze will happen soon. How do we plan on concluding on this bug report? Recap for the actual bug I reported: If you want to start xapi, execute the following steps: 1) Start /etc/init.d/xend 2) Stop /etc/init.d/xend 3) Start /etc/init.d/xcp-xapi Step 1 is required because you need access to /proc/xen/ Step 2 is required because xapi cannot run

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}

Hi, I've been trying to fix several bugs in XCP, before the Debian 7 release. It's not bug free yet, but it's going into that direction. I would need some help to fix the remaining! 1/ The new 1.3.2-12 release The Debian release team has already accepted an unblock for this new version that I uploaded in Debian SID. Here's the debian/changelog: * Fixes bashism in

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

Processing commands for control at bugs.debian.org: > severity 695221 serious Bug #695221 [xcp-xapi] xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet netmask Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 695221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695221

Processing commands for control at bugs.debian.org: > reopen 678923 Bug #678923 {Done: George Shuklin <george.shuklin at gmail.com>} [xcp-xapi] xcp-xapi: host-disable and host-reboot make host disable forever Bug reopened Ignoring request to alter fixed versions of bug #678923 to the same values previously set > End of message, stopping processing here. Please contact me if you need

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

Processing commands for control at bugs.debian.org: > retitle 655301 xend shouldn't start if TOOLSTACK is not xm Bug #655301 [xcp-xapi] xcp-xapi fails to start Changed Bug title to 'xend shouldn't start if TOOLSTACK is not xm' from 'xcp-xapi fails to start' > reassign 655301 xen-utils-common Bug #655301 [xcp-xapi] xend shouldn't start if TOOLSTACK is not xm Bug

Processing commands for control at bugs.debian.org: > reassign #680528 xen-utils-common Bug #680528 [xcp-xapi] xcp-xapi: /etc/init.d/xendomains cause xapi to hand during boot Bug reassigned from package 'xcp-xapi' to 'xen-utils-common'. No longer marked as found in versions xen-api/1.3.2-8. Ignoring request to alter fixed versions of bug #680528 to the same values previously

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

Processing commands for control at bugs.debian.org: > retitle 674137 Please make bind port configurable Bug #674137 [xcp-xapi] xcp-xapi: default ports in xapi Changed Bug title to 'Please make bind port configurable' from 'xcp-xapi: default ports in xapi' > severity 674137 wishlist Bug #674137 [xcp-xapi] Please make bind port configurable Ignoring request to change severity

Processing commands for control at bugs.debian.org: > reassign 677614 xen-utils-common 4.1.2-6 Bug #677614 [xcp-xapi] xcp-xapi: someone should create /etc/default/xen Bug reassigned from package 'xcp-xapi' to 'xen-utils-common'. No longer marked as found in versions xen-api/1.3.2-6. No longer marked as fixed in versions 4.1.2-7. Bug #677614 [xen-utils-common] xcp-xapi: someone

Processing commands for control at bugs.debian.org: > tags #680588 pending Bug #680588 [xcp-xapi] xcp-xapi: startup race condition between xcp-xapi and xcp-networkd on slave Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 680588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680588 Debian Bug Tracking System Contact owner

Hi, I thought I'd query this here before opening a bug I installed XCP wheezy and imported a couple of my domU instances I chose to use Open vSwitch (ovs) networking mode I notice that each vif is created (e.g. vif1.0, vif2.0) when the domU boots. However, they are not bridged. As a hack, I just do brctl addif xenbr0 vif1.0 and then my domU is reachable. But I realise I should not

Processing commands for control at bugs.debian.org: > severity 702428 serious Bug #702428 [xcp-xapi] HVM fails to start with VIF / qemu-dm error Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 702428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702428 Debian Bug Tracking System Contact owner at

Processing commands for control at bugs.debian.org: > reassign 677614 xen-utils-common/4.1.2-6 Unknown command or malformed arguments to command. > fixed 677614 4.1.2-7 Bug #677614 [xcp-xapi] xcp-xapi: someone should create /etc/default/xen There is no source info for the package 'xcp-xapi' at version '4.1.2-7' with architecture '' Unable to make a source version

Package: xcp-xapi Version: 1.3-15 Severity: wishlist The current initscript has the possibility of slowing down the boot process by 50 seconds. If this is required, it probably should be backgrounded. # Wait for xapi to write its "init complete" cookie: after here it's safe to modify templates. wait_for_xapi() { MAX_RETRIES=50 RETRY=0 while [ ${RETRY} -lt ${MAX_RETRIES}

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