Docs look better, but they also serve to highlight that the base config
should be more fleshed out. That's a lot of non-trivial steps to get to
a point where you can actually use your slapd install for something.
--
openldap sections in ubuntu server guide not updated for packages in karmic
I'm not as enraged as others here, but I agree with Yannick. If we had a
debconf based base configuration for cn=config, and removed it, then it
should be put back in. Clearly having it would be less problematic for
most users than not having it.
--
openldap sections in ubuntu server guide not
*** This bug is a duplicate of bug 463684 ***
https://bugs.launchpad.net/bugs/463684
Why is this marked as a duplicate of a documentation bug? There are
documentation issues here, to be sure, but this is also a useful
configuration missing by default bug, which isn't covered by #463684.
--
Here's an interesting addition to this problem:
In my cluster, one system is based on a core2duo CPU, while the other is
based on an i7 920 CPU. When the VM is originally started on the i7,
migration doesn't work. When it's originally started on the core2, it
does. From this, I'm guessing that
Ok, updated to the latest libvirt packages from PPA:dnjl/virtualization.
Now, the migrate, then suspend/resume suggestion works for me. Still
less than ideal, as it kills the whole live migration thing, but at
least it doesn't totally kill my VMs anymore.
--
VM is suspended after live migrate in
This was with a hardy/amd64 guest OS. I haven't tried any other guests,
because the bulk of our VMs are supposed to be LTS installs.
--
VM is suspended after live migrate in Karmic
https://bugs.launchpad.net/bugs/448674
You received this bug notification because you are a member of Ubuntu
Server
I'm seeing behaviour that looks like this on karmic/amd64, only a
suspend/resume doesn't fix the VM. It stays hard locked. I can connect
to it on the virtual serial console or via VNC, and it shows what was
there before the migration, but it never unlocks and starts working.
--
VM is suspended
Public bug reported:
This is a bug reported in Debian and Redhat, which I'm currently seeing
on fresh installs of Ubuntu/karmic. The details of my problem generally
match the Debian bug report, which I'll link here.
ProblemType: Bug
Architecture: amd64
Date: Fri Nov 27 15:12:25 2009
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36181383/Dependencies.txt
** Bug watch added: Debian Bug tracker #533436
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533436
** Also affects: drbd8 (Debian) via
/etc/lvm/lvm.conf filter suggestion from redhat bug works well,
actually. After filtering out the block device my drbd device is based
on, lvcreate works as expected.
--
Unable to use use LVM with DRBD block devices as PV
https://bugs.launchpad.net/bugs/489398
You received this bug notification
Hey Kai-Cheung,
Sorry I wasn't more explicit, but I *did* rebuild the required libraries
from Tim's repo for jaunty. It still doesn't build properly for me. ;)
I suspect that perhaps the build-deps on the packages aren't totally
accurate, since I'm building on a fresh jaunty install inside a VM,
I definitely agree about introducing into Karmic. That way there'll be
some wider usage and testing before the next LTS.
--
[needs-packaging] Fedora Directory Server for Ubuntu
https://bugs.launchpad.net/bugs/27463
You received this bug notification because you are a member of Ubuntu
Server
Tim:
Is it possible to get packages for jaunty into your repo? I'm getting
errors trying to rebuild the packages on jaunty/amd64. It freaks out and
generates a ton of errors trying to compile this:
/bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-DBUILD_NUM=\2009.161.2056\
Any update on when we'll see an updated package for this issue?
--
open-iscsi user-space does not match kernel module version
https://bugs.launchpad.net/bugs/289470
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-iscsi in ubuntu.
--
14 matches
Mail list logo
