Displaying 20 results from an estimated 20000 matches similar to: "Processed: serious bug with networking"
2013 Feb 11
0
Processed: Back to important
Processing commands for control at bugs.debian.org:
> severity 695221 important
Bug #695221 [xcp-xapi] xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet netmask
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
695221:
2012 Dec 05
4
Bug#695221: xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet netmask
Package: xcp-xapi
Version: 1.3.2-13
Severity: critical
I get this bug when installing XCP and configuring the network portion of it.
When I issue the following command:
xe pif-reconfigure-ip uuid=$PIF_UUID mode=static IP=10.0.0.10 netmask=255.255.255.240 gateway=10.0.0.1 DNS=10.5.1.2,10.5.1.3
My network interface looks like this (Broken):
eth2 Link encap:Ethernet HWaddr 00:50:ec:24:c7:43
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 Aug 02
0
Bug#682216: Bug #682216 document about VLAN configuration on dom0
Hi,
After reading XenServer documents and debugging, I found the previous
configuration is correct, here is the one I've configured to work:
In XCP, as in XenServer, system's network configuration doesn't really
matter, it only make sense before XCP starts and handles the network
settings. So there is no need to configure VLAN on host machine, and
you only need a minimal one active
2013 Feb 10
1
Bug#695221: confirmed bug, serious
control: severity +2 serious
I would call this an RC bug (serious), but not critical
It would be critical if the user lost data from some unrelated
application, etc
It is serious because
a) it makes the package and the whole system unusable for all but one
very specific network configuration (users with a /24)
b) using good old `xm' style Xen I never experienced any issue like
this,
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 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 Jul 19
1
Bug#682122: xcp-xapi: README.Debian has a few misleading commands
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
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:
2012 Jul 19
1
Bug#682120: xen-api: missing --minimal in example command
Package: src:xen-api
Version: 1.3.2-9
Severity: wishlist
Hi,
In /usr/share/doc/xcp-xapi/README.Debian.gz, line 149:
149 PIF_UUID=`xe pif-list device=eth0`
150 xe pif-reconfigure-ip uuid=$PIF_UUID mode=static \
151 IP=1.2.3.4 netmask=255.255.255.0 gateway=1.2.3.1
The command for acquiring the pif-uuid is missing a --minimal
parameter, which makes it output the UUID only.
--
Regards,
2012 Jul 06
4
Bug#680528: xcp-xapi: /etc/init.d/xendomains cause xapi to hand during boot
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
2012 Jun 30
0
Processed: sets some xcp-api bug severities
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
2010 Apr 07
6
using ipoib with xcp
Hello,
I have been playing with the XCP for a while now, and must say I''m very
exited about the technology. I had no prior experience with Xen so it has
taken me a while to understand the concepts, but now I feel most important
issues are solved and I''ve purchased some hardware to build my (tiny) cloud
on.
The box is a Supermicro 1026TT-IBXF, so I have 2 x Ethernet and 1 x
2013 Mar 06
0
Bug#702337: possible documentation issue
It appears that this issue may be a result of documentation problems
When I was having this problem, I had xenbr0 declared in my
/etc/network/interfaces file. I have now stripped out everything in the
interfaces file except the loopback interface, rebooted, and now my
xcp+openvswitch system appears to be adding domUs to the bridge
automatically, so the problem is no longer there.
Specifically,
2012 Jul 20
2
Bug#682202: xcp-squeezed not started on boot
Package: xcp-squeezed
Version: 1.3.2-9
Severity: important
When trying to start a guest I get:
# xe vm-start name-label=squeeze-2
The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem.
message: Failure("The ballooning daemon is not running")
If I then manually run "/etc/init.d/xcp-squeezed
2012 Jul 03
4
Processed: your mail
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
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 May 23
4
Bug#674161: xcp-xapi: 'the device disappeared from xenstore' message during vbd-plug (vm-start)
Package: xcp-xapi
Version: 1.3.2-6
Severity: normal
Tags: upstream
vbd plug to PV domain cause following error:
The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem.
message: the device disappeared from xenstore (frontend (domid=4 | kind=vbd | devid=51760); backend (domid=0 | kind=vbd | devid=51760))
(same error
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
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)