[Bug 1554098] Re: Update s390x syscall tables
Thanks - I've updated the title of the bug to be about the syscall tables - I'll leave it to the Ubuntu dev to figure out if it makes sense to fix this w/ a new upstream or a backport. ** Summary changed: - Rebase libseccomp from (2.2.3-3) -> 2.3.0 + Update s390x syscall tables ** Changed in: libseccomp (Ubuntu) Status: Incomplete => Confirmed ** Changed in: libseccomp (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Dimitri John Ledkov (xnox) ** Changed in: libseccomp (Ubuntu) Importance: Wishlist => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1554098 Title: Update s390x syscall tables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1554098/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1554098] Re: Rebase libseccomp from (2.2.3-3) -> 2.3.0
s390x support has been backported to Ubuntu 2.2.3 packages. Is there some bug fix or additional functionality missing from that backport? If so, I suggest we reframe/retitle this bug to be about that functionality - that'll be more actionable than a new upstream version at this stage. ** Changed in: libseccomp (Ubuntu) Status: New => Incomplete ** Changed in: libseccomp (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1554098 Title: Rebase libseccomp from (2.2.3-3) -> 2.3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1554098/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1545749] Re: libibverbs1: add s390x support
** Changed in: libibverbs (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libibverbs in Ubuntu. https://bugs.launchpad.net/bugs/1545749 Title: libibverbs1: add s390x support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1545749/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1540407] Re: multipathd drops paths of a temporarily lost device
** Changed in: multipath-tools (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => Canonical Server Team (canonical-server) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1540407 Title: multipathd drops paths of a temporarily lost device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540407/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1540407] Re: multipathd drops paths of a temporarily lost device
** Changed in: multipath-tools (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1540407 Title: multipathd drops paths of a temporarily lost device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540407/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4
Marking as impacting juju-core/trusty. This is easily reproduced by attempting to bootstrap a juju-local environment in trusty with juju- core 1.24.7-0ubuntu1~14.04.1 when using a kernel w/ 4 level page tables. This will be a supported config once the xenial-lts kernel is available in trusty. A no-change rebuild of juju-core trusty would be sufficient to resolve this issue. ubuntu@cvm2s2:~$ juju bootstrap --verbose Bootstrapping environment "local" Starting new instance for initial state server Building tools to upload (1.24.7.1-trusty-arm64) Bootstrap failed, destroying environment ERROR failed to bootstrap environment: cannot upload bootstrap tools: cannot get version from "/tmp/juju-tools525417221/jujud": exit status 2; p=0x9354f000 fatal error: runtime_lfstackpush: invalid pointer runtime stack: :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 goroutine 1 [garbage collection]: github.com_juju_cmd.DefaultContext /build/juju-core-qiO5uV/juju-core-1.24.7/src/github.com/juju/cmd/cmd.go:261 main.Main /build/juju-core-qiO5uV/juju-core-1.24.7/src/github.com/juju/juju/cmd/jujud/main.go:166 main.MainWrapper /build/juju-core-qiO5uV/juju-core-1.24.7/src/github.com/juju/juju/cmd/jujud/main.go:151 main.main /build/juju-core-qiO5uV/juju-core-1.24.7/src/github.com/juju/juju/cmd/jujud/main_nix.go:13 goroutine 3 [syscall]: goroutine in C code; stack unavailable ** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu) Status: New => Triaged -- 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/1472650 Title: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4 To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1472650/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1507244] Re: Missing erasure coding plugins for jerasure/neon and shec
** Changed in: ceph (Ubuntu Vivid) Status: Confirmed => In Progress -- 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/1507244 Title: Missing erasure coding plugins for jerasure/neon and shec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1507244/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457639] Re: qemu-img qcow2 conversion hangs on large core systems
** Patch added: "patch from my vivid git branch" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1457639/+attachment/4507008/+files/aio-strengthen-memory-barriers-for-bottom-half-sched.patch -- 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/1457639 Title: qemu-img qcow2 conversion hangs on large core systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1457639/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457639] Re: qemu-img qcow2 conversion hangs on large core systems
@Serge: I identified the patch that fixes this - see comment #2. -- 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/1457639 Title: qemu-img qcow2 conversion hangs on large core systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1457639/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457639] Re: qemu-img qcow2 conversion hangs on large core systems
Sorry for the additional post - I just noticed that @Haw was asking about trusty. As I recall, the issue fixed by the patch I provided was introduced in vivid, and was fixed before wily. In other words, only vivid should be impacted. I'm surprised to hear that it impacts trusty. -- 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/1457639 Title: qemu-img qcow2 conversion hangs on large core systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1457639/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1508577] Re: [wily] installing juju-local on ARM64 failed. broken apt dependency
fwiw, this isn't a general arm64 problem. I can install juju-local on a mustang running wily w/o a problem. I suspect it maybe due to using a custom kernel, possibly with some networking features disabled in the config. I've asked Manoj to set -x /usr/lib/aarch64-linux-gnu/lxc/lxc- net to see if that is the case. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1508577 Title: [wily] installing juju-local on ARM64 failed. broken apt dependency To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1508577/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1499838] Re: ipmi-locate causes synchronous external abort on ARM
I've verified this no longer crashes on arm64, and that the output of ipmi-locate on an x86 system (with a BMC) is identical before and after this update. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1499838 Title: ipmi-locate causes synchronous external abort on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1499838/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1499838] Re: ipmi-locate causes synchronous external abort on ARM
** Bug watch added: Debian Bug tracker #800038 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800038 ** Also affects: freeipmi (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800038 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1499838 Title: ipmi-locate causes synchronous external abort on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1499838/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1499838] Re: ipmi-locate causes synchronous external abort on ARM
** Also affects: freeipmi (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: freeipmi (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: freeipmi (Ubuntu Wily) Importance: Undecided Assignee: Newell Jensen (newell-jensen) Status: Confirmed ** Also affects: freeipmi (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: freeipmi (Ubuntu Vivid) 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. https://bugs.launchpad.net/bugs/1499838 Title: ipmi-locate causes synchronous external abort on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1499838/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault
** Changed in: irqbalance (Ubuntu Vivid) Status: Triaged => In Progress ** Changed in: irqbalance (Ubuntu Trusty) Status: Triaged => In Progress ** Changed in: irqbalance (Ubuntu Utopic) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1469214 Title: HP ProLiant m400 Server crashes with unhandled level 3 translation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault
** Changed in: irqbalance (Ubuntu Wily) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1469214 Title: HP ProLiant m400 Server crashes with unhandled level 3 translation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457639] Re: qemu-img qcow2 conversion hangs on large core systems
** Changed in: qemu (Ubuntu Vivid) Status: Confirmed = In Progress -- 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/1457639 Title: qemu-img qcow2 conversion hangs on large core systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1457639/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
SRU regression test results: ubuntu@ip-10-180-202-218:~/qa-regression-testing/scripts$ ./test-qemu.py Skipping private tests WARN: could not find 'libvirt/qatest.tar.bz2'. Some tests will be skipped Please see qemu/README.qatest-virtio for more information. add dummy drive delete dummy drive (drive_del) hotplug scsi drive hotunplug scsi drive (drive_del) hotplug virtio drive hotunplug virtio drive (drive_del) .. block (libvirt/qatest/qatest.qcow2) blockstats (ide0-hd0: rd_bytes=) chardev (chardevmon: filename=null) chardev (filename=tcp:127.0.0.1:,server) cpus (* CPU #0: ) history (: 'info block') jit (Translation buffer state) mice (QEMU PS/2 Mouse) name (qatest-vm) network (user.0: index=0,type=user,net=10) numa (0 nodes) pci (Bridge: PCI device) pci (Host bridge: PCI device) pci (IDE controller: PCI device) pci (ISA bridge: PCI device) pci (VGA controller: PCI device) qdm (virtio-blk-pci) qdm (virtio-net-pci) qtree (bus: main-system-bus) registers (EAX=) registers (EIP=) roms (name=) status (VM status: running) usb (info usb) usernet (VLAN 0 (user.0)) uuid (ded3a46b-bb60-43f4-8113-d041aeb93cdf) version ((qemu) ... create snapshot start with -drive file=snapshot stop and verify backing store start with -snapshot stop and verify backing store ... cow qcow qcow2 vdi vmdk vpc . cow qcow qcow2 vdi vmdk vpc AC97 ES1370 VGA cirrus-vga e1000 hda-duplex (skipping start) hda-output (skipping start) i6300esb i82550 i82551 i82557a i82557b i82557c i82558a i82558b i82559a i82559b i82559c i82559er i82562 i82801 ib700 ich9-ahci ide-cd (skipping start) ide-drive (skipping start) ide-hd (skipping start) intel-hda ioh3420 isa-applesmc isa-debugcon (skipping start) isa-ide (skipping start) isa-parallel (skipping start) isa-serial (skipping start) ivshmem (skipping start) lsi53c895a ne2k_isa (skipping start) ne2k_pci pci-ohci pcnet piix3-usb-uhci piix4-usb-uhci rtl8139 sb16 scsi-cd (skipping start) scsi-disk (skipping start) scsi-generic (skipping start) scsi-hd (skipping start) usb-braille (skipping start) usb-bt-dongle (skipping start) usb-host usb-hub usb-kbd usb-mouse usb-net usb-serial (skipping start) usb-storage (skipping start) usb-tablet usb-wacom-tablet virtconsole (skipping start) virtio-9p-pci (skipping start) virtio-balloon-pci virtio-blk-pci (skipping start) virtio-net-pci virtio-serial-pci virtserialport (skipping start) vmware-svga vt82c686b-usb-uhci x3130-upstream xio3130-downstream . pc isapc pc-0.10 pc-0.11 pc-0.12 pc-0.13 pc-0.14 . -- Ran 15 tests in 308.960s OK -- 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
Verification: dannf@mustang:~$ lxc launch trusty lp1389897 Creating container...done Starting container...done dannf@mustang:~$ lxc exec lp1389897 -- /bin/bash root@lp1389897:~# echo 'deb http://ports.ubuntu.com/ubuntu-ports trusty-proposed main' | tee -a /etc/apt/sources.list deb http://ports.ubuntu.com/ubuntu-ports trusty-proposed main root@lp1389897:~# apt-get update apt-get install qemu-kvm -y Ign http://ports.ubuntu.com trusty InRelease Ign http://ports.ubuntu.com trusty-updates InRelease Ign http://ports.ubuntu.com trusty-security InRelease Ign http://ports.ubuntu.com trusty-proposed InRelease Hit http://ports.ubuntu.com trusty Release.gpg Get:1 http://ports.ubuntu.com trusty-updates Release.gpg [933 B] Get:2 http://ports.ubuntu.com trusty-security Release.gpg [933 B] Get:3 http://ports.ubuntu.com trusty-proposed Release.gpg [933 B] Hit http://ports.ubuntu.com trusty Release Get:4 http://ports.ubuntu.com trusty-updates Release [63.5 kB] Get:5 http://ports.ubuntu.com trusty-security Release [63.5 kB] Get:6 http://ports.ubuntu.com trusty-proposed Release [211 kB] Hit http://ports.ubuntu.com trusty/main arm64 Packages Hit http://ports.ubuntu.com trusty/restricted arm64 Packages Hit http://ports.ubuntu.com trusty/universe arm64 Packages Hit http://ports.ubuntu.com trusty/multiverse arm64 Packages Hit http://ports.ubuntu.com trusty/main Translation-en Hit http://ports.ubuntu.com trusty/multiverse Translation-en Hit http://ports.ubuntu.com trusty/restricted Translation-en Hit http://ports.ubuntu.com trusty/universe Translation-en Get:7 http://ports.ubuntu.com trusty-updates/main arm64 Packages [482 kB] Get:8 http://ports.ubuntu.com trusty-updates/restricted arm64 Packages [28 B] Get:9 http://ports.ubuntu.com trusty-updates/universe arm64 Packages [283 kB] Get:10 http://ports.ubuntu.com trusty-updates/multiverse arm64 Packages [9391 B] Get:11 http://ports.ubuntu.com trusty-updates/main Translation-en [288 kB] Hit http://ports.ubuntu.com trusty-updates/multiverse Translation-en Get:12 http://ports.ubuntu.com trusty-updates/restricted Translation-en [3560 B] Get:13 http://ports.ubuntu.com trusty-updates/universe Translation-en [160 kB] Get:14 http://ports.ubuntu.com trusty-security/main arm64 Packages [262 kB] Get:15 http://ports.ubuntu.com trusty-security/restricted arm64 Packages [28 B] Get:16 http://ports.ubuntu.com trusty-security/universe arm64 Packages [106 kB] Get:17 http://ports.ubuntu.com trusty-security/multiverse arm64 Packages [1660 B] Get:18 http://ports.ubuntu.com trusty-security/main Translation-en [178 kB] Hit http://ports.ubuntu.com trusty-security/multiverse Translation-en Hit http://ports.ubuntu.com trusty-security/restricted Translation-en Get:19 http://ports.ubuntu.com trusty-security/universe Translation-en [65.6 kB] Get:20 http://ports.ubuntu.com trusty-proposed/main arm64 Packages [133 kB] Get:21 http://ports.ubuntu.com trusty-proposed/main Translation-en [74.6 kB] Fetched 2388 kB in 10s (233 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: acl ca-certificates libaio1 libasn1-8-heimdal libasound2 libasound2-data libasyncns0 libbluetooth3 libboost-atomic1.54.0 libboost-system1.54.0 libboost-thread1.54.0 libbrlapi0.6 libcaca0 libcap-ng0 libcurl3-gnutls libfdt1 libflac8 libglib2.0-0 libglib2.0-data libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal libidn11 libkrb5-26-heimdal libldap-2.4-2 libnspr4 libnss3 libnss3-nssdb libogg0 libpixman-1-0 libpulse0 librados2 librbd1 libroken18-heimdal librtmp0 libsasl2-2 libsasl2-modules libsasl2-modules-db libsdl1.2debian libsndfile1 libusb-1.0-0 libusbredirparser1 libvorbis0a libvorbisenc2 libwind0-heimdal libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxext6 libxml2 openssl qemu-keymaps qemu-system-arm qemu-system-common qemu-utils sgml-base shared-mime-info sharutils xml-core Suggested packages: libasound2-plugins alsa-utils pulseaudio libsasl2-modules-otp libsasl2-modules-ldap libsasl2-modules-sql libsasl2-modules-gssapi-mit libsasl2-modules-gssapi-heimdal samba vde2 debootstrap sgml-base-doc bsd-mailx mailx debhelper The following NEW packages will be installed: acl ca-certificates libaio1 libasn1-8-heimdal libasound2 libasound2-data libasyncns0 libbluetooth3 libboost-atomic1.54.0 libboost-system1.54.0 libboost-thread1.54.0 libbrlapi0.6 libcaca0 libcap-ng0 libcurl3-gnutls libfdt1 libflac8 libglib2.0-0 libglib2.0-data libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal libidn11 libkrb5-26-heimdal libldap-2.4-2 libnspr4 libnss3 libnss3-nssdb libogg0 libpixman-1-0 libpulse0 librados2 librbd1 libroken18-heimdal librtmp0 libsasl2-2 libsasl2-modules libsasl2-modules-db
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
** Description changed: - There is currently no way to install just enough qemu to have kvm work. - On x86 you can install qemu-kvm, but even on the other architectures - where this is built (e.g. armhf) it depends on qemu-system-x86. Or you - can install qemu-system but that installs way more than you need. + [Impact] + There is currently no way to install just enough qemu to have kvm work. On x86 you can install qemu-kvm, but even on the other architectures where this is built (e.g. armhf) it depends on qemu-system-x86. Or you can install qemu-system but that installs way more than you need. - Quick consensus seemed to be that qemu-kvm should depend on the - appropriate qemu-system-$ARCH. + [Test Case] + $ apt-get install qemu-kvm + This should pull in the appropriate qemu packages to run KVM on the host. + + [Regression Risk] + This is a new package for some archs (arm64/powerpc/ppc64el), so that minimizes the risk of regression there. The biggest risk I see is if someone on armhf was using 'apt-get install qemu-kvm' as a shorthand for installing qemu-system-x86. It seems unlikely (read: very slow) for someone to try to be running emulated x86 on armhf. That said, the upgrade to this won't force qemu-system-x86 off of their system - it would just be a behavior change for new installs. -- 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
** No longer affects: qemu (Ubuntu Utopic) -- 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
** Patch added: debdiff for trusty https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+attachment/4439054/+files/trusty.debdiff -- 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1419262] Re: mysql-5.5 test suite no longer works because of timestamps in the past
On Fri, Jul 17, 2015 at 2:56 PM, Steve Langasek steve.langa...@canonical.com wrote: The SSL tests no longer fail, but the mysql5.6 package is still failing its test suite, now because of the test 'main.ctype_uca'. The failure can be found at https://jenkins.qa.ubuntu.com/job/trusty- adt-mysql-5.6/15/ARCH=amd64,label=adt/console: main.ctype_uca [ fail ] Test ended at 2015-07-17 17:52:51 CURRENT_TEST: main.ctype_uca mysqltest: At line 554: command remove_file failed with error 1. my_errno=13 The result from queries just before the failure was: snip 1 SIMPLE t1 range c c 42 NULL3 Using where; Using index SELECT hex(c), hex(weight_string(c)) FROM t1 WHERE c LIKE 'a%' ORDER BY c; hex(c) hex(weight_string(c)) 61 120F 61F0909080 120F30D2 61EFBFBF120FFBC1 61F48FBFBF 120FFBE1 SELECT hex(c), hex(weight_string(c)), c FROM t1 WHERE c LIKE _utf32 0x10400 ORDER BY c, BINARY c; hex(c) hex(weight_string(c)) c F090908030D2 F09090A830D2 SELECT hex(c), hex(weight_string(c)), c FROM t1 WHERE c LIKE _utf32 0x10428 ORDER BY c, BINARY c; hex(c) hex(weight_string(c)) c F090908030D2 F09090A830D2 DROP TABLE t1; # # Bug #16204175 : COLLATION NAME MISSING FROM LOG MESSAGES # ABOUT LDML DEFINITION PROBLEMS # More results from queries before failure can be found in /tmp/tmp.cJlnK7IBON/var/log/ctype_uca.log - saving '/tmp/tmp.cJlnK7IBON/var/log/main.ctype_uca/' to '/tmp/tmp.cJlnK7IBON/var/log/main.ctype_uca/' Retrying test main.ctype_uca, attempt(2/3)... main.ctype_uca [ retry-fail ] Test ended at 2015-07-17 17:52:53 CURRENT_TEST: main.ctype_uca mysqltest: At line 553: command copy_file failed with error 1. my_errno=17 The result from queries just before the failure was: snip 1 SIMPLE t1 range c c 42 NULL3 Using where; Using index SELECT hex(c), hex(weight_string(c)) FROM t1 WHERE c LIKE 'a%' ORDER BY c; hex(c) hex(weight_string(c)) 61 120F 61F0909080 120F30D2 61EFBFBF120FFBC1 61F48FBFBF 120FFBE1 SELECT hex(c), hex(weight_string(c)), c FROM t1 WHERE c LIKE _utf32 0x10400 ORDER BY c, BINARY c; hex(c) hex(weight_string(c)) c F090908030D2 F09090A830D2 SELECT hex(c), hex(weight_string(c)), c FROM t1 WHERE c LIKE _utf32 0x10428 ORDER BY c, BINARY c; hex(c) hex(weight_string(c)) c F090908030D2 F09090A830D2 DROP TABLE t1; # # Bug #16204175 : COLLATION NAME MISSING FROM LOG MESSAGES # ABOUT LDML DEFINITION PROBLEMS # More results from queries before failure can be found in /tmp/tmp.cJlnK7IBON/var/log/ctype_uca.log - saving '/tmp/tmp.cJlnK7IBON/var/log/main.ctype_uca/' to '/tmp/tmp.cJlnK7IBON/var/log/main.ctype_uca/' Test main.ctype_uca has failed 2 times, no more retries! The problem occurs on both amd64 and i386. This appears to be a new test is the latest upload of mysql5.6 and should probably just be disabled? Nevertheless, this should be resolved before promoting this package since otherwise the problem of the package failing its test suite has not been addressed... This test was failing because it expects to be able to write to /usr. I've disabled it, and now the test suites pass. New uploads for trusty and utopic are awaiting approval. I also included a workaround for the FTBFS of mysql-5.6/trusty on arm64 introduced by the gcc-4.8 SRU - both are fixes that were previously included in later mysql-5.6 uploads. -dann -- 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/1419262 Title: mysql-5.5 test suite no longer works because of timestamps in the past To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1419262/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64 and ppc64el
** Changed in: mariadb-5.5 (Ubuntu) Status: New = Fix Released ** Changed in: mysql-5.5 (Ubuntu) Status: New = Invalid ** Changed in: mariadb-5.5 (Ubuntu) Status: Fix Released = Invalid -- 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 and ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault
Ming was able to help me reliable reproduce this with the command: stress-ng --sequential 0 --seq-start 86 --seq-end 90 -t 60 --syslog --metrics --times -v I prepared a wily package w/ the proposed upstream backport for testing: lp:~dannf/ubuntu/wily/irqbalance/lp1469214 Unfortunately, I'm still seeing irqbalance crash even with this backport: [ 2461.635168] irqbalance[558]: unhandled input address range fault (11) at 0x20202020202034, esr 0x9204 [ 2461.635175] pgd = ffcfab3f3000 [ 2461.675979] [20202020202034] *pgd= [ 2461.733566] CPU: 4 PID: 558 Comm: irqbalance Not tainted 3.13.0-57-generic #95-Ubuntu [ 2461.733570] task: ffcfa9cdcd00 ti: ffcfa9df8000 task.ti: ffcfa9df8000 [ 2461.733577] PC is at 0x40605c [ 2461.733580] LR is at 0x4040e4 [ 2461.733582] pc : [0040605c] lr : [004040e4] pstate: 8000 [ 2461.733584] sp : 007fd95cf7a0 [ 2461.733585] x29: 007fd95cf7a0 x28: 0041a000 [ 2461.733588] x27: 0041a000 x26: 00409510 [ 2461.733591] x25: 0041a000 x24: 00405000 [ 2461.733593] x23: 0041acf8 x22: 0041a000 [ 2461.733596] x21: 14ab0130 x20: 0041a000 [ 2461.733598] x19: 14a9f0e0 x18: [ 2461.733601] x17: 007fa72118ec x16: 007fa75a72e0 [ 2461.733603] x15: 003bcfb11b54656b x14: 2030203020302030 [ 2461.733606] x13: 2030203020302030 x12: 2030203020302030 [ 2461.733608] x11: 2030203020302030 x10: 2030203020302030 [ 2461.733611] x9 : 2030203020302030 x8 : 14a9bc80 [ 2461.733613] x7 : 0020 x6 : 14a9bc90 [ 2461.733616] x5 : 0001 x4 : 007fa722a2a0 [ 2461.733618] x3 : 14a9b880 x2 : 0001 [ 2461.733620] x1 : 4320202020202020 x0 : 3355000a -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1469214 Title: HP ProLiant m400 Server crashes with unhandled level 3 translation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64 and ppc64el
mysql-5.5/utopic verified. The last remaining mysql update is mysql-5.6/trusty which I had to reupload to fix a FTBFS issue unrelated to this update (LP: #1419262). ** Changed in: mariadb-10.0 (Ubuntu Utopic) Status: New = Invalid ** Changed in: mariadb-10.0 (Ubuntu Trusty) Status: New = Invalid ** Changed in: mariadb-10.0 (Ubuntu Wily) Status: New = Triaged -- 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 and ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64 and ppc64el
Fixed by inclusion of micro release 5.5.44. ** Changed in: mariadb-5.5 (Ubuntu Utopic) Status: New = Fix Released -- 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 and ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64 and ppc64el
Fixed by inclusion of micro release 5.5.44. ** Changed in: mariadb-5.5 (Ubuntu Trusty) Status: Confirmed = Fix Released -- 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 and ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault
On Mon, Jul 13, 2015 at 9:27 AM, Ming Lei 1469...@bugs.launchpad.net wrote: Dann, Please follow the steps in #12, in which you should trigger the crash in 4 minutes. I've been running that in a loop and I'm currently on iteration #76 w/o a crash :( Maybe it's Linux ms10-33-mcdivittB0 3.19.0-22-generic #22-Ubuntu SMP Tue Jun 16 17:18:17 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux BTW, looks wily kernel can't boot to shell prompt on mcdivitt. OK - mind filing a separate bug for that? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1469214 Title: HP ProLiant m400 Server crashes with unhandled level 3 translation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1419262] Re: mysql-5.5 test suite no longer works because of timestamps in the past
** Also affects: mysql-5.5 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: mysql-5.6 (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: mysql-5.6 (Ubuntu Trusty) Status: New = In Progress ** Changed in: mysql-5.6 (Ubuntu Trusty) Assignee: (unassigned) = dann frazier (dannf) ** Changed in: mysql-5.6 (Ubuntu Trusty) Importance: Undecided = High ** Changed in: mysql-5.5 (Ubuntu Trusty) Status: New = Invalid -- 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/1419262 Title: mysql-5.5 test suite no longer works because of timestamps in the past To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1419262/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64 and ppc64el
mysql-5.5/trusty verified. -- 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 and ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault
On Tue, Jul 7, 2015 at 2:25 AM, Ming Lei 1469...@bugs.launchpad.net wrote: On Tue, Jul 7, 2015 at 11:16 AM, Ming Lei ming@canonical.com wrote: Looks there are two kinds of translation fault from irqbalance: 1) happend in place_irq_in_node() which can reproduce in vivid package 2) the 2nd one happened in glib2, which is built by myself, because irqbalance can choose to use its own local glib if there isn't glib2 available, and the glib2 does exist in my server in which I build irqbalance. Both of two above reports can be fixed by the following irqbalance commit: NUMA is not available fix https://github.com/Irqbalance/irqbalance/commit/a3c812eb6cd627cd3fae45b8345538558b86973c Looks stress-ng can't only find kernel bug, but also userspace issue, :-) I was looking to upload a fix for wily, but I haven't been able to reproduce it to in order to verify the fix. I ran 'stress-ng --seq 0 -t 60 --syslog --metrics --times -v' overnight in a loop, but irqbalance never crashed. How long should I expect this to take on average? Does it usually crash in a single run? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1469214 Title: HP ProLiant m400 Server crashes with unhandled level 3 translation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64 and ppc64el
I've verified mysql-5.6/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 and ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64 and ppc64el
Also verified mysql-5.6/utopic. -- 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 and ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1447834] Re: curtin doesn't support arm64-efi targets
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1447834 Title: curtin doesn't support arm64-efi targets To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1447834/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault
** Also affects: irqbalance (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: irqbalance (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: irqbalance (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Medium Assignee: dann frazier (dannf) Status: Triaged ** Also affects: irqbalance (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1469214 Title: HP ProLiant m400 Server crashes with unhandled level 3 translation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1427406] Re: data corruption on arm64 and ppc64el
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. https://bugs.launchpad.net/bugs/1427406 Title: data corruption on arm64 and ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1447834] Re: curtin doesn't support arm64-efi targets
** 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: +https://code.launchpad.net/~newell-jensen/maas/uefi-arm64/+merge/260639 + + [Regression Risk] + 2/3 of the curtin changes are preventing code that was running on all aarch64 platforms to just running on non-UEFI aarch64 systems. Since we only supported non-UEFI systems before, that should be a low risk of regression. + + The only other change is adding the grub target name for arm64, which is + also pretty straightforward. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1447834 Title: curtin doesn't support arm64-efi targets To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1447834/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
** 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 corruption on arm64 (and maybe ppc64el?) + Data corruption on arm64 and ppc64el [Test Case] Reproducibility varies across SoCs but, at least on one SoC, it reliably fails within seconds with these sysbench commands: sysbench --num-threads=128 --max-requests=0 --max-time=1000 --test=oltp prepare sysbench --num-threads=128 --max-requests=0 --max-time=1000 --test=oltp run On failure, mysql will crash and sysbench will report a connection loss to the database. [Regression Risk] The fix touch some low level locking code, so there is always the risk that it introduces a problem on other platforms. However, this fix has been included in MariaDB since the 10.0.13 release in Aug, 2014 so it has had some real world testing. ** Summary changed: - data corruption on arm64 + data corruption on arm64 and ppc64el -- 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 and ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64 and ppc64el
** 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 = Critical -- 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 and ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
** 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 notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
** 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 notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
** 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 notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
** 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 notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1411294] Re: kernel panic during MAAS fastpath install of Vivid images
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: http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/fs/overlayfs?id=2b561327c40709b6f2145fe3c4c3159289653e7b I do, however, agree that overlayroot should also support kernels w/o these patches (e.g. upstream). I'd personally recommend filing that as a separate bug though, as this one has been fixed and has reached a terminal state. -dann -- You received this bug notification because you are a bug assignee. https://bugs.launchpad.net/bugs/1411294 Title: kernel panic during MAAS fastpath install of Vivid images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1411294/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1411294 Title: kernel panic during MAAS fastpath install of Vivid images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1411294/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
** 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 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 to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
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: data corruption on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
** 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: mariadb-5.5 (Ubuntu Wily) -- 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 to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457639] Re: qemu-img qcow2 conversion hangs on large core systems
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 because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1457639 Title: qemu-img qcow2 conversion hangs on large core systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1457639/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457639] [NEW] qemu-img qcow2 conversion hangs on large core systems
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 http://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-arm64-disk1.img -O disk.img for i in $(seq 1 10); do qemu-img convert -O qcow2 disk.img disk.qcow2; done Mine always hangs within the first 3 iterations. [Regression Risk] Fix is a clean cherry pick from upstream, which should give us a clear path to resolution if regressions are found. ** Affects: qemu (Ubuntu) Importance: High Status: Confirmed ** Affects: qemu (Ubuntu Vivid) Importance: High Status: Confirmed ** Affects: qemu (Ubuntu Wily) Importance: High Status: Confirmed ** Tags: hs-arm64 ** Also affects: qemu (Ubuntu Wily) Importance: High Status: Confirmed ** Also affects: qemu (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Vivid) Status: New = Confirmed ** Changed in: qemu (Ubuntu Vivid) Importance: Undecided = High -- 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/1457639 Title: qemu-img qcow2 conversion hangs on large core systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1457639/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457639] Re: qemu-img qcow2 conversion hangs on large core systems
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 doesn't imply the bug is *not* there - so I'm assuming it makes more sense to go through Debian than to be an Ubuntu-specific patch. -- 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/1457639 Title: qemu-img qcow2 conversion hangs on large core systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1457639/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1411294] Re: kernel panic during MAAS fastpath install of Vivid images
** 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 commissioning/deploying using trusty+hwe-v (when it exists). + + [Test Case] + Create custom trusty image using the vivid kernel and attempt to commission a node with MAAS using that image. + + [Regression Potential] + If the kernel detection code is buggy, it could regress functionality on older kernels (e.g. 3.13/3.16). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1411294 Title: kernel panic during MAAS fastpath install of Vivid images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1411294/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1411294] Re: kernel panic during MAAS fastpath install of Vivid images
** 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) ** Changed in: cloud-initramfs-tools (Ubuntu Utopic) Assignee: (unassigned) = dann frazier (dannf) ** Changed in: cloud-initramfs-tools (Ubuntu Trusty) Status: Confirmed = In Progress ** Changed in: cloud-initramfs-tools (Ubuntu Utopic) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1411294 Title: kernel panic during MAAS fastpath install of Vivid images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1411294/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1411294] Re: kernel panic during MAAS fastpath install of Vivid images
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 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cloud-initramfs-tools (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New = Invalid ** Changed in: cloud-initramfs-tools (Ubuntu Trusty) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1411294 Title: kernel panic during MAAS fastpath install of Vivid images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1411294/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
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 quite a bit between MariaDB and MySQL. I've verified this builds on armhf, i386 and amd64 (including whatever build-time test suites run), but I haven't done any further testing on those architectures. -- 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 to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
** 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 to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
** 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. https://bugs.launchpad.net/bugs/1427406 Title: data corruption on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
** 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. https://bugs.launchpad.net/bugs/1427406 Title: data corruption on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
** 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, 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 to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
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 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 to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] [NEW] data corruption on arm64
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 seconds with these sysbench commands: sysbench --num-threads=128 --max-requests=0 --max-time=1000 --test=oltp prepare sysbench --num-threads=128 --max-requests=0 --max-time=1000 --test=oltp run On failure, mysql will crash and sysbench will report a connection loss to the database. [Regression Risk] The fix touch some low level locking code, so there is always the risk that it introduces a problem on other platforms. However, this fix has been included in MariaDB since the 10.0.13 release in Aug, 2014 so it has had some real world testing. ** Affects: mysql-5.6 (Ubuntu) Importance: Critical Status: Confirmed -- 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 to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
** 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. https://bugs.launchpad.net/bugs/1427406 Title: data corruption on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1427406] Re: data corruption on arm64
** 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 (Ubuntu Trusty) Status: New = Confirmed ** Patch added: mysql-5.6-trusty.patch https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1427406/+attachment/4332872/+files/mysql-5.6-trusty.patch ** Changed in: mysql-5.6 (Ubuntu Trusty) Importance: Undecided = Critical -- 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 to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1427406/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1311250] Re: Ubuntu 14.04 cannot ssh into Chassis Manager
** 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: Ubuntu 14.04 cannot ssh into Chassis Manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1311250/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1355934] [NEW] qemu-aarch64-static: java dies with SEGV
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 start end size prot 0040-00401000 1000 r-x 0041-00412000 2000 rw- 0040-00401000 1000 --- 00401000-004000801000 0080 rw- 004000801000-00400081c000 0001b000 r-x 00400081c000-00400082c000 0001 --- 00400082c000-00400082f000 3000 rw- start_brk 0x end_code 0x00400834 start_code 0x0040 start_data 0x00410db0 end_data 0x00411030 start_stack 0x0040008007b0 brk 0x00411038 entry 0x004000801f80 qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault (core dumped) ** Affects: qemu (Ubuntu) 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/1355934 Title: qemu-aarch64-static: java dies with SEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1355934/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1289527] Re: qemu-aarch64-static: java dies with SIGILL
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 size prot 0040-00401000 1000 r-x 0041-00412000 2000 rw- 0040-00401000 1000 --- 00401000-004000801000 0080 rw- 004000801000-00400081c000 0001b000 r-x 00400081c000-00400082c000 0001 --- 00400082c000-00400082f000 3000 rw- start_brk 0x end_code0x00400834 start_code 0x0040 start_data 0x00410db0 end_data0x00411030 start_stack 0x0040008007b0 brk 0x00411038 entry 0x004000801f80 qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault (core dumped) -- 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 notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289527/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1289527] Re: qemu-aarch64-static: java dies with SIGILL
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 Ubuntu. https://bugs.launchpad.net/bugs/1289527 Title: qemu-aarch64-static: java dies with SIGILL To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289527/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1324992] Re: freeipmi patch for HP moonshot ARM cartridges with I2c
** 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 you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1324992 Title: freeipmi patch for HP moonshot ARM cartridges with I2c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1324992/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1341788] [NEW] requires manually loading i2c-dev module in SSIF driver mode
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 would work for cases where the lowlevel i2c driver is autoloaded (which is the case today, at least with properly configured device-tree platforms). The problem is that this will consume memory on all Ubuntu systems, whether or not they support this interface and whether or not the user plans to use it. - Make freeipmi commands suggest the user load the module when it fails to find the user-requested dev entry - Make freeipmi commands automatically load the i2c-dev module, if available, when the user specifies SSIF - Introduce a package (or modify an existing package) to automatically load the i2c-dev module on boot if an i2c device is found on the system (possibly via a udev rule, or an upstart/systemd job). Precedent for this exists in the openipmi package. It should be straightforward to generate a patch to do the right thing - but we'll need some advice from the Ubuntu community to decide what the best mechanism is. ** Affects: freeipmi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1341788 Title: requires manually loading i2c-dev module in SSIF driver mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1341788/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1324992] Re: freeipmi patch for HP moonshot ARM cartridges with I2c
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 --get-device-id ipmi_cmd_get_device_id: internal system error And this is with my branch: root@ubuntu:/home/ubuntu# bmc-info --no-probing --driver-type=SSIF --driver-address=0x10 --driver-device=/dev/i2c-2 Device ID : 20 Device Revision : 0 Device SDRs : supported Firmware Revision : 1.30 Device Available : yes (normal operation) IPMI Version : 2.0 Sensor Device : supported SDR Repository Device : unsupported SEL Device: supported FRU Inventory Device : supported IPMB Event Receiver : unsupported IPMB Event Generator : supported Bridge: unsupported Chassis Device: supported Manufacturer ID : Hewlett-Packard (11) Product ID: 8449 System Firmware Version : System Name : ProLiant m800 Server Cartridge Primary Operating System Name : Operating System Name : Channel Information Channel Number : 0 Medium Type : IPMB (I2C) Protocol Type: IPMB-1.0 Active Session Count : 0 Session Support : session-less Vendor ID: Intelligent Platform Management Interface forum (7154) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1324992 Title: freeipmi patch for HP moonshot ARM cartridges with I2c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1324992/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1324992] Re: freeipmi patch for HP moonshot ARM cartridges with I2c
** 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. https://bugs.launchpad.net/bugs/1324992 Title: freeipmi patch for HP moonshot ARM cartridges with I2c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1324992/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1331057] [NEW] Can't be used to verify current trusty images
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 http://cloud-images.ubuntu.com/trusty/current/SHA256SUMS http://cloud-images.ubuntu.com/trusty/current/SHA256SUMS.gpg ubuntu@server-46af3152-8a83-4995-8dfb-e3b2d07e0841:~$ gpg --verify SHA256SUMS.gpg SHA256SUMS gpg: Signature made Sat 14 Jun 2014 01:03:39 PM UTC using RSA key ID 7DB87C81 gpg: Can't check signature: public key not found ubuntu@server-46af3152-8a83-4995-8dfb-e3b2d07e0841:~$ gpg --keyring /usr/share/keyrings/ubuntu-cloudimage-keyring.gpg --list-keys/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg - pub 4096R/476CF100 2012-10-27 uid Ubuntu Cloud Image Builder (Canonical Internal Cloud Image Builder) ubuntu-cloudbuilder-nore...@canonical.com sub 4096R/9D817405 2012-10-27 ubuntu@server-46af3152-8a83-4995-8dfb-e3b2d07e0841:~$ dpkg -l ubuntu-cloudimage-keyring Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-p end |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==-==-= ii ubuntu-cloudimage-keyring 2013.11.11 allGnuPG keys of the Ubuntu Cloud Image builder ** Affects: ubuntu-cloudimage-keyring (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ubuntu-cloudimage-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1331057 Title: Can't be used to verify current trusty images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-cloudimage-keyring/+bug/1331057/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1324992] Re: freeipmi patch for HP moonshot ARM cartridges with I2c
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 Ubuntu. https://bugs.launchpad.net/bugs/1324992 Title: freeipmi patch for HP moonshot ARM cartridges with I2c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1324992/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1324992] Re: freeipmi patch for HP moonshot ARM cartridges with I2c
** 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 the BMC on ARM HP Moonshot
cartridges
+ [Test Case]
- Here are the details.
-
- svn://svn.savannah.gnu.org/freeipmi/trunk
-
- Revision: 10072
- Author: chu11
- Date: Friday, May 30, 2014 10:21:03 AM
- Message:
- Retry ssif reads as needed
-
- Modified : /trunk/ChangeLog
- Modified : /trunk/libfreeipmi/api/ipmi-ssif-driver-api.c
- Modified : /trunk/libfreeipmi/api/ipmi-ssif-driver-api.h
-
- I have attached the ChangeLog and patch file for your reference.
-
- -Original Message-
- From: Al Chu [mailto:ch...@llnl.gov]
- Sent: Friday, May 30, 2014 10:26 AM
- To: Dande, Shashi
- Cc: freeipmi-de...@gnu.org
- Subject: RE: FreeIPMI Patch Submission
-
- Great. It'll be in the next release of FreeIPMI (1.4.4)
-
- Al
-
- On Thu, 2014-05-29 at 23:32 +, Dande, Shashi wrote:
- Hi Al
-
- Here is the updated patch per our conversation today.
-
- Thanks
- Shashi
-
- Index: ipmi-ssif-driver-api.c
- ===
- --- ipmi-ssif-driver-api.c(revision 10066)
- +++ ipmi-ssif-driver-api.c(working copy)
- @@ -319,7 +319,9 @@
- uint8_t cmd = 0; /* used for debugging */
- uint8_t group_extension = 0; /* used for debugging */
- uint64_t val;
- -
- + struct timespec request, remain;
- + uint8_t retry = IPMI_SSIF_RETRY_DEFAULT;
- +
- assert (ctx
- ctx-magic == IPMI_CTX_MAGIC
- ctx-type == IPMI_DEVICE_SSIF
- @@ -350,9 +352,39 @@
- if (_ssif_cmd_write (ctx, cmd, group_extension, obj_cmd_rq) 0)
- return (-1);
-
- +
/**
- +12.9 SMBus NACKs and Error Recovery:
- +
- +The BMC can NACK the SMBus host controller if it is not ready to
accept a new
- +transaction. Typically, this will be exhibited by the BMC NACK'ing its
slave
- +address.
- +
- +If the BMC NACKs a single part transaction, software can simply retry
it.
- +If a 'middle' or 'end' transaction is NACK'd, software should not
retry the
- +particular but should restart the multi-part read or write from the
beginning
- +Start transaction for the transfer.
- +
- +
- + ***/
- if (_ssif_cmd_read (ctx, cmd, group_extension, obj_cmd_rs) 0)
- -return (-1);
- +{
- + while (1)
- +{
- + request.tv_sec = 0;
- + request.tv_nsec = IPMI_SSIF_TIMEOUT_DEFAULT;
- + if (nanosleep (request, remain) 0 )
- +return (-1);
-
- + if (_ssif_cmd_read (ctx, cmd, group_extension, obj_cmd_rs) 0)
- +{
- + if (retry == 0)
- +return (-1);
- +
- + retry--;
- +}
- +else
- + break;
- +}
- +}
- +
- return (0);
- }
-
- Index: ipmi-ssif-driver-api.h
- ===
- --- ipmi-ssif-driver-api.h(revision 10066)
- +++ ipmi-ssif-driver-api.h(working copy)
- @@ -23,6 +23,9 @@
- #include freeipmi/api/ipmi-api.h
- #include freeipmi/fiid/fiid.h
-
- +#define IPMI_SSIF_RETRY_DEFAULT 5
- +#define IPMI_SSIF_TIMEOUT_DEFAULT 2000 /* 20 ms */
- +
- int api_ssif_cmd (ipmi_ctx_t ctx,
- fiid_obj_t obj_cmd_rq,
- fiid_obj_t obj_cmd_rs);
+ [Regression Potential]
+ Should be minimal, given the new code only runs in a case that would've
previous resulted in a failure.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1324992
Title:
freeipmi patch for HP moonshot ARM cartridges with I2c
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1324992/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 908112] Re: #110992 still happens (modules are not loaded)
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 Title: #110992 still happens (modules are not loaded) To manage notifications about this bug go to: https://bugs.launchpad.net/eilt/+bug/908112/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1289178] Re: MAAS packages should also pull in the tools necessary for power control
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 notification in the UI that warns a user when the tools required for a certain power type are not installed. -- 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/1289178 Title: MAAS packages should also pull in the tools necessary for power control To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1289178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1289527] Re: qemu-aarch64-static: java dies with SIGILL
** 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 notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289527/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1289527] [NEW] qemu-aarch64-static: java dies with SIGILL
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 Environment: # # SIGILL (0x4) at pc=0x0040098e8070, pid=15034, tid=274902467056 # # JRE version: (7.0_51-b31) (build ) # Java VM: OpenJDK 64-Bit Server VM (25.0-b59 mixed mode linux-aarch64 compressed oops) # Problematic frame: # v ~BufferBlob::flush_icache_stub # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try ulimit -c unlimited before starting Java again # # An error report file with more information is saved as: # /home/dannf/hs_err_pid15034.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # qemu: uncaught target signal 6 (Aborted) - core dumped Aborted (core dumped) dannf@server-75e0210e-4f99-4c86-9277-3201ab7b6afd:~$ ** Affects: qemu (Ubuntu) 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1289527/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1285363] Re: qemu-aarch64-static segfaults
@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 manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1285363/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
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 Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1276909 Title: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1285363] Re: qemu-aarch64-static segfaults
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 appears to only be reproducible on systems with 1 CPU (easy to reproduce on 4). -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1285363/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
** 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. https://bugs.launchpad.net/bugs/1276909 Title: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1285363] [NEW] qemu-aarch64-static segfaults
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 included in suse's tree. 1) dh_fixperms is a script that commonly runs at the end of a package build. Its basically doing a `find | xargs chmod`. 2) debootstrap --second-stage This is used to configure an arm64 chroot that was built using debootstrap on a non-native host. It is basically invoking a bunch of shell scripts (postinst, etc). When it blows up, the stack consistently looks like this: Core was generated by `/usr/bin/qemu-aarch64-static /bin/sh -e /debootstrap/debootstrap --second-stage'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x60058e55 in memcpy (__len=8, __src=0x7fff62ae34e0, __dest=0x400082c330) at /usr/include/x86_64-linux-gnu/bits/string3.h:51 51 return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest)); (gdb) bt #0 0x60058e55 in memcpy (__len=8, __src=0x7fff62ae34e0, __dest=0x400082c330) at /usr/include/x86_64-linux-gnu/bits/string3.h:51 #1 stq_p (v=274886476624, ptr=0x400082c330) at /mnt/qemu.upstream/include/qemu/bswap.h:280 #2 stq_le_p (v=274886476624, ptr=0x400082c330) at /mnt/qemu.upstream/include/qemu/bswap.h:315 #3 target_setup_sigframe (set=0x7fff62ae3530, env=0x62d9c678, sf=0x400082b0d0) at /mnt/qemu.upstream/linux-user/signal.c:1167 #4 target_setup_frame (usig=usig@entry=17, ka=ka@entry=0x604ec1e0 sigact_table+512, info=info@entry=0x0, set=set@entry=0x7fff62ae3530, env=env@entry=0x62d9c678) at /mnt/qemu.upstream/linux-user/signal.c:1286 #5 0x60059f46 in setup_frame (env=0x62d9c678, set=0x7fff62ae3530, ka=0x604ec1e0 sigact_table+512, sig=17) at /mnt/qemu.upstream/linux-user/signal.c:1322 #6 process_pending_signals (cpu_env=cpu_env@entry=0x62d9c678) at /mnt/qemu.upstream/linux-user/signal.c:5747 #7 0x60056e60 in cpu_loop (env=env@entry=0x62d9c678) at /mnt/qemu.upstream/linux-user/main.c:1082 #8 0x60005079 in main (argc=optimized out, argv=optimized out, envp=optimized out) at /mnt/qemu.upstream/linux-user/main.c:4374 ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: hs-arm64 ** Patch added: qemu.debdiff https://bugs.launchpad.net/bugs/1285363/+attachment/3998337/+files/qemu.debdiff -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1285363/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
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: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
** 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 juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1276909 Title: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1284344] [NEW] qemu-user-aarch64: dns is broken
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: 269 qemu: Unsupported syscall: 269 qemu: Unsupported syscall: 269 qemu: Unsupported syscall: 269 qemu: Unsupported syscall: 269 Err http://ports.ubuntu.com trusty InRelease Err http://ports.ubuntu.com trusty Release.gpg Could not resolve 'ports.ubuntu.com' Reading package lists... Done W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/trusty/InRelease W: Failed to fetch http://ports.ubuntu.com/ubuntu- ports/dists/trusty/Release.gpg Could not resolve 'ports.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: hs-arm64 ** Patch added: qemu-implement-sendmmsg.debdiff https://bugs.launchpad.net/bugs/1284344/+attachment/3994978/+files/qemu-implement-sendmmsg.debdiff -- 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/1284344 Title: qemu-user-aarch64: dns is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284344/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1283279] [NEW] numactl binaries not built on arm64
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 Status: New ** Tags: hs-arm64 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to numactl in Ubuntu. https://bugs.launchpad.net/bugs/1283279 Title: numactl binaries not built on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1283279/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1283279] Re: numactl binaries not built on arm64
** 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 you are a member of Ubuntu Server Team, which is subscribed to numactl in Ubuntu. https://bugs.launchpad.net/bugs/1283279 Title: numactl binaries not built on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1283279/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1280666] [NEW] FTBFS on arm64; outdated config.{sub,guess}
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 make)
make[1]: Entering directory `/build/buildd/nis-3.17/yp-tools-2.9'
make[1]: *** No targets specified and no makefile found. Stop.
make[1]: Leaving directory `/build/buildd/nis-3.17/yp-tools-2.9'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
** Affects: nis (Ubuntu)
Importance: Undecided
Status: New
** Affects: nis (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #739059
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739059
** Also affects: nis (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739059
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/1280666
Title:
FTBFS on arm64; outdated config.{sub,guess}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1280666/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
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 isn't required that this match the dpkg arch - that isn't the case for ARM32 where juju calls it arm but the relevant corresponding dpkg arch is 'armhf'. -- 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: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
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 other way around ppc64 should map to ppc64el Apologies, there's a couple points of confusion here. To be explicit: uname -m returns: ppc64le, aarch64 dpkg uses: ppc64el, arm64 Yes, the le/el is transposed between the two ppc64 ones. Weird, I know. Yes, we said ppc64 above but I'm saying ppc64le now. This is because code inspection shows that juju is using 'uname -m' here in the script it passes to the manual provisioned hosts, and this wasn't clear when we asked a ppc64el/le porter about it. I explicitly asked our porter friend to run 'uname -m', and he confirmed it returns ppc64le. -- 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: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
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 w/ some access earlier this week - is this the same testing he works on? -- 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: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
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 you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1276909 Title: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276909] [NEW] error detecting hardware characteristics: unrecognised architecture: aarch64
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 +++-==---= un juju none none (no description available) dannf@trusty:~$ cat ~/.juju/environments.yaml default: manual environments: manual: type: manual bootstrap-host: bootstrap.dannf bootstrap-user: dannf dannf@trusty:~$ juju add-machine ssh:arm64.dannf ERROR error detecting hardware characteristics: unrecognised architecture: aarch64 dannf@trusty:~$ ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: hs-arm64 -- 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: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
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: [bootstrap.dannf:17070] 2014-02-06 06:12:54 INFO juju apiclient.go:118 state/api: dialing wss://bootstrap.dannf:17070/ 2014-02-06 06:12:54 INFO juju apiclient.go:128 state/api: connection established 2014-02-06 06:12:54 INFO juju.environs.manual init.go:156 initialising arm64.dannf, user 2014-02-06 06:12:54 INFO juju.environs.manual init.go:167 ubuntu user is already initialised 2014-02-06 06:12:54 INFO juju.environs.manual provisioner.go:260 addresses for arm64.dannf: [192.168.1.117 public:arm64.dannf] 2014-02-06 06:12:54 INFO juju.environs.manual init.go:29 Checking if arm64.dannf is already provisioned 2014-02-06 06:12:54 INFO juju.environs.manual init.go:46 arm64.dannf is not provisioned 2014-02-06 06:12:54 INFO juju.environs.manual init.go:55 Detecting series and characteristics on arm64.dannf 2014-02-06 06:12:54 INFO juju.environs.manual init.go:118 series: trusty, characteristics: arch=aarch64 cpu-cores=1 mem=16062M 2014-02-06 06:12:57 ERROR juju.cmd supercommand.go:294 no matching tools available ** Patch added: recognize-aarch64.patch https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1276909/+attachment/3970848/+files/recognize-aarch64.patch -- 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: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1261452] Re: juju-core is unavailable for arm64
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 Ubuntu. https://bugs.launchpad.net/bugs/1261452 Title: juju-core is unavailable for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1261452/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1261452] Re: juju-core is unavailable for arm64
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 Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1261452 Title: juju-core is unavailable for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1261452/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1261452] [NEW] juju-core is unavailable for arm64
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) Importance: Undecided Status: New ** Also affects: mongodb (Ubuntu) Importance: Undecided Status: New ** Also affects: libv8 (Ubuntu) Importance: Undecided Status: New -- 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/1261452 Title: juju-core is unavailable for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1261452/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1261452] Re: juju-core is unavailable for arm64
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. https://bugs.launchpad.net/bugs/1261452 Title: juju-core is unavailable for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1261452/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1257082] Re: MAAS does not use NTP servers specified in DHCPD options
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 attempt this?
I think you need to edit /usr/share/maas/preseeds/generic. Find the
preseed/late_command section.
Then, just before the final true, add another command with :
in-target sed -i 's/NTPDATE_USE_NTP_CONF=yes/NTPDATE_USE_NTP_CONF=no/'
/etc/default/ntpdate
BEFORE:
{{def post_scripts}}
# Executes late command and disables PXE.
d-i preseed/late_command string true \
in-target sh -c 'f=$1; shift; echo $0 $f chmod 0440 $f $*'
'ubuntu ALL=(ALL) NOPASSWD: ALL' /etc/sudoers.d/maas \
in-target wget --no-proxy {{node_disable_pxe_url|escape.shell}}
--post-data {{node_disable_pxe_data|escape.shell}} -O /dev/null \
true
{{enddef}}
AFTER:
{{def post_scripts}}
# Executes late command and disables PXE.
d-i preseed/late_command string true \
in-target sh -c 'f=$1; shift; echo $0 $f chmod 0440 $f $*'
'ubuntu ALL=(ALL) NOPASSWD: ALL' /etc/sudoers.d/maas \
in-target wget --no-proxy {{node_disable_pxe_url|escape.shell}}
--post-data {{node_disable_pxe_data|escape.shell}} -O /dev/null \
in-target sed -i
's/NTPDATE_USE_NTP_CONF=yes/NTPDATE_USE_NTP_CONF=no/'
/etc/default/ntpdate \
true
{{enddef}}
Will this mean all newly-deployed MAAS nodes get
this change?
Yup.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1257082
Title:
MAAS does not use NTP servers specified in DHCPD options
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1257082/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
