Blueprint changed by dann frazier:
Work items changed:
Work items:
[louis-bouchard] - kdump-tools needs to be MIR / file a bug: DONE
[stefan-bader-canonical] - discuss linuxcrashdump changes on ubuntu-devel /
ubuntu-kernel: DONE
[stefan-bader-canonical] - linuxcrashdump changed
Blueprint changed by dann frazier:
Whiteboard changed:
User Stories:
Risks:
Test Plans:
Release Note:
--
The kdump mechanism from the kdump-tool package is more flexible than
its kexec-tool equivalent. It allows for multiple dumps to be collected
Public bug reported:
maas-0.1+bzr1269+dfsg-0ubuntu1, in /etc/maas/commissioning-user-data:
if [ ! -z power_settings ]; then
signal --power-type=ipmi --power-parameters=${power_settings} WORKING
finished [maas-ipmi-autodetect]
fi
Notice the missing $. I'm not sure if this causes any
Public bug reported:
For reasons described in LP: #1076028, shouldn't MAAS also conflict with
the tftpd package?
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
(and atftpd, for that matter)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1172520
Title:
should conflict w/ tftpd
To manage notifications about this bug go to:
Public bug reported:
This is necessary to pass the PCI/PCI Express Compliance Test required
by SVVP.
** Affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Patch added: Upstream fix
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/857746/+attachment/2449578/+files/e1000-Dont-set-the-Capabilities-List-bit.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
Here's a backport for lucid. I've tested that this correctly disables
the capabilities bit on a fresh lucid install.
** Patch added: lucid backport
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/857746/+attachment/2469608/+files/e1000-Dont-set-the-Capabilities-List-bit.patch
--
You
** Patch added: lspci output verifying fix for lucid
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/857746/+attachment/2469727/+files/lspci_-H1_-vvv.lucid.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
fyi, it looks like this could occur if a misbehaving bmc's status
register contained 0xff. That's another reason to check to see if the
older kernel works. If the previously working kernel also shows this
problem, I'd suggest removing power from the system to see if you can
reset the BMC.
--
You
** Summary changed:
- UI URL gives HTTP error 200 after CD install
+ UI URL displays 200 Error page after CD install
** Description changed:
I installed a MAAS server into a VM w/ the beta2 quantal cd:
- ubuntu-12.10-beta2-server-amd64.iso
+ ubuntu-12.10-beta2-server-amd64.iso
I did
Public bug reported:
I installed a MAAS server into a VM w/ the beta2 quantal cd:
ubuntu-12.10-beta2-server-amd64.iso
I did pass console=ttyS0, and I am in an environment w/ no NTP server,
but other than that a very vanilla install.
After install, the MAAS interface displayed the following
** Attachment added: apport maas-region-controller
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1067558/+attachment/3400902/+files/apport.maas-region-controller.1rcu6q.apport
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I noticed apport doesn't grab /var/log/celery-*, so I'm attaching a
tarball of all of /var/log/maas
** Attachment added: tarball of /var/log/maas
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1067558/+attachment/3400903/+files/var_log_maas.tgz
--
You received this bug notification
** Description changed:
I installed a MAAS server into a VM w/ the beta2 quantal cd:
- ubuntu-12.10-beta2-server-amd64.iso
+ ubuntu-12.10-beta2-server-amd64.iso
I did pass console=ttyS0, and I am in an environment w/ no NTP server,
but other than that a very vanilla install.
Public bug reported:
I am using MAAS in a network w/ a preexisting DNS/DHCP infrastructure. I
would like for my MAAS nodes to use the CNAME for the IP they are
assigned as their hostname. This seems to work - but only for the first
enlisted node. All following nodes get configured with the
** Attachment added: screenshot
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1067834/+attachment/3401788/+files/inconsistent-names.png
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Summary changed:
- inconsistent use of CNAME for hostname
+ inconsistent use of reverse DNS for hostname
** Description changed:
I am using MAAS in a network w/ a preexisting DNS/DHCP infrastructure. I
- would like for my MAAS nodes to use the CNAME for the IP they are
- assigned as their
I have a quantal/maas system that was displaying this message. I
upgraded to the version in -proposed (0.1+bzr1269+dfsg-0ubuntu1) and
waited 5 minutes. Unfortunately, the issue persists.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
I'm running juju 0.6-1ubuntu1 on a quantal/maas cloud of highbank/maas
nodes. I have a demo loop that I run to deploy hadoop, wait, add a few
nodes, wait add a few more nodes, then tear things down to just the
bootstrap node restart. I'm finding that this will very quickly
** Attachment added: output of netstat -pan at time of hang
https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1070519/+attachment/3410750/+files/netstat-pan.out
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
Just a note about severity - from what I can tell, this looks like a
time bomb that should've broken every existing precise/MAAS once the
weekly cronjob detected quantal's release.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas
I rebuilt this configuration on a less-restrictive network (identical
DNS/DHCP config, but w/o a firewall), and I was unable to reproduce the
problem. I did observe errors from the DNS server in the problematic
config - they were ipv6 issues. These issues did not correlate w/
failures to use PTR
Note that the zookeeper process appears to be spinning, not just hung.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1070519
Title:
zookeeper: WARN
Public bug reported:
Binary package hint: qemu-kvm
qemu-kvm includes symlinks to files in the vgabios package, but only
newer vgabios packages provide those files. The dependency that natty
oneiric's qemu-kvm has on vgabios probably needs to be versioned to = 0
.6c-2ubuntu2 to work well w/
I don't have a strong opinion either way (I've got it resolved where I
needed it to be), but the only justification that comes to mind for me
is a partial upgrade scenario. Whether or not that's an SRU qualifier,
I've no idea.
--
You received this bug notification because you are a member of
I can easily reproduce this problem w/ natty's multipath-tools and can
verify that the above fix works for me. I should be able to test an SRU
if desired.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
Public bug reported:
I obtained a coredump from a system where natty's multipathd had crashed
and received the following backtrace:
0 0x7f802925da75 in *__GI_raise (sig=value optimized out)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x7f80292615c0 in *__GI_abort () at
** Description changed:
- I obtained a coredump from a system where multipathd had crashed and
- received the following backtrace:
+ I obtained a coredump from a system where natty's multipathd had crashed
+ and received the following backtrace:
0 0x7f802925da75 in *__GI_raise (sig=value
Public bug reported:
The 1.4.14-0ubuntu3 upload updated config.{guess,sub} to support arm64.
Unfortunately, the way the patching system works, configure is ran with
no patches applied.
** Affects: memcached (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
** Bug watch added: Debian Bug tracker #721203
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721203
** Also affects: memcached (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721203
Importance: Unknown
Status: Unknown
--
You received this bug notification
Well, and -exynos5. See LP: 1240570.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1250390
Title:
No published Saucy armhf ephemeral images
To manage notifications about this bug go
On Tue, Dec 3, 2013 at 12:35 PM, Brian Rzycki b.rzy...@samsung.com wrote:
Robie: Yes, changing NTPDATE_USE_NTP_CONF=no makes everything work, at
least when I change it after the node is deployed. I am not aware of how
to try this with a preeseed late_command. Do you have instructions for
me to
Public bug reported:
juju-core is currently unavailable for arm64, this bug is intended to
track that progress.
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Affects: libv8 (Ubuntu)
Importance: Undecided
Status: New
** Affects: mongodb (Ubuntu)
juju-core relies on mongodb, which is also not available for arm64.
mongodb has a build-dependency on libv8, which requires porting to
arm64.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
juju-core 1.17.0-0ubuntu3 timed out building, but it looks like a kernel
issue. I reproduced this hang on both a 3.8 and a 3.12 kernel. However,
I tested w/ a 3.13 (hand rolled w/ xgene support), and juju-core built
fine.
--
You received this bug notification because you are a member of Ubuntu
juju-core should build on the buildds if we configure them with:
echo never | sudo tee /sys/kernel/mm/transparent_hugepages/enabled
(tested w/ 3.8 and 3.13 kernels)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in
Public bug reported:
dannf@trusty:~$ dpkg -l juju
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
Here's what seems to be a straightforward fix for this bug - after
applying, I get further:
dannf@trusty:~$ juju add-machine ssh:arm64dannf -v
verbose is deprecated with the current meaning, use show-log
2014-02-06 06:12:54 INFO juju api.go:231 connecting to API addresses:
On Fri, Feb 7, 2014 at 8:55 AM, John A Meinel j...@arbash-meinel.com wrote:
I don't have direct ways to test the patch, but it seems sane to me. Is
there something we can get into some form of testing to make sure that
we don't break this in the future? (CI testing for aarch64?)
I setup sinzui
This is the only other obvious place that grep says needs arch-
enablement.
** Patch added: patch for release-public-tools script
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1276909/+attachment/3972091/+files/pub-tools-arm64.patch
--
You received this bug notification because
On Fri, Feb 7, 2014 at 10:26 AM, John A Meinel j...@arbash-meinel.com wrote:
offhand, I would think we'd want to use the term arm64 for this (to
match arm), but I don't have a strong stake in what we call it.
I'd prefer arm64 as well (easier to type, 1:1 mapping for dpkg arch).
It apparently
On Fri, Feb 7, 2014 at 11:40 AM, Dave Cheney 1276...@bugs.launchpad.net wrote:
On Fri, Feb 7, 2014 at 7:37 PM, Antonio Rosales
1276...@bugs.launchpad.netwrote:
After discussion John and Dan the mapping for arm and ppc should look
like:
aarch64 should map to arm64
This one should be the
** Patch added: patch extracted from upstream
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/674645/+attachment/1731498/+files/dnsmasq-doublefree.patch
--
occasional crashes: glibc detected double free or corruption
https://bugs.launchpad.net/bugs/674645
You received this bug
Here's a debdiff against natty.
** Patch added: multipath-tools-fix-shutdown-segv.patch
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/488285/+attachment/181/+files/multipath-tools-fix-shutdown-segv.patch
--
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: multipath-tools
I received a coredump from a customer (running a lucid-based system).
Analyzing the core from multipathd shows that we are crashing in
waiter.c::free_waiter().
void free_waiter (void *data)
{
struct event_thread *wp = (struct
On Wed, Feb 09, 2011 at 09:37:17PM -, Serge Hallyn wrote:
Thanks for the patch, Dann. I would ask you to hit 'propose for merge'
from your lp tree, but I think it would be nice to have DEP-3 tags in
the patch to help out future maintainers. So I'll add those to my own
version and propose
Public bug reported:
[...]
checking for msgmerge... /usr/bin/msgmerge
checking build system type... Invalid configuration `aarch64-linux-gnu':
machine `aarch64' not recognized
configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed
make: [build] Error 1 (ignored)
(cd yp-tools-2.9
Public bug reported:
All binary packages produced by the numactl source package are
restricted to a set of architectures that does not include arm64. I've
verified that, if enabled, these binaries do build just fine on arm64.
** Affects: numactl (Ubuntu)
Importance: Undecided
** Bug watch added: Debian Bug tracker #739725
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739725
** Also affects: numactl (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739725
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
ubuntu@server-3632d7f9-5780-46d9-a3fc-c9692d9c0699:~$ sudo chroot /mnt/arm64/
root@server-3632d7f9-5780-46d9-a3fc-c9692d9c0699:/# apt-get update
0% [Working]qemu: Unsupported syscall: 269
qemu: Unsupported syscall: 269
qemu: Unsupported syscall: 269
qemu: Unsupported syscall:
Updated patch for arm64. This one I was able to test since arm64 tools
are now available in the simple stream :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1276909
Title:
** Patch added: updated arm64 patch for manual provider support
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1276909/+attachment/3996477/+files/juju-manual-arm64.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
I've found a couple conditions that causes qemu-user-static to core dump
fairly reliably - same with upstream git - while a binary built from
suse's aarch64-1.6 branch seems to consistently work fine.
Testing suggests they are resolved by the sigprocmask wrapper patches
On Thu, Feb 27, 2014 at 3:34 PM, Serge Hallyn
1285...@bugs.launchpad.net wrote:
Dann,
can you confirm that you can reproduce this with the upstream git head
(or the qemu-2.0~git package)?
I just reverified with upstream git head @
9fbee91a131a05e443d7108d7fbdf3ca91020290.
Note that this
** Patch added: juju-core-arm64-v3.patch
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1276909/+attachment/4000250/+files/juju-core-arm64-v3.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
On Thu, Feb 27, 2014 at 8:20 PM, Tim Penhey tim.pen...@canonical.com wrote:
I've made a branch out of the patches (well, manually did it). @dann can
I get you to give the diff a once over?
@Tim: Yes, looks correct to me.
--
You received this bug notification because you are a member of Ubuntu
@Serge: I can confirm that this is fixed in 1.7.0+dfsg-3ubuntu5sig1 from
your ppa.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1285363
Title:
qemu-aarch64-static segfaults
To
Public bug reported:
qemu-aarch64-static from qemu-user-static 1.7.0+dfsg-3ubuntu5
(I haven't tried reproducing w/ upstream git yet)
In an arm64 trusty chroot on an amd64 system:
dannf@server-75e0210e-4f99-4c86-9277-3201ab7b6afd:~$ java
#
# A fatal error has been detected by the Java Runtime
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1289527
Title:
qemu-aarch64-static: java dies with SIGILL
To manage
MAAS does not pull in ipmitool by default (it is a Suggests, due to
ipmitool being in universe). While I understand that we can't add a
strict dependency w/o including ipmitool in main, I do think it is an
issue that it can cause MAAS to silently fail to work. IMO, there should
minimally be some
Try installing 'openipmi' - it should cause the modules to get loaded at
boot, and it is a Suggests of the ipmitool package.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/908112
I've prepared a potential fix for this issue in ppa:ce-hyperscale/ce-
hyperscale-scratch. Please verify and confirm that this backport
contains the required functionality.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeipmi in
** Description changed:
- As per HP for moonshot arm cartridges freeipmi changes are needed. So
- this request is to pull the patch from upstream into current version of
- trusty to support the i2c communication on HP moonshot chassis.
+ [Impact]
+ freeipmi is unable to reliable communicate with
Public bug reported:
The description of this package says This package contains the keys
used for files on cloud-images.ubuntu.com. However, the checksum files
are signed with keyid 7DB87C81, which I can't find in this package.
ubuntu@server-46af3152-8a83-4995-8dfb-e3b2d07e0841:~$ wget
OK, turns out it was a firmware setting that Manoj was missing in the
previous comment.
On a system with the correct setting, this is what freeipmi shows w/o my branch:
root@ubuntu:/home/ubuntu# bmc-info --no-probing --driver-type=SSIF
--driver-address=0x10 --driver-device=/dev/i2c-2
** Changed in: freeipmi (Ubuntu)
Status: New = Confirmed
** Changed in: freeipmi (Ubuntu Trusty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeipmi in Ubuntu.
** Bug watch added: Debian Bug tracker #754807
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754807
** Also affects: freeipmi (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754807
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
freeipmi supports an SSIF driver mode that uses the kernel's /dev/i2c-*
interface. However, this interface is only exposed when the i2c-dev
module is loaded, and this appears to be a manual process today.
Some options I see:
- Link i2c-dev statically in the kernel. This
Using 2.1+dfsg-2ubuntu2 from utopic within a trusty ubuntu core:
# /usr/bin/qemu-aarch64-static -d unimp /usr/bin/java
host mmap_min_addr=0x1
Reserved 0x12000 bytes of guest address space
Relocating guest address space from 0x0040 to 0x40
guest_base 0x0
startend
I'm also seeing a SEGV (not a SIGILL) when testing the version of QEMU
that shipped in trusty. So, we might just consider this bug fixed and
track this segfault issue separately.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in
Public bug reported:
Using 2.1+dfsg-2ubuntu2 from utopic within a trusty ubuntu core:
# /usr/bin/qemu-aarch64-static -d unimp /usr/bin/java
host mmap_min_addr=0x1
Reserved 0x12000 bytes of guest address space
Relocating guest address space from 0x0040 to 0x40
guest_base 0x0
** Summary changed:
- Ubuntu 14.04 cannnot ssh into Chassis Manager
+ Ubuntu 14.04 cannot ssh into Chassis Manager
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1311250
Title:
I've prepared a git branch against Debian's mysql-5.6 tree w/ fixes that pass
my test on ARM64:
https://github.com/dannf/mysql-5.6.git
I should note that this was really a mechanical port w/ blackbox
testing. I'm not an expert in the semantics at this level - and the code
here had diverged
Public bug reported:
I've verified that the following MariaDB issue also impacts MySQL:
https://mariadb.atlassian.net/browse/MDEV-6615
[Impact]
Data corruption on arm64 (and maybe ppc64el?)
[Test Case]
Reproducibility varies across SoCs but, at least on one SoC, it reliably fails
within
** Patch added: mysql-5.6-vivid.patch
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1427406/+attachment/4332652/+files/mysql-5.6-vivid.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
** Also affects: mysql-5.6 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: mysql-5.6 (Ubuntu Vivid)
Importance: Critical
Status: Confirmed
** Also affects: mysql-5.6 (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: mysql-5.6
** Bug watch added: MySQL Bug System #76135
http://bugs.mysql.com/bug.php?id=76135
** Also affects: mysql-server via
http://bugs.mysql.com/bug.php?id=76135
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Also affects: mariadb-5.5 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mariadb-10.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
** Changed in: mariadb-5.5 (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: mariadb-5.5 (Ubuntu Trusty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
Apparently the fix I've proposed here caused regressions in MariaDB and was
reworked:
https://mariadb.atlassian.net/browse/MDEV-7026
Unfortunately, the reworking reintroduces the problem on arm64:
https://mariadb.atlassian.net/browse/MDEV-7658
--
You received this bug notification because
** No longer affects: mariadb-5.5 (Ubuntu Vivid)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1427406
Title:
data corruption on arm64
To manage notifications about this bug go
I'm working on MAAS enablement for a system that will require a = 3.18
kernel and I've hit this issue in trusty. I'm obviously using custom
images since trusty doesn't include a newer kernel - but I wonder if
this won't be a problem with hwe-v images starting in 14.04.3.
** Also affects: linux
** Description changed:
- There appears to be an issue with the use of overlayfs in the image. See
- the attached screenshot for details. Immediately after that overlayfs
- error the kernel panics.
+ [Impact]
+ overlayfs support doesn't work with kernels 3.18 which will, for example,
break MAAS
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: cloud-initramfs-tools (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: cloud-initramfs-tools (Ubuntu Trusty)
Assignee: (unassigned) = dann frazier (dannf
** Description changed:
- We need to add support to curtin for supporting UEFI-based ARM64
- systems.
+ [Impact]
+ Curtin doesn't support UEFI-based ARM64 systems.
+
+ [Test Case]
+ Use Curtin to install an ARM64-UEFI system. We did this testing with MAAS
incorporating this MP:
+
** Changed in: mysql-5.6 (Ubuntu Vivid)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1427406
Title:
data corruption on arm64
To manage
** Changed in: mysql-5.6 (Ubuntu Trusty)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1427406
Title:
data corruption on arm64
To manage
** Changed in: mysql-5.6 (Ubuntu Utopic)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1427406
Title:
data corruption on arm64
To manage
** Also affects: mysql-5.5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.5 in Ubuntu.
https://bugs.launchpad.net/bugs/1427406
Title:
data corruption on arm64
To manage
** Changed in: mysql-5.5 (Ubuntu Utopic)
Status: New = In Progress
** Description changed:
I've verified that the following MariaDB issue also impacts MySQL:
- https://mariadb.atlassian.net/browse/MDEV-6615
-
+ https://mariadb.atlassian.net/browse/MDEV-6615
[Impact]
- Data
** Changed in: mysql-5.5 (Ubuntu Trusty)
Status: New = In Progress
** Changed in: mysql-5.6 (Ubuntu Utopic)
Importance: Undecided = Critical
** Changed in: mysql-5.5 (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: mysql-5.5 (Ubuntu Utopic)
Importance: Undecided =
On Wed, May 27, 2015 at 2:59 AM, jpo j...@joerg-pommnitz.de wrote:
The Fix in 0.26ubuntu1 does not address the fact that the module was
renamed from overlayfs to overlay.
Note that the Ubuntu 15.04 kernel contains patches to provide
backwards compatibility:
** Bug watch added: Debian Bug tracker #787221
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787221
** Also affects: mariadb-10.0 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787221
Importance: Unknown
Status: Unknown
--
You received this bug notification
Fixes for mariadb-5.5 and mariadb-10.0 are now available upstream:
https://mariadb.atlassian.net/browse/MDEV-7658
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1427406
Title:
** Also affects: mysql-5.6 (Ubuntu Wily)
Importance: Critical
Status: Confirmed
** Also affects: mariadb-5.5 (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: mariadb-10.0 (Ubuntu Wily)
Importance: Undecided
Status: New
** No longer affects:
On Wed, Jul 1, 2015 at 9:33 AM, Chris J Arges
1427...@bugs.launchpad.net wrote:
Actually these looked ok, go ahead and re-upload. Sorry about the noise.
Done.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
Debian has been updated to 2.3 which includes the upstream fix, so
ignore my last comment. I assume wily will get a 2.3 upload soon, and
that will fix the issue there.
I have pushed a branch for vivid to git://git.launchpad.net/~dannf/qemu
(lp1457639-vivid)
--
You received this bug notification
Public bug reported:
[Impact]
qemu-img frequently hangs when converting a file to qcow2 on a system with a
large number of cores.
[Test Case]
On a system with a large number of cores (my test system has 48), run:
wget
I pushed a fix based on the debian-unstable branch to:
git://git.launchpad.net/~dannf/qemu
I haven't been able to reproduce this issue on Debian unstable so I
didn't file a Debian bug. However, as the upstream commit log describes,
easy reproduction is pretty sensitive to the environment and
1 - 100 of 136 matches
Mail list logo
