uid/username is listed in nss_initgroups_ignoreusers in the
/etc/ldap.conf file.
What happened instead:
It seems that a connection is made anyways.
Thank you,
Deric Sullivan
** Affects: libnss-ldap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because y
Actually, the original post without the "auto bond0" is from mar_rio.
I'm the second person reporting the bug. I assumed that you didn't put
"auto bond0" because we've been quoting the README as authoritative and
it doesn't have the auto for the bond. To reproduce the original bug I
simplified my
Regarding comment #9:
Maybe there is some type of race condition that could cause the bug but I have
many servers that had never shown this bug. And regardless of any possible
race condition, the SRU guarantees that the bug will appear.
Regarding comment #8 and #9:
I tried the config as sugges
I've updated bug #482419 to indicate that its fix has caused this bug.
Deric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/823366
Title:
bond_primary is ignored in /etc/network/interfaces
To manag
The patch for this bug breaks the use of bond_primary in
/etc/network/interfaces. See Bug #823366.
The following piece of code from the "setup_master()" function in
/etc/network/if-pre-up.d/ifenslave will only setup a primary if the
primary is listed as a slave (which will not be the case with th
I would lke to correct my previous comment.
I should have said:
I do not see this bug in the previous lucid-updates (1.1.0-14ubuntu2.1) but I
do see it in the current lucid-updates (1.1.0-14ubuntu2.2).
Thanks,
Deric
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I do not see this bug in lucid but I do see it in lucid-updates.
Deric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/823366
Title:
bond_primary is ignored in /etc/network/interfaces
To manage noti
Martin, thanks for the clarification on how/when the fixed package moves from
-proposed to -updates.
But is there anything else needed? I waited 10 days to be safe, and still the
package is not in -updates. It's also still listed on the "Pending Ubuntu
stable release updates" web page.
Thanks
Thanks again.
Deric
On 05/06/11 15:52, Serge Hallyn wrote:
> The package will be moved to lucid-updates 7 days after this bug
> was marked verification-done.
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Hi,
I'm trying to figure out if there is anything else that I'm supposed to
do to get this fix into lucid-updates.
When I look at the web page for "Pending Ubuntu stable release updates"
(at "http://people.canonical.com/~ubuntu-archive/pending-sru.html";) I
see, in the lucid section, that qemu
Please note that I tried this on lucid only (and the bug was fixed). I
don't have access to any maverick systems.
Thanks,
Deric
On 05/03/11 17:30, Deric Sullivan wrote:
> I installed the lucid proposed qemu-kvm package and the bug is fixed.
>
> Thanks,
> Deric
>
> On
I installed the lucid proposed qemu-kvm package and the bug is fixed.
Thanks,
Deric
On 05/03/11 05:40, Martin Pitt wrote:
> Accepted qemu-kvm into lucid-proposed, the package will build now and be
> available in a few hours. Please test and give feedback here. See
> https://wiki.ubuntu.com/Testin
I installed the lucid proposed qemu-kvm package and the bug is fixed.
Thanks,
Deric
On 05/03/11 05:42, Martin Pitt wrote:
> Accepted qemu-kvm into maverick-proposed, the package will build now and
> be available in a few hours. Please test and give feedback here. See
> https://wiki.ubuntu.com/Tes
Great. Thanks.
Deric
On 04/30/11 15:16, Clint Byrum wrote:
> No it was not denied. I've gone ahead and accepted the bug for
> lucid/maverick SRU.
>
> ** Also affects: qemu-kvm (Ubuntu Lucid)
> Importance: Undecided
> Status: New
>
> ** Also affects: qemu-kvm (Ubuntu Maverick)
> I
Hi Serge,
Was the SRU for lucid to fix the "once" bug in qemu-kvm denied?
I've seen an update since you requested the SRU but it doesn't seem to
include the fix for the "once" bug.
Thanks,
Deric
On 02/17/11 20:41, Serge Hallyn wrote:
> Quoting Deric
Thanks, that fixed the problem. Will that fix make it into "lucid-
updates"?
Deric
On 02/17/11 18:40, Deric Sullivan wrote:
> Hi Serge,
>
> Thanks for looking into this.
>
> I am using amd64 so I'll try out the fix.
> Using "once" did not
Hi Serge,
Thanks for looking into this.
I am using amd64 so I'll try out the fix.
Using "once" did not work for me even if there wasn't a valid OS on
the hard drive.
I'm OK with an importance of "low", I was using the workaround of
simply stopping the qemu-kvm after the firs
Public bug reported:
Binary package hint: qemu-kvm
Package: qemu-kvm
The "once" parameter does not seem to work with the "-boot" option.
To reproduce:
create an image file to be used as a hard disk:
qemu-img create test-img 1G
Starting a VM guest using "once" + "order" ignores the "once":
/usr
18 matches
Mail list logo
