Displaying 20 results from an estimated 5000 matches similar to: "Bug#680511: xcp-xe: autocomplete for sr-probe type=nfs does not provide hints for device-config"
2012 Sep 17
3
Bug#687936: xcp-xe: 'xe console' command undocumented
Package: xcp-xe
Version: 1.3.2-11
Severity: minor
xe did not prove help in autocomplete for xe console command.
Steps to reproduce:
xe console[tab]
Output (help) does not contains xe console command.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores)
2012 Jul 06
1
Bug#680500: xcp-xe: Tab in autocomple of params for 'xe pif-list params=' erase some arguments
Package: xcp-xe
Version: 1.3.2-8
Severity: minor
When autocomplete for bash is activated following misbehavior happens:
xe pif-list params=device,m[Tab]
expected behavior:
autocomplete to xe pif-list params=device,management
actual behavior:
xe pif-list params=management
('device' removed)
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500,
2012 May 29
1
Bug#675052: xcp-xapi: xe vm-memory-target-set does not write target to xenstore
Package: xcp-xapi
Version: 1.3.2-6
Severity: important
Tags: upstream
xe vm-memory-target-set does not write new target to /local/domain/ID/memory/target. Balloon in guest domain is expecting this value to be changed to do selfballooning.
This breaks 'dynamic memory control' feature.
Steps to reproduce:
1) Setup any PV virtual machine with static-memory-min < static-memory-max
2)
2012 May 29
3
Bug#675055: xcp-xapi: xe-edit-bootloader does not compatible with new /dev/sm
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
2012 Jun 24
1
Bug#678723: xcp-xapi: vif-interfaces added to database as PIF's
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
2012 May 29
2
Bug#675050: xcp-xapi: /usr/lib/xcp/lib/bin/xe-edit-bootloader uses wrong path to the 'xe'
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
2013 Mar 05
1
Bug#702340: xe sr-create creates nested PV/VG
Package: xcp-xe
Version: 1.3.2-14
Severity: normal
I created an LV manually and ran the command:
xe sr-create type=ext name-label=myHostSr0 \
device-config:device=/dev/mapper/vg00-sr0
The SR was created, however, I found that it was created as a nested LV,
in other words, it appears xe did something like this:
pvcreate /dev/mapper/vg00-sr0
vgcreate sr_vg
lvcreate sr_vg sr0
2012 Jul 06
1
Bug#680499: xcp-xapi: Http_client.Http_request_rejected during upgrade
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: [
2012 Jun 13
2
Bug#677395: xcp-xapi: xe pif-configure-ip does not remove old ip from interface
Package: xcp-xapi
Version: 1.3.2-6
Severity: minor
Tags: upstream
If xe pif-configure-ip called twice with different IP, it did not remove old IP from interface (but didn't store both addresses in database).
(Checked for management interface)
Steps to reproduce:
xe pif-reconfigure-ip uuid=... ip=IP1 ....
xe pif-reconfigure-ip uuid=(same) ip=IP2 ...
'ip addr show' shows both
2012 Sep 11
1
Bug#687284: /usr/lib/xcp/bin/xe-reset-networking uses Fedora-specific paths
Package: xcp-xapi
Version: 1.3.2-11
xe-reset-networking uses Fedora/CentOS-specific paths like /etc/firstboot.d (perhaps /var/lib/xcp/firstboot.d instead? - this is used in other places) and /etc/sysconfig and possibly others. The script doesn't properly reset networking due to this.
Regards,
Ognyan Kulev
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
2012 Sep 27
1
Bug#688961: xcp-xapi: xe host-set-hostname-live fails (debian is not centos!)
Package: xcp-xapi
Version: 1.3.2-11
Severity: normal
xe host-set-hostname-live host-uuid=68878163-7c93-17af-7911-5a2726fefc66 host-name=xapi-xh3
The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem.
message: Subprocess exitted with unexpected code 2; stdout = [ ]; stderr = [ sed: can't read
2012 May 01
1
Bug#670988: xcp-xapi: /usr/lib/xcp/bin/xe-mount-iso-sr has wrong path for XE
Package: xcp-xapi
Version: 1.3-16
Severity: normal
Tags: patch
Dear Maintainer,
Path to "xe" program in /usr/lib/xcp/bin/xe-mount-iso-sr should be:
XE="/usr/bin/xe"
HTH,
David
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores)
2010 Aug 16
3
XCP: xe host-evacuate generates wrong error message
Good day.
XCP 0.5
xe host-evacuate uuid=f9458b0b-5e35-4ee0-adcf-c8945a37868c
You attempted an operation on a VM which requires a more recent version
of the PV drivers. Please upgrade your PV drivers.
vm: a84aaf23-8afe-2ccc-0299-83b9dfd08c35
But at really vm uuid with bad PV-drivers is
42e397c7-3d76-02c0-a1f9-c78d79cac6c6 and no uuid a84aaf23... present in
pool.
I think, it is an error in
2013 Dec 08
1
Bug#731718: after run: xe vm-import filename=... The VM could not be imported
Package: xcp-xe
Version: 1.3.2-15
after run: xe vm-import filename=debserv.ovf
i get messages:
The VM could not be imported.
msg: INTERNAL_ERROR: [ Failure("int_of_string") ]
In /var/log/xcp-xapi.log, i get the lines:
|5239 INET 127.0.0.1:80|VM import R:d700155bd1f0|import] Importing (as new VM)
|5239 INET 127.0.0.1:80|VM import R:d700155bd1f0|import] Reading XML
|5239 INET
2012 Jun 25
4
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:
2013 Oct 07
1
Bug#725676: resizing SR fails
Package: xcp-xapi
Version: 1.3.2-14
I've expanded the underlying volume for the SR
xe sr-scan doesn't seem to detect the new space
I've tried various things:
- using pvresize so that LVM detects the bigger partition
pvresize /dev/sda6
and the pvscan command now shows the correct space. running "xe
sr-scan uuid=$UUID" after this failed to detect the space
-
2011 Nov 21
0
Issue XCP 1.1: Shared LVM SR - unavailable host leaves VDI attached RW (xe vdi-introduce not available)
Dear list,
We observed the following issue in conjunction w/ XCP 1.1 which is a
_severe_ problem.
Our environment:
- Two XCP 1.1 hosts in the same resource pool
- Shared LVM based storage repository based on DRBD
- VMs running on both systems stored on the shared SR
If suddenly one host dies unexpectedly (e.g. hardware defect, power
issue) the metadata still assumes the VMs that were running on
2012 Jul 03
1
Bug#680102: xcp-xapi: xcp fails eject host from pool (no /etc/firstboot.d found)
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,
2012 Jul 12
2
Bug#681343: xcp-xapi: wait_for_xapi() function in init.d script does not work
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.
2012 Jul 07
1
Bug#680588: xcp-xapi: startup race condition between xcp-xapi and xcp-networkd on slave
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: