George Shuklin
2012-Jun-25 03:01 UTC
[Pkg-xen-devel] Bug#678923: xcp-xapi: host-disable and host-reboot make host disable forever
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: <unknown> I've reboot host again, but again it stays 'disabled' no matter what I do (xcp restart, master restart and so on). ("this_host" is a slave in two hosts pool). -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xcp-xapi depends on: ii hwdata 0.233-1 ii libc6 2.13-33 ii libpam0g 1.1.3-7.1 ii libuuid1 2.20.1-5 ii libvhd0 2.0.90-1 ii libxen-4.1 4.1.2-6 ii libxenstore3.0 4.1.2-6 ii lsb-base 4.1+Debian7 ii pciutils 1:3.1.9-4 ii python 2.7.3~rc2-1 ii python-xenapi 1.3.2-6 ii stunnel4 [stunnel] 3:4.53-1 ii xcp-eliloader 0.1-4 ii xcp-fe 0.5.2-3+b1 ii xcp-networkd 1.3.2-6 ii xcp-squeezed 1.3.2-6 ii xcp-storage-managers 0.1.1-2 ii xcp-v6d 1.3.2-6 ii xcp-xe 1.3.2-6 ii xen-hypervisor-4.1-amd64 [xen-hypervisor-4.1] 4.1.2-6 ii xen-utils-4.1 4.1.2-6 ii zlib1g 1:1.2.7.dfsg-11 Versions of packages xcp-xapi recommends: ii cifs-utils 2:5.5-1 ii xcp-guest-templates 0.1-3 ii xcp-vncterm 0.1-2 xcp-xapi suggests no packages. -- no debconf information
Debian Bug Tracking System
2012-Jul-03 05:51 UTC
[Pkg-xen-devel] Bug#678923: marked as done (xcp-xapi: host-disable and host-reboot make host disable forever)
Your message dated Tue, 03 Jul 2012 09:48:45 +0400 with message-id <4FF287BD.2000308 at gmail.com> and subject line has caused the Debian Bug report #678923, regarding xcp-xapi: host-disable and host-reboot make host disable forever 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.) -- 678923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678923 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: George Shuklin <george.shuklin at gmail.com> Subject: xcp-xapi: host-disable and host-reboot make host disable forever Date: Mon, 25 Jun 2012 07:01:01 +0400 Size: 4081 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120703/71c8822c/attachment.mht> -------------- next part -------------- An embedded message was scrubbed... From: George Shuklin <george.shuklin at gmail.com> Subject: no subject Date: Tue, 03 Jul 2012 09:48:45 +0400 Size: 2416 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120703/71c8822c/attachment-0001.mht>
George Shuklin
2012-Jul-05 02:21 UTC
[Pkg-xen-devel] Bug#678923: Acknowledgement (xcp-xapi: host-disable and host-reboot make host disable forever)
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 uuidThe 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 /var/lib/xcp/local.db. 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 script?
Thomas Goirand
2012-Jul-07 06:08 UTC
[Pkg-xen-devel] Bug#678923: xcp-xapi: host-disable and host-reboot make host disable forever
Hi, This is fixed in the Git on Alioth. Tagging as pending an upload. Thomas
Debian Bug Tracking System
2012-Jul-08 17:36 UTC
[Pkg-xen-devel] Bug#678923: marked as done (xcp-xapi: host-disable and host-reboot make host disable forever)
Your message dated Sun, 08 Jul 2012 17:32:48 +0000 with message-id <E1SnvLk-0003fa-Tc at franck.debian.org> and subject line Bug#678923: fixed in xen-api 1.3.2-9 has caused the Debian Bug report #678923, regarding xcp-xapi: host-disable and host-reboot make host disable forever 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.) -- 678923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678923 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: George Shuklin <george.shuklin at gmail.com> Subject: xcp-xapi: host-disable and host-reboot make host disable forever Date: Mon, 25 Jun 2012 07:01:01 +0400 Size: 4081 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120708/3181d63c/attachment.mht> -------------- next part -------------- An embedded message was scrubbed... From: Thomas Goirand <zigo at debian.org> Subject: Bug#678923: fixed in xen-api 1.3.2-9 Date: Sun, 08 Jul 2012 17:32:48 +0000 Size: 6933 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120708/3181d63c/attachment-0001.mht>
Seemingly Similar Threads
- Bug#680102: xcp-xapi: xcp fails eject host from pool (no /etc/firstboot.d found)
- Bug#680588: xcp-xapi: startup race condition between xcp-xapi and xcp-networkd on slave
- Bug#677395: xcp-xapi: xe pif-configure-ip does not remove old ip from interface
- Bug#675055: xcp-xapi: xe-edit-bootloader does not compatible with new /dev/sm
- Bug#675050: xcp-xapi: /usr/lib/xcp/lib/bin/xe-edit-bootloader uses wrong path to the 'xe'