Ritesh Raj Sarraf
2012-May-23 09:25 UTC
[Pkg-xen-devel] Bug#674132: xcp-xapi: backend check error
Package: xcp-xapi Severity: important The README doc mentions: 4/ Configuring Xen and XCP -------------------------- 4.1/ Switch using xl instead of xm and xend to control Xen As of writing, you should do that: sed -i "s/TOOLSTACK=/TOOLSTACK=xl/" /etc/default/xen Where as the init script checks for: # Exit cleanly if TOOLSTACK != xapi if [ "${TOOLSTACK}" != "xapi" ]; then log_failure_msg "Xen toolstack is not set to xapi! Exiting." exit 0 fi Please fix this to one. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (100, 'experimental'), (1, 'quantal') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Mike McClurg
2012-May-23 10:03 UTC
[Pkg-xen-devel] Bug#674132: Bug#674132: xcp-xapi: backend check error
On Wed, May 23, 2012 at 10:25 AM, Ritesh Raj Sarraf <rrs at debian.org> wrote:> Package: xcp-xapi > Severity: important > > The README doc mentions: > > 4/ Configuring Xen and XCP > -------------------------- > 4.1/ Switch using xl instead of xm and xend to control Xen > As of writing, you should do that: > sed -i "s/TOOLSTACK=/TOOLSTACK=xl/" /etc/default/xen > > > Where as the init script checks for: > > # Exit cleanly if TOOLSTACK != xapi > if [ "${TOOLSTACK}" != "xapi" ]; then > ? ? ? ?log_failure_msg "Xen toolstack is not set to xapi! Exiting." > ? ? ? ?exit 0 > fi > > > Please fix this to one.Hi Ritesh, Should this really be an error? It's likely that for Xen 4.1, someone might have three toolstacks installed at the same time: xm, xl, and xapi. It seems that they should have the option to switch between the three without causing an error in the init scripts of the other two. In this case, do we really want to return an error here? Mike
Debian Bug Tracking System
2012-Jun-29 19:54 UTC
[Pkg-xen-devel] Bug#674132: marked as done (xcp-xapi: backend check error)
Your message dated Fri, 29 Jun 2012 19:52:39 +0000 with message-id <E1SkhF9-0004A4-EE at franck.debian.org> and subject line Bug#674132: fixed in xen-api 1.3.2-7 has caused the Debian Bug report #674132, regarding xcp-xapi: backend check error to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 674132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674132 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Ritesh Raj Sarraf <rrs at debian.org> Subject: xcp-xapi: backend check error Date: Wed, 23 May 2012 14:55:00 +0530 Size: 3528 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120629/e2898927/attachment-0002.mht> -------------- next part -------------- An embedded message was scrubbed... From: Thomas Goirand <zigo at debian.org> Subject: Bug#674132: fixed in xen-api 1.3.2-7 Date: Fri, 29 Jun 2012 19:52:39 +0000 Size: 7758 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120629/e2898927/attachment-0003.mht>
Seemingly Similar Threads
- Bug#655303: xcp-xapi: document network configuration in README.Debian
- Bug#655301: xcp-xapi fails to start
- Bug#686778: xcp-xapi: what user should xapi run as
- Bug#655302: xcp-xapi: init script will slow down boot process
- Bug#674137: xcp-xapi: default ports in xapi