** Changed in: samba (Ubuntu)
Assignee: (unassigned) = Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1416906
Title:
force user no longer works
To manage notifications
I have packaged the latest samba plus this debdiff into
https://launchpad.net/~chiluk/+archive/ubuntu/lp1416906
Please wait for the packages to build, and then test thems, \
Once you report back that these fix your issue. I'll get the fix
integrated into the archive packages.
Thanks.
--
You
I have packaged the latest samba plus this debdiff into
https://launchpad.net/~chiluk/+archive/ubuntu/lp1416906
Please wait for the packages to build, and then test thems, \
Once you report back that these fix your issue. I'll get the fix
integrated into the archive packages.
Thanks.
--
You
Here's the commit with magic we are looking for.
** Changed in: samba (Ubuntu)
Status: New = Incomplete
** Changed in: samba (Ubuntu)
Status: Incomplete = In Progress
** Patch added: lp1416906.debdiff
Here's the commit with magic we are looking for.
** Changed in: samba (Ubuntu)
Status: New = Incomplete
** Changed in: samba (Ubuntu)
Status: Incomplete = In Progress
** Patch added: lp1416906.debdiff
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404409
Title:
[regression] Intel 10Gb NIC Crashes
To manage notifications about this bug go to:
If we don't respin the installation guide for each point release of
trusty please ignore the series nomination.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368700
Title:
note for pxe boot with
** Changed in: libvirt (Ubuntu Trusty)
Status: Confirmed = Fix Released
** Changed in: libvirt (Ubuntu Utopic)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
** Changed in: libvirt (Ubuntu Trusty)
Status: Confirmed = Fix Released
** Changed in: libvirt (Ubuntu Utopic)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ceph (Ubuntu)
Assignee: Dave Chiluk (chiluk) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261501
Title:
ceph osds unbalanced
To manage notifications about
** Changed in: ceph (Ubuntu)
Assignee: Dave Chiluk (chiluk) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1261501
Title:
ceph osds unbalanced
To manage
** Tags removed: verification-needed
** Tags added: verification-done-trusty verification-needed-utopic
** Tags removed: verification-needed-utopic
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: verification-done-utopic
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403648
Title:
Apparmor denies qemu
** Changed in: libvirt (Ubuntu Trusty)
Assignee: (unassigned) = Dave Chiluk (chiluk)
** Changed in: libvirt (Ubuntu Utopic)
Assignee: (unassigned) = Dave Chiluk (chiluk)
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Dave Chiluk (chiluk)
** Changed in: ceph (Juju Charms
** Changed in: libvirt (Ubuntu Trusty)
Assignee: (unassigned) = Dave Chiluk (chiluk)
** Changed in: libvirt (Ubuntu Utopic)
Assignee: (unassigned) = Dave Chiluk (chiluk)
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Dave Chiluk (chiluk)
** Changed in: ceph (Juju Charms
This patch should also go into trusty so that it can be picked up for
14.04.2.
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/583216
Title:
inet_protocols can't
This patch should also go into trusty so that it can be picked up for
14.04.2.
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/583216
Title:
inet_protocols can't be preseeded
To
** Changed in: postfix (Ubuntu)
Milestone: None = ubuntu-14.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/583216
Title:
inet_protocols can't be preseeded
To manage notifications about
** Changed in: postfix (Ubuntu)
Milestone: None = ubuntu-14.04.2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/583216
Title:
inet_protocols can't be preseeded
To manage
** Description changed:
+ [Impact]
+ * Log files become overloaded with apparmor denials when
+
+ [Test Case]
+ * Launch a qemu instance using libvirt.
+ * See logged apparmor error in /var/log/syslog
+
+ [Regression Potential]
+ * Current defaults are to deny access to these files, but users
@Takenori
These messages can be worked around by editing
/etc/apparmor.d/abstractions/libvirt-qemu as such
__
--- libvirt-qemu.orig 2014-12-19 20:13:31.162926539 +
+++ libvirt-qemu2014-12-19 20:20:32.226276231 +
@@ -130,6
Public bug reported:
Apparmor denise libvirt access to a number of important directories.
syslog.4:Dec 12 17:18:08 nuc2 kernel: [54334.001494] type=1400
audit(1418404688.659:48): apparmor=DENIED operation=open
profile=libvirt-64557998-1e6b-43fb-bf6a-7dc9b9c7a660
Public bug reported:
Apparmor denise libvirt access to a number of important directories.
syslog.4:Dec 12 17:18:08 nuc2 kernel: [54334.001494] type=1400
audit(1418404688.659:48): apparmor=DENIED operation=open
profile=libvirt-64557998-1e6b-43fb-bf6a-7dc9b9c7a660
I just realized there's another bug opened that's similar to this
bug 1365261.
However, the resolution for the /tmp/ errors and the resolution for
/var/lib/charm/ceph errors may be different, so I'll leave this one
open.
** Summary changed:
- Apparmor denies libvirt access to a number of
xml for the created vm.
This applies to all vm's created via openstack through libvirt.
** Attachment added: xml
https://bugs.launchpad.net/charms/+source/ceph/+bug/1403648/+attachment/4283134/+files/xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Is there any way to get rid of the messages? Perhaps we should patch
qemu to not attempt to access /tmp or /var/tmp?
Basically these messages are now filling up logs on openstack compute
nodes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403648
Title:
Apparmor denies qemu access to a number of important directories.
To manage notifications about this bug go to:
Somehow the earlier xml upload was corrupted trying again.
** Attachment added: xml
https://bugs.launchpad.net/charms/+source/ceph/+bug/1403648/+attachment/4283152/+files/xml
** Attachment removed: xml
Launchpad fail... One more time.
** Attachment added: xml.txt
https://bugs.launchpad.net/charms/+source/ceph/+bug/1403648/+attachment/4283154/+files/xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Launchpad fail... One more time.
** Attachment added: xml.txt
https://bugs.launchpad.net/charms/+source/ceph/+bug/1403648/+attachment/4283155/+files/xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I accidentally opened a similar but slightly different bug to this one at
https://bugs.launchpad.net/charms/+source/ceph/+bug/1403648
These messages can be safely ignored, although we are pursuing a way to
clean them up.
--
You received this bug notification because you are a member of Ubuntu
There are numerous reports that this is still not resolved in the latest
packages available in trusty.
http://openvswitch.org/pipermail/discuss/2014-December/015931.html
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
There are numerous reports that this is still not resolved in the latest
packages available in trusty.
http://openvswitch.org/pipermail/discuss/2014-December/015931.html
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365261
Title:
Apparmor denies qemu access to /tmp directory
To manage notifications about this bug go to:
** Description changed:
- [Impact]
- When all the following exist
-- mounting a server using hostname.
-- the hostname resolves to both an ipv4 and ipv6 address
-- the nfs server only supports nfsv4
- Then.
- * The nfs client will not fall back fo nfsv4, and will be unable to
Thanks for doing that verification Tyler.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391662
Title:
mount.nfs does not
Got this update from Tyler through UA.
I have installed the package that Dave provided and it seems to resolve
the problem!
Tyler please +1 here as well.
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- If you attempt to mount a share from a server that is dual stack (i.e.
- has both an A and a record in DNS) and NFSv3-only, mount.nfs goes
- into an infinite loop of retrying an NFS-v4 mount:
+ [Impact]
+ When all the following exist
+- mounting a server using
** Changed in: nfs-utils (Ubuntu)
Assignee: (unassigned) = Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391662
Title:
mount.nfs does not downgrade NFS version when
I have built a test package with this commit for precise
http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=9da66f8898a6
I have placed it http://people.canonical.com/~chiluk/lp1391662/
Unfortunately my environments do not have ipv6 name resolution
adequately functioning to fully test
** Patch added: Proposed debdiff
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391662/+attachment/4260754/+files/lp1391662.debdiff
** Changed in: nfs-utils (Ubuntu)
Importance: Undecided = Medium
** Changed in: nfs-utils (Ubuntu)
Status: New = In Progress
--
You
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications about this bug go to:
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240088
Title:
add network (nm-applet) to login screen
To manage notifications about this bug go to:
** Also affects: nova-compute (Juju Charms Collection)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1265877
Title:
nova fails to launch
** Also affects: nova-compute (Juju Charms Collection)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265877
Title:
nova fails to launch i386 images
To
** Changed in: linux (Ubuntu Utopic)
Status: Confirmed = Won't Fix
** Changed in: linux (Ubuntu Trusty)
Status: New = Won't Fix
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The ubuntu kernel uses the same values as the upstream kernel in regards
to these values. They are tunable for exactly this kind of case.
I brought this case up with the Ubuntu Kernel team, and unfortunately
due to the fact that this could potentially be used in a memory-
exhaustion, denial of
@Carl Hetherington
Your patch is interesting. Please submit it to the mainline kernel, and
to stable if you feel it deserves to go into stable. Once it hits
stable it will then likely get picked up by the Ubuntu 3.13 kernel.
--
You received this bug notification because you are a member of
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New = Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: ua
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1370716
Title:
port 1 of bl460c Gen9 can not get IP
To manage notifications about this bug go to:
** Tags added: ua
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04] Bluetooth headsets are not working after last
couple of updates
To manage notifications about
1. Intel chipset raid is a type of software raid so it being detected as an md
device is expected.
2. Does the machine get to the grub menu?
3. How did you partition the Raid 1?
4. What did you select for the grub install device?
** Tags added: ua
--
You received this bug notification
*** This bug is a duplicate of bug 1354234 ***
https://bugs.launchpad.net/bugs/1354234
Thank you for your opening of this bug, but this issue has already been
resolved by 3.13.0-36 please see bug 1368245 for more information.
** This bug has been marked a duplicate of bug 1354234
14.04:
** Tags added: ua
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1329434
Title:
nested KVM fails on intel hardware - KVM: entry failed, hardware error
0x0
To manage notifications about this bug
** Changed in: compiz-core
Assignee: Kip Warner (kip) = (unassigned)
** Changed in: compiz
Assignee: Kip Warner (kip) = (unassigned)
** Changed in: compiz (Ubuntu)
Assignee: Kip Warner (kip) = (unassigned)
** Changed in: nvidia-graphics-drivers (Ubuntu)
Assignee: Kip Warner
** Changed in: pcsc-lite (Ubuntu)
Assignee: Kip Warner (kip) = Dariusz Gadomski (dgadomski)
** Changed in: pcsc-lite (Ubuntu)
Assignee: Dariusz Gadomski (dgadomski) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354234
Title:
14.04: PANIC with dcache shrink list corruption?
@matthew-l-dailey,
Could you put together a debdiff for this patch against the latest utopic
sources?
This looks to be a fairly good guide.
http://packaging.ubuntu.com/html/traditional-packaging.html
Also if you are feeling frisky you could also create a debdiff for the trusty
and precise
hopefully this is quite a bit more isolated than I originally
believed.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Dave Chiluk (chiluk)
** Changed in: linux-lts-trusty (Ubuntu)
Assignee: (unassigned
@matthew-l-dailey,
Could you put together a debdiff for this patch against the latest utopic
sources?
This looks to be a fairly good guide.
http://packaging.ubuntu.com/html/traditional-packaging.html
Also if you are feeling frisky you could also create a debdiff for the trusty
and precise
Public bug reported:
How to reproduce with linux-lts-trusty
1. Enable wake on lan in bios
2. Boot *(however you want to boot)
3. Check that device supports wakeonlan
ethtool eth0
# the Wake-on: setting should include g
4. shutdown -h now
5. wakeonlan -i ip address mac address
in my case
Looks like this is already resolved in mainline v3.17-rc2-utopic. I
will bisect how upstream resolved the issue
** Tags added: kernel-bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363361
v3.14.17-utopic - fails
v3.15-rc1-trusty - is fixed
Now for bed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363361
Title:
Machine does not wake up to wakeonlan magic packets after shutdown -h
** Changed in: linux (Ubuntu)
Assignee: Dave Chiluk (chiluk) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047566
Title:
Memory leaks when using NFS
To manage notifications
*** This bug is a duplicate of bug 1354234 ***
https://bugs.launchpad.net/bugs/1354234
** This bug has been marked a duplicate of bug 1354234
14.04: PANIC with dcache shrink list corruption? problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here's a soft lockup that is reportedly fixed by this patchset
BUG: soft lockup - CPU#1 stuck for 23s! [test.sh:1928]
Kernel panic - not syncing: softlockup: hung tasks
CPU: 1 PID: 1928 Comm: test.sh Tainted: G W 3.13.0-24-generic #47-Ubuntu
Hardware name: NEC Mercury CPU Module
** Tags added: ua
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354234
Title:
14.04: PANIC with dcache shrink list corruption? problem
To manage notifications about this bug go to:
Public bug reported:
BUG: soft lockup - CPU#1 stuck for 23s! [test.sh:1928]
Kernel panic - not syncing: softlockup: hung tasks
CPU: 1 PID: 1928 Comm: test.sh Tainted: GW3.13.0-24-generic
#47-Ubuntu
Hardware name: NEC Mercury CPU Module [NQ2250-902]/GC-MDC10-NJ, BIOS 5.6.0005
So upon further investigation, this issue appears to be more access
point/timing related than kernel specific. Once I connect to the access
point using an older kernel, any of the new kernels will also work.
Very odd. Not really sure how to proceed on this one.
--
You received this bug
://patchwork.ozlabs.org/patch/357291/
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Dave Chiluk (chiluk)
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Same issue here. This really should be a security concern. Any one of
us could have been typing our password directly into irc if it was in
focus behind the lock screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The trusty fix for this is still sitting in trusty-proposed. Can this
be released to updates?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1313209
Title:
Running byobu-ctrl-a
The trusty fix for this is still sitting in trusty-proposed. Can this
be released to updates?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313209
Title:
Running byobu-ctrl-a fails
To manage
** Tags added: ua
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302605
Title:
Calls to /libx32/ld-linux-x32.so.2 hang when using auditd
To manage notifications about this bug go to:
** Also affects: linux-lts-trusty (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-lts-trusty (Ubuntu Lucid)
Status: New = Invalid
** Changed in: linux-lts-trusty (Ubuntu Saucy)
Status: New = Invalid
** Changed in: linux-lts-trusty (Ubuntu Utopic)
@Tim - This was noticed at a meeting room that I don't go to very often.
I will do my best. It should be noted that arges who was running Utopic
was also seeing the same issue on his T420. (I'm not sure what specific
kernel version that was though).
--
You received this bug notification
Public bug reported:
3.13.0-29-generic works 3.13.0-30 results in the following errors
Jun 23 20:53:15 colt kernel: [5.862854] iwlwifi :03:00.0: L1 Disabled;
Enabling L0S
Jun 23 20:53:15 colt kernel: [5.869441] iwlwifi :03:00.0: Radio
type=0x2-0x1-0x0
Jun 23 20:53:15 colt
Public bug reported:
Kernel Bug affects 3.11-3.15 on machines using gso offload.
Stack trace
[ 871.025524] [ cut here ]
[ 871.030742] kernel BUG at /build/buildd/linux-3.13.0/net/core/skbuff.c:2903!
[ 871.038669] invalid opcode: [#1] SMP
[ 871.043318] Modules linked
** Description changed:
- Kernel Bug affects 3.11 - 3.13.0-30 on machines capable using gso
- offload.
+ Kernel Bug affects 3.11-3.15 on machines capable using gso offload.
Stack trace
[ 871.025524] [ cut here ]
[ 871.030742] kernel BUG at
I have sent an e-mail to the linux-stable mailing list requesting that
this patch be included in the stable trees.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331219
Title:
Kernel Bug at
@pkern, it is already in proposed for precise. Make sure you enable
-proposed from a mirror that has already synced with the main archives
*(i.e. mirroring usually happens nightly, so it may not be on your
mirror yet).
The lts-trusty kernels in precise are basically mirrors of the ubuntu-
@pkern, it is already in proposed for precise. Make sure you enable
-proposed from a mirror that has already synced with the main archives
*(i.e. mirroring usually happens nightly, so it may not be on your
mirror yet).
The lts-trusty kernels in precise are basically mirrors of the ubuntu-
I sent James Jones a message on Linked-in directing him to this bug,
hopefully that helps. The interwebs are a beautiful and often very
small place.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Anton the kernel SRU process is special and is done using a mailing list
Please see
https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat
and
https://wiki.ubuntu.com/KernelTeam/KernelUpdates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Assuming the schedule holds, and there aren't any unforseen CVE's or
test regressions, we should see it in about 4 weeks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1300739
Assuming the schedule holds, and there aren't any unforseen CVE's or
test regressions, we should see it in about 4 weeks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300739
Title:
keepalived
pkern-k that comment is from a bot that monitors all bugs open against
linux.
This was modified by c28f49fd37b during the ubuntu-raring kernel
timeframe, due to a configuration review.
We are looking into this.
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1300739
Title:
keepalived doesn't load any ipv6
** Description changed:
- I've upgraded from 12.04 to 14.04 and the keepalived no longer loads any
- IPv6 virtual servers.
+ SRU Justification:
+ Impact: Keepalived is no longer able to load any IPv6 virtual servers for
load balancing purposes.
+ Fix: Re-enable CONFIG_IP_VS_IPV6=y
+ Testcase:
Change has been submitted to both Trusty, and Utopic trees.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1300739
Title:
keepalived doesn't load any ipv6 virtual servers
To
pkern-k that comment is from a bot that monitors all bugs open against
linux.
This was modified by c28f49fd37b during the ubuntu-raring kernel
timeframe, due to a configuration review.
We are looking into this.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300739
Title:
keepalived doesn't load any ipv6 virtual servers
** Description changed:
- I've upgraded from 12.04 to 14.04 and the keepalived no longer loads any
- IPv6 virtual servers.
+ SRU Justification:
+ Impact: Keepalived is no longer able to load any IPv6 virtual servers for
load balancing purposes.
+ Fix: Re-enable CONFIG_IP_VS_IPV6=y
+ Testcase:
Change has been submitted to both Trusty, and Utopic trees.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300739
Title:
keepalived doesn't load any ipv6 virtual servers
To manage notifications
@david-partain, this has been fixed in trusty, what you are experiencing
is a new bug altogether.
I was able to verify that forcing the bootdev in the preseed file does
indeed force grub to install onto /dev/sdb when using the non-netboot
install.
However, when using the same preseed file with
@david-partain I was able to work around the error that I was
experiencing by ensuring that there was a valid partition table on
/dev/sdb.
That makes sense as well. There's really no way to install bootloader to
the mbr of /dev/sdb if the mbr doesn't exist because there is no
partition table.
--
** Patch added: lp1301692.debdiff
https://bugs.launchpad.net/ubuntu/+source/amtterm/+bug/1301692/+attachment/4064148/+files/lp1301692.debdiff
** Patch removed: lp1301692.debdiff
https://bugs.launchpad.net/ubuntu/+source/amtterm/+bug/1301692/+attachment/4061940/+files/lp1301692.debdiff
--
Public bug reported:
amtterm disconnects with the following error.
amtterm: RUN_SOL - ERROR (failure)
amtterm: ERROR: redir_data: unknown r-buf 0x29
This is the result of amtterm not being able to handle the 0x29 control
character.
** Affects: amtterm (Ubuntu)
Importance: Undecided
Here's a debdiff with the solution, backported from upstream.. There's
really not much more to be said.
** Changed in: amtterm (Ubuntu)
Assignee: (unassigned) = Dave Chiluk (chiluk)
** Changed in: amtterm (Ubuntu)
Status: New = In Progress
** Patch added: lp1301692.debdiff
https
So I got a report that this change has regressed console memtest86+. I
have verified that precise package in my ppa does indeed cause the
regression on the serial console menuentry. I'm installing trusty on my
testbed that has a serial port now, to verify there.
Also as an aside, I tested
601 - 700 of 1003 matches
Mail list logo
