[Bug 54680] Re: Dual Head gives square cursor (or "SWCursor" crashes gnome)

[Louis Bouchard]

Hi,

I have started to experience this "big square cursor" on the second head
since upgrading to Gutsy on the new HP Compaq 6910p (Radeon X2300) when
I installed the xorg-driver-fglrx  package. I didn't have this problem
with the original driver.

It appears that upgrading to the Proprietary ATI driver fglrx  (8.40.4
available here http://ati.amd.com/support/drivers/linux/linux-
radeon.html) fixes the issue.

Just thought you might want to know.

Regards,

...Louis

-- 
Dual Head gives square cursor (or "SWCursor" crashes gnome)
https://bugs.launchpad.net/bugs/54680
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915509] Re: QEMU 1:4.2-3ubuntu6.12 : Unable to start SEV enabled VM using virtio driver

[Louis Bouchard]

Hello,
After much digging and searching the internet, I have found what needs to be 
used to get IOMMU enabled and, hence start a SEV vm using VIRTIO :

  -device 
virtio-blk-pci,drive=drive0,id=virblk0,num-queues=4,disable-modern=off,disable-legacy=on,iommu_platform=on
 \
  -drive file=/var/lib/libvirt/images/real-qemu.qcow2,if=none,id=drive0 \

The addition of disable-modern=off,disable-legacy=on does the trick !

Thanks for your suggestions.

...Louis

** Changed in: qemu (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915509

Title:
  QEMU 1:4.2-3ubuntu6.12 : Unable to start SEV enabled VM using virtio
  driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1915509/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929255] Re: update-initrd-links creates incorrect symlinks

[Louis Bouchard]

** Also affects: linux-base (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929255

Title:
  update-initrd-links creates incorrect symlinks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880522] Re: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

[Louis Bouchard]

Hello,
Sorry to switch this bug back to Confirmed, but the fix that you mention is 
clearly not present in the latest kernel available in Focal :

root@launchpad-kernel:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename:   focal
root@launchpad-kernel:~# uname -a
Linux launchpad-kernel 5.4.0-1030-kvm #31-Ubuntu SMP Wed Dec 9 17:27:05 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
root@launchpad-kernel:~# grep IP_VS /boot/config-5.4.0-1030-kvm
# CONFIG_IP_VS is not set
root@launchpad-kernel:~# modprobe ip_vs
modprobe: FATAL: Module ip_vs not found in directory /lib/modules/5.4.0-1030-kvm

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880522

Title:
  CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1880522/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880522] Re: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

[Louis Bouchard]

Hello again,

Sorry for the noise, I blindly reported what one of our user told me
without checking. Its problem is IP_VS which has nothing to do with this
bug.

Thanks for your help in fixing this and, once again sorry.

...Louis

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880522

Title:
  CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1880522/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863866] [NEW] tinc missing net-tools dependency for Bionic onward

[Louis Bouchard]

Public bug reported:

net-tools is not installed by default on Bionic and after. tinc expects
ifconfig to be available so it should depends on net-tools

** Affects: tinc (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863866

Title:
  tinc missing net-tools dependency for Bionic onward

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tinc/+bug/1863866/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1286882] Re: libapache2-mpm-itk postinst failed

[Louis Bouchard]

** Changed in: apache2 (Ubuntu Trusty)
 Assignee: Louis Bouchard (louis-bouchard) => (unassigned)

** Changed in: mpm-itk (Ubuntu Trusty)
 Assignee: Louis Bouchard (louis-bouchard) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1286882

Title:
  libapache2-mpm-itk postinst failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1286882/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1596599] [NEW] Full disk encryption passphrase is using wrong locale

[Louis Bouchard]

Public bug reported:

When installing from the Xenial 16.04 media (amd64), if the language
selected at the first step (before Ubiquity kicks in) is english and is
then changed to another language (french in this situation), the whole
installation process will proceed in french, all text entered in the
field will be french, but the passphrase entered for the full disk
encryption will be keyed in using the initial language, i.e. english.

If the user enters Canonical in the field, the value fowarded to Luks to
create the passphrase will be Cqnonicql even though the rest of the
typed text will be entered correctly.

This has the ackward result of blocking the boot sequence after
installation unless the selected passphrase only has letters that do not
change position depending on the locale. Entering the english-localized
letters allow the user to boot correctly.

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubiquity (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Also affects: ubiquity (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596599

Title:
  Full disk encryption passphrase is using wrong locale

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1596599/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1596599] Re: Full disk encryption passphrase is using wrong locale

[Louis Bouchard]

** Description changed:

  When installing from the Xenial 16.04 media (amd64), if the language
  selected at the first step (before Ubiquity kicks in) is english and is
  then changed to another language (french in this situation), the whole
  installation process will proceed in french, all text entered in the
  field will be french, but the passphrase entered for the full disk
  encryption will be keyed in using the initial language, i.e. english.
  
  If the user enters Canonical in the field, the value fowarded to Luks to
  create the passphrase will be Cqnonicql even though the rest of the
  typed text will be entered correctly.
  
  This has the ackward result of blocking the boot sequence after
  installation unless the selected passphrase only has letters that do not
  change position depending on the locale. Entering the english-localized
  letters allow the user to boot correctly.
+ 
+ How to reproduce :
+ ==
+ 
+ Install using the 16.04 iso
+ Select english at the very first menu selection where this is displayed :
+ 
+  Try Ubuntu without installing
+ Install Ubuntu
+ Check disk for defects
+  Test memory
+   Boot from first hard disk
+ 
+ Then choose "Install Ubuntu"
+ 
+ In the Welcome section of Ubiquity (graphical installer), change the
+ language to french and proceed with a normal installation and select LVM
+ and full disk encryption
+ 
+ Use aAa as the full disk encryption passphrase
+ 
+ After reboot, using aAa as the passphrase will not unlock the boot disk.
+ qQq must be used.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596599

Title:
  Full disk encryption passphrase is using wrong locale

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1596599/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1596599] Re: Full disk encryption passphrase is using wrong locale

[Louis Bouchard]

Here is the installation log produced with DEBCONF_DEBUG=developer &
ubiquity-debug passed as kernel parameters.

** Attachment added: "installer-log.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1596599/+attachment/4692146/+files/installer-log.tgz

** Changed in: ubiquity (Ubuntu Xenial)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596599

Title:
  Full disk encryption passphrase is using wrong locale

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1596599/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570775] Re: makekdump should re-exec with cio_ignore on s390x

[Louis Bouchard]

Hello,

I don't know where you are getting these packages from :

~$ rmadison makedumpfile
 makedumpfile | 1:1.5.9-5   | xenial   | source, amd64, 
armhf, i386, powerpc, ppc64el, s390x
 makedumpfile | 1:1.6.0-1   | yakkety  | source, amd64, 
armhf, i386, powerpc, ppc64el, s390x
$ rmadison kexec-tools
 kexec-tools | 1:2.0.10-1ubuntu2  | xenial  | source, amd64, armhf, 
i386, powerpc, ppc64el, s390x
 kexec-tools | 1:2.0.10-2ubuntu1  | yakkety | source, amd64, armhf, 
i386, powerpc, ppc64el, s390x
caribou@marvin:~$ 

Xenial has makedumpfile | 1:1.5.9-5 and kexec-tools | 1:2.0.10-1ubuntu2.

This change (along with a few more enablements) will have to be SRUed to
Xenial. But this doesn't change the fact that the versions in the
archive do install correctly.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570775

Title:
  makekdump should re-exec with cio_ignore on s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1570775/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

[Louis Bouchard]

Ok, I'll have a look at it; I only backported the Eoan fix to Bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805183

Title:
  systemd-resolved constantly restarts on Bionic upgraded from Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1837869] Re: Cannot complete snapshot if read-only backing store is opened by another VM

[Louis Bouchard]

Hi,
Sorry, I'm off on vacation until August 12th. Will look at this once I'm
back

...Louis

Le mer. 31 juil. 2019 à 09:05, Christian Ehrhardt  <
1837...@bugs.launchpad.net> a écrit :

> Hrm, that didn't help.
> Now I can't even start the guests anymore:
>   root@b:~# qemu-system-x86_64: -drive
> file=./top-vm02.img,if=virtio,id=disk0: Failed to get "write" lock
>
> It seems I too blindly picked out of context for this :-/.
> But I also don't have a lot of time for this right now.
> Maybe I should just start bisecting it in the background ...
>
> Let me know if you have identified anything quicker than me.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1837869
>
> Title:
>   Cannot complete snapshot if read-only backing store is opened by
>   another VM
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1837869/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837869

Title:
  Cannot complete snapshot if read-only backing store is opened by
  another VM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1837869/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1852766] [NEW] Attaching RBD device after qemu upgrade fails with "Unknown protocol 'rbd'"

[Louis Bouchard]

Public bug reported:

After upgrading the following QEMU packages to latest Bionic version
(1:2.11+dfsg-1ubuntu7.20) :

- qemu-system-x86
- qemu-system-common
- qemu-utils
- qemu-block-extra:amd64

Attaching an RBD device to a VM that was running prior to the upgrade
fails with

"Unknown protocol 'rbd'

This only happens if this is the first RBD device to be attached after
the upgrade. Attaching a device, then upgrading to 1:2.11+dfsg-
1ubuntu7.20 will not generate the error message and the device will
attach correctly.

Attaching a device to a new VM created _AFTER_ the upgrade does not
trigger the problem either.

Downgrading qemu-block-extra:amd64 after the upgrade and prior to first
attaching an RBD device will also not trigger the error.

Here are two examples :
Using :
ii  qemu-block-extra:amd641:2.11+dfsg-1ubuntu7
ii  qemu-system-common1:2.11+dfsg-1ubuntu7
ii  qemu-system-x86   1:2.11+dfsg-1ubuntu7
ii  qemu-utils1:2.11+dfsg-1ubuntu7
./qmp-shell -H /opt/vms/1/qmp.sock
(QEMU) drive_add auto 
format=raw,cache=writeback,file=rbd:rbd/disk-086264fd-9ca4-42a9-9deb-4a8be80f2bab:rbd_cache=true:id=compute-hv:conf=/etc/ceph/ceph.conf:keyring=/etc/ceph/ceph.client.compute-hv.keyring,id=volume-8b84f816-6e11-4a17-a2ce-0cdb6f486bfe,throttling.iops-total=1,if=none
OK

With :
ii  qemu-block-extra:amd641:2.11+dfsg-1ubuntu7
ii  qemu-system-common1:2.11+dfsg-1ubuntu7
ii  qemu-system-x86   1:2.11+dfsg-1ubuntu7
ii  qemu-utils1:2.11+dfsg-1ubuntu7

and an existing QEMU process running

$ apt udpate && apt -y install qemu-utils qemu-system-x86 qemu-system-common 
qemu-block-extra:amd64
Using :
ii  qemu-block-extra:amd641:2.11+dfsg-1ubuntu7.20
ii  qemu-system-common1:2.11+dfsg-1ubuntu7.20
ii  qemu-system-x86   1:2.11+dfsg-1ubuntu7.20
ii  qemu-utils1:2.11+dfsg-1ubuntu7.20

./qmp-shell -H /opt/vms/1/qmp.sock
(QEMU) drive_add auto 
format=raw,cache=writeback,file=rbd:rbd/disk-086264fd-9ca4-42a9-9deb-4a8be80f2bab:rbd_cache=true:id=compute-hv:conf=/etc/ceph/ceph.conf:keyring=/etc/ceph/ceph.client.compute-hv.keyring,id=volume-8b84f816-6e11-4a17-a2ce-0cdb6f486bfe,throttling.iops-total=1,if=none
Unknown protocol 'rbd'
(QEMU)

Restarting the QEMU process fixes the issue.

** Affects: qemu (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: qemu (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed

** Also affects: qemu (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: qemu (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: qemu (Ubuntu Bionic)
   Importance: Undecided => Medium

** Description changed:

  After upgrading the following QEMU packages to latest Bionic version
  (1:2.11+dfsg-1ubuntu7.20) :
  
  - qemu-system-x86
  - qemu-system-common
  - qemu-utils
  - qemu-block-extra:amd64
  
  Attaching an RBD device to a VM that was running prior to the upgrade
  fails with
  
  "Unknown protocol 'rbd'
  
  This only happens if this is the first RBD device to be attached after
  the upgrade. Attaching a device, then upgrading to 1:2.11+dfsg-
  1ubuntu7.20 will not generate the error message and the device will
  attach correctly.
  
  Attaching a device to a new VM created _AFTER_ the upgrade does not
  trigger the problem either.
  
  Downgrading qemu-block-extra:amd64 after the upgrade and prior to first
  attaching an RBD device will also not trigger the error.
  
  Here are two examples :
  Using :
  ii  qemu-block-extra:amd641:2.11+dfsg-1ubuntu7
  ii  qemu-system-common1:2.11+dfsg-1ubuntu7
  ii  qemu-system-x86   1:2.11+dfsg-1ubuntu7
  ii  qemu-utils1:2.11+dfsg-1ubuntu7
  ./qmp-shell -H /opt/vms/1/qmp.sock
  (QEMU) drive_add auto 
format=raw,cache=writeback,file=rbd:rbd/disk-086264fd-9ca4-42a9-9deb-4a8be80f2bab:rbd_cache=true:id=compute-hv:conf=/etc/ceph/ceph.conf:keyring=/etc/ceph/ceph.client.compute-hv.keyring,id=volume-8b84f816-6e11-4a17-a2ce-0cdb6f486bfe,throttling.iops-total=1,if=none
  OK
  
- 
  With :
  ii  qemu-block-extra:amd641:2.11+dfsg-1ubuntu7
  ii  qemu-system-common1:2.11+dfsg-1ubuntu7
  ii  qemu-system-x86   1:2.11+dfsg-1ubuntu7
  ii  qemu-utils1:2.11+dfsg-1ubuntu7
  
  and an existing QEMU process running
  
  $ apt udpate && apt -y install qemu-utils qemu-system-x86 qemu-system-common 
qemu-block-extra:amd64
  Using :
  ii  qemu-block-extra:amd641:2.11+dfsg-1ubuntu7.20
  ii  qemu-system-common1:2.11+dfsg-1ubuntu7.20
  ii  qemu-system-x86   1:2.11+dfsg-1ubuntu7.20
  ii  qemu-utils1:2.11+dfsg-1ubuntu7.20
  
  ./qmp-shell -H /opt/vms/1/

[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules

[Louis Bouchard]

Hello,

Nice to see so many known and friendly faces around this bug. Let me
outline a *real life* issue that we're facing following this issue.

We've put block storage in private beta a while ago
(https://www.scaleway.com/fr/betas/#block-storage) based on RBD storage.

The same platform experienced another QEMU issue (LPl #1837869) kindly
fixed and SRU by @paelzer) that we deployed on the same platform this
week. So all the instances currently running that have NOT used RBD
based storage during the BETA but will still be running when we go live
and want to use RBD storage when it goes GA will experience this bug
unless they reboot their instance.

We're looking into a workaround solution to alleviate this situation but
I thought I'd share the context to give a some kind of "real life"
experience :-)

Kind regards,

Louis (aka caribou) ;-)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847361

Title:
  Upgrade of qemu binaries causes running instances not able to
  dynamically load modules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1635463] Re: pip freeze includes "pkg-resources==0.0.0"

[Louis Bouchard]

Hello,

for what it's worth, the problem comes from the debianized version of
virtualenv which uses a debundled version of pkg_resource which gets
added into the virtualenv at creation time :

$ virtualenv .
Running virtualenv with interpreter /usr/bin/python2
New python executable in /home/caribou/git/quividi/test/bin/python2
Also creating executable in /home/caribou/git/quividi/test/bin/python
Installing setuptools, pkg_resources, pip, wheel...done.
$ pip freeze
pkg-resources==0.0.0

Using the pip installed version of virtualenv can be a workable
workaround :

$ sudo apt -y purge python3-virtualenv virtualenv tox
$ pip install virtualenv
$ virtualenv .
pip install virtualenv
Collecting virtualenv
  Downloading 
https://files.pythonhosted.org/packages/c5/97/00dd42a0fc41e9016b23f07ec7f657f636cb672fad9cf72b80f8f65c6a46/virtualenv-16.7.7-py2.py3-none-any.whl
 (3.4MB)
100% || 3.4MB 351kB/s 
Installing collected packages: virtualenv
Successfully installed virtualenv-16.7.7
$ virtualenv .
New python executable in /home/caribou/git/quividi/test/bin/python
Installing setuptools, pip, wheel...
done.
$ source bin/activate
$ pip freeze
$

hth,
...Louis

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1635463

Title:
  pip freeze includes "pkg-resources==0.0.0"

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1635463/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1837869] Re: Cannot complete snapshot if read-only backing store is opened by another VM

[Louis Bouchard]

As discussed offline, a new round of test confirms that the fix in your
PPA fixes the File Lock issue.

** Changed in: qemu (Ubuntu Bionic)
   Status: Incomplete => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837869

Title:
  Cannot complete snapshot if read-only backing store is opened by
  another VM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1837869/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845619] [NEW] Please backport bugfix for Debian Bug 838503 : mdadm should not start syncing RAID1 arrays at full speed during installation

[Louis Bouchard]

Public bug reported:

Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838503
fixes slow installation caused by RAID synchronization.

This is fixed in DISCO and EOAN already.

** Affects: partman-md (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: partman-md (Ubuntu Bionic)
 Importance: Medium
 Assignee: Louis Bouchard (louis)
 Status: Confirmed

** Affects: partman-md (Ubuntu Disco)
 Importance: Undecided
 Status: Fix Released

** Affects: partman-md (Ubuntu Eoan)
 Importance: Undecided
 Status: Fix Released

** Also affects: partman-md (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: partman-md (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: partman-md (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: partman-md (Ubuntu Disco)
   Status: New => Fix Released

** Changed in: partman-md (Ubuntu Eoan)
   Status: New => Fix Released

** Changed in: partman-md (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: partman-md (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: partman-md (Ubuntu Bionic)
 Assignee: (unassigned) => Louis Bouchard (louis)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845619

Title:
  Please backport bugfix for Debian Bug 838503 : mdadm should not start
  syncing RAID1 arrays at full speed during installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-md/+bug/1845619/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915509] [NEW] QEMU 1:4.2-3ubuntu6.12 : Unable to start SEV enabled VM using virtio driver

[Louis Bouchard]

Public bug reported:

When using the VIRTIO driver, starting a VM with SEV enabled on sev
enabled hardware fails. The situation may be tested with the following
commands :

$ dd if=/dev/urandom of=/tmp/sev_key.aes bs=8 count=4
$ cp /usr/share/OVMF/OVMF_CODE.fd /tmp
$ cp /usr/share/OVMF/OVMF_VARS.fd /tmp
$ qemu-system-x86_64 -name real-qemu \
-machine 
pc-q35-3.0,accel=kvm,usb=off,vmport=off,dump-guest-core=off,memory-encryption=sev0
 \
-display none \
-monitor none \
-nographic \
-nodefaults \
-m 16384.0M \
-serial mon:stdio \
-smp 2 \
-cpu host \
-device sga \
-device 
pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2
 \
-netdev user,id=net0,net=192.168.100.0/24,dhcpstart=192.168.100.1 \
-device 
virtio-net-pci,netdev=net0,id=net0,mac=52:54:00:cc:56:90,bus=pci.1,addr=0x0,romfile=,iommu_platform=on
 \
-drive if=pflash,format=raw,readonly,file=/tmp/OVMF_CODE.fd \
-drive if=pflash,format=raw,file=/tmp/OVMF_VARS.fd \
-drive file=/var/lib/libvirt/images/real-qemu.qcow2,if=virtio,id=disk0 \
-object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1,policy=0x3 \
-object secret,id=masterKey0,format=raw,file=/tmp/sev_key.aes

The output when starting the VM shows :
qemu-system-x86_64: Guest says index 53230 is available

When running the same script using the 'ide' driver instead of the
'virtio' driver, the VM starts correctly :

root@ubuntu:~# dmesg | grep -i sev
[0.243361] AMD Secure Encrypted Virtualization (SEV) active


There is a mention in the libvirt knowledge base documentation about the 
requirement to use IOMMU to make the virtio work 
(https://libvirt.org/kbase/launch_security_sev.html#virtio) so another test was 
to enable IOMMU :

$ qemu-system-x86_64 -name real-qemu \
  -machine 
pc-q35-3.0,accel=kvm,usb=off,vmport=off,dump-guest-core=off,memory-encryption=sev0
 \
  -display none \
  -monitor none \
  -nographic \
  -nodefaults \
  -m 16384.0M \
  -serial mon:stdio \
  -smp 2 \
  -cpu host \
  -device sga \
  -device 
pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2
 \
  -netdev user,id=net0,net=192.168.100.0/24,dhcpstart=192.168.100.1 \
  -device 
virtio-net-pci,netdev=net0,id=net0,mac=52:54:00:cc:56:90,bus=pci.1,addr=0x0,romfile=,iommu_platform=on
 \
  -drive if=pflash,format=raw,readonly,file=/tmp/OVMF_CODE.fd \
  -drive if=pflash,format=raw,file=/tmp/OVMF_VARS.fd \
  -device virtio-blk-pci,drive=drive0,id=virblk0,num-queues=4,iommu_platform=on 
\
  -drive file=/var/lib/libvirt/images/real-qemu.qcow2,if=none,id=drive0 \
  -object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1,policy=0x3 \
  -object secret,id=masterKey0,format=raw,file=/tmp/sev_key.aes

This also fails and issues the following error message :
qemu-system-x86_64: -device 
virtio-blk-pci,drive=drive0,id=virblk0,num-queues=4,iommu_platform=on: 
VIRTIO_F_IOMMU_PLATFORM was supported by neither legacy nor transitional device

Is it possible to use SEV in conjunction with the VIRTIO driver ?

** Affects: qemu (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915509

Title:
  QEMU 1:4.2-3ubuntu6.12 : Unable to start SEV enabled VM using virtio
  driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1915509/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880522] [NEW] CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

[Louis Bouchard]

Public bug reported:

The NF_TABLES options are not included in the -kvm flavor of the 5.4
kernel. This package is used in the Ubuntu Cloud Image.

The linux-image-5.4.0-31-generic package has the options present in the
config file.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880522

Title:
  CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880522/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880522] Re: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

[Louis Bouchard]

Hello Stefan,

Any hint on who could check on that ? What needs to be clarified is if
this is a requirement and there to stay or not.

Kind regards,

...Louis

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880522

Title:
  CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1880522/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873809] Re: Make linux-kvm bootable in LXD VMs

[Louis Bouchard]

Hello,
thanks for the quick turnaround.

For the record, some EFI configs did exist in prior 5.3 images :

root@focal:/boot# cat /etc/cloud/build.info
build_name: server
serial: 20200223
root@focal:/boot# uname -r
5.3.0-1009-kvm
root@focal:/boot# grep -i ^CONFIG_EFI config-5.3.0-1009-kvm 
CONFIG_EFI=y
CONFIG_EFI_VARS=y
CONFIG_EFI_ESRT=y
CONFIG_EFI_RUNTIME_WRAPPERS=y
CONFIG_EFI_EARLYCON=y
CONFIG_EFI_PARTITION=y
CONFIG_EFIVAR_FS=m

I'll be using the other image for testing in the meantime
...Louis

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873809

Title:
  Make linux-kvm bootable in LXD VMs

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-bl-tutorials/+bug/1873809/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873809] Re: Make linux-kvm bootable in LXD VMs

[Louis Bouchard]

Hello,

Just tested the latest image in ./current and it boots fine :

root@focal-ok:~# uname -a
Linux focal-ok 5.4.0-1009-kvm #9-Ubuntu SMP Mon Apr 20 20:23:56 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux
root@focal-ok:~# cat /etc/cloud/build.info
build_name: server
serial: 20200421
root@focal-ok:~# uname -r
5.4.0-1009-kvm
root@focal-ok:~# grep -i ^CONFIG_EFI /boot/config-5.4.0-1009-kvm 
CONFIG_EFI=y
CONFIG_EFI_STUB=y
CONFIG_EFI_MIXED=y
CONFIG_EFI_VARS=y
CONFIG_EFI_ESRT=y
CONFIG_EFI_RUNTIME_WRAPPERS=y
CONFIG_EFI_EARLYCON=y
CONFIG_EFI_PARTITION=y
CONFIG_EFIVAR_FS=m

Thanks for the quick turnaround !
...Louis

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873809

Title:
  Make linux-kvm bootable in LXD VMs

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1873809/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found

[Louis Bouchard]

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-base (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820755

Title:
  Netboot install fails due to linux-image-4.4.0-143-generic.postinst
  linux-update-symlinks not found

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1491894] Re: lucid to precise to trusty upgrade may leave system unbootable

[Louis Bouchard]

** Changed in: grub2 (Ubuntu)
 Assignee: Louis Bouchard (louis) => (unassigned)

** Changed in: grub2 (Ubuntu Trusty)
 Assignee: Louis Bouchard (louis) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491894

Title:
  lucid to precise to trusty upgrade may leave system unbootable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1491894/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1434991] Re: python attributeError 'SSLTimeoutError' after upgrade

[Louis Bouchard]

** Changed in: pywbem (Ubuntu)
 Assignee: Louis Bouchard (louis) => (unassigned)

** Changed in: pywbem (Ubuntu Trusty)
 Assignee: Louis Bouchard (louis) => (unassigned)

** Changed in: pywbem (Ubuntu Utopic)
 Assignee: Louis Bouchard (louis) => (unassigned)

** Changed in: pywbem (Ubuntu Vivid)
 Assignee: Louis Bouchard (louis) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434991

Title:
  python attributeError 'SSLTimeoutError' after upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pywbem/+bug/1434991/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1506550] Re: quassel can't play audio notifications in wily

[Louis Bouchard]

** Changed in: quassel (Ubuntu)
 Assignee: Louis Bouchard (louis) => (unassigned)

** Changed in: quassel (Ubuntu Wily)
 Assignee: Louis Bouchard (louis) => (unassigned)

** Changed in: quassel (Ubuntu Xenial)
 Assignee: Louis Bouchard (louis) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506550

Title:
  quassel can't play audio notifications in wily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1506550/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1447695] Re: sosreport 3.2 does not collect systemd information

[Louis Bouchard]

** Changed in: sosreport (Ubuntu Trusty)
 Assignee: Louis Bouchard (louis) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447695

Title:
  sosreport 3.2 does not collect systemd information

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1447695/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1834505] Re: Random kernel panics in QEMU instances when running on EPYC architecture

[Louis Bouchard]

** Description changed:

  We have been seeing many kernel panic in QEMU instances on newly
  deployed servers all running on the EPYC architecture. Many of the KP
  occur early after the start of the QEMU process or within a few hours.
+ 
+ All the servers are running an up to date Bionic. After the first few
+ panics on 4.15 kernels, we upgraded to 4.18 and still had panics.
  
  The only thing running on the underlying server is QEMU processes. Here
  is a typical backtrace of a kernel panic :
  
  [58034.598930] BUG: unable to handle kernel paging request at 943276c49f64
  [58034.612039] PGD 8363067 P4D 8363067 PUD 8367067 PMD 759ac063 PTE 
800076c49163
  [58034.612992] Oops:  [#1] SMP NOPTI
  [58034.613462] CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 
4.18.0-20-generic #21~18.04.1-Ubuntu
  [58034.614685] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), 
BIOS 0.0.0 02/06/2015
  [58034.615803] RIP: 0010:sched_ttwu_pending+0x6b/0xe0
  [58034.616385] Code: 4b a1 93 00 41 83 a4 24 98 09 00 00 03 4c 89 e7 48 89 45 
d8 c7 45 e0 00 00 00 00 e8 ef ca ff ff 48 8d 73 d0 48 83 fe d0 74 2c <0f> b6 96 
64 08 00 00 48 8b 46 30 48 8d 4d d8 4c 89 e7 48 8d 5>
  [58034.618537] RSP: 0018:94327f803f90 EFLAGS: 00010087
  [58034.619134] RAX: 34c83ba48a83 RBX: 943276c49730 RCX: 

  [58034.619992] RDX: 2a12 RSI: 943276c49700 RDI: 
94327fe3e000
  [58034.620913] RBP: 94327f803fb8 R08: 3753c7b87c93 R09: 

  [58034.621835] R10:  R11:  R12: 
94327f822c00
  [58034.622723] R13:  R14:  R15: 

  [58034.623539] FS:  () GS:94327f80() 
knlGS:
  [58034.624513] CS:  0010 DS:  ES:  CR0: 80050033
  [58034.625214] CR2: 943276c49f64 CR3: 76544000 CR4: 
003406f0
  [58034.626268] Call Trace:
  [58034.626605]  
  [58034.626924]  scheduler_ipi+0xa9/0x130
  [58034.627400]  smp_reschedule_interrupt+0x39/0xe0
  [58034.627925]  reschedule_interrupt+0xf/0x20
  [58034.628398]  
  [58034.628659] RIP: 0010:rcu_idle_exit+0x40/0x70
  [58034.629181] Code: fa 66 0f 1f 44 00 00 48 c7 c3 80 a6 01 00 65 48 03 1d ec 
4b 50 4e 48 8b 03 48 85 c0 74 16 48 83 c0 01 48 89 03 4c 89 e7 57 9d <0f> 1f 44 
00 00 5b 41 5c 5d c3 e8 a1 c6 ff ff 48 b8 00 00 00 0>
  [58034.631577] RSP: 0018:b2e03e48 EFLAGS: 0202 ORIG_RAX: 
ff02
  [58034.632566] RAX: 4000 RBX: 94327f81a680 RCX: 
94327f81a680
  [58034.633557] RDX:  RSI: 94327f81a680 RDI: 
0202
  [58034.634416] RBP: b2e03e58 R08: 0001cc00 R09: 
0001
  [58034.635292] R10: b2e03d98 R11:  R12: 
0202
  [58034.636107] R13:  R14:  R15: 
7e369c93
  [58034.637052]  do_idle+0x13f/0x280
  [58034.637453]  cpu_startup_entry+0x73/0x80
  [58034.638067]  rest_init+0xae/0xb0
  [58034.638506]  start_kernel+0x539/0x55a
  [58034.638938]  x86_64_start_reservations+0x24/0x26
  [58034.639470]  x86_64_start_kernel+0x74/0x77
  [58034.639958]  secondary_startup_64+0xa5/0xb0
  [58034.640441] Modules linked in: cfg80211 veth xt_nat xt_tcpudp 
ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_fi>
  
  None of the server has experienced any kernel panic itself.
  
  After analysing many of the crashes and seeing many of them handling
  interrupts, we decided to reboot the instances with the  noapic
  parameter.
  
  No kernel panic has been seen since but this is just a workaround until
  a solution is found.
  
  AMD has been informed of the issue.
  
  TIA,
  
  ...Louis (aka Caribou)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834505

Title:
  Random kernel panics in QEMU instances when running on EPYC
  architecture

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834505/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1834505] [NEW] Random kernel panics in QEMU instances when running on EPYC architecture

[Louis Bouchard]

Public bug reported:

We have been seeing many kernel panic in QEMU instances on newly
deployed servers all running on the EPYC architecture. Many of the KP
occur early after the start of the QEMU process or within a few hours.

All the servers are running an up to date Bionic. After the first few
panics on 4.15 kernels, we upgraded to 4.18 and still had panics.

The only thing running on the underlying server is QEMU processes. Here
is a typical backtrace of a kernel panic :

[58034.598930] BUG: unable to handle kernel paging request at 943276c49f64
[58034.612039] PGD 8363067 P4D 8363067 PUD 8367067 PMD 759ac063 PTE 
800076c49163
[58034.612992] Oops:  [#1] SMP NOPTI
[58034.613462] CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 
4.18.0-20-generic #21~18.04.1-Ubuntu
[58034.614685] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 
0.0.0 02/06/2015
[58034.615803] RIP: 0010:sched_ttwu_pending+0x6b/0xe0
[58034.616385] Code: 4b a1 93 00 41 83 a4 24 98 09 00 00 03 4c 89 e7 48 89 45 
d8 c7 45 e0 00 00 00 00 e8 ef ca ff ff 48 8d 73 d0 48 83 fe d0 74 2c <0f> b6 96 
64 08 00 00 48 8b 46 30 48 8d 4d d8 4c 89 e7 48 8d 5>
[58034.618537] RSP: 0018:94327f803f90 EFLAGS: 00010087
[58034.619134] RAX: 34c83ba48a83 RBX: 943276c49730 RCX: 
[58034.619992] RDX: 2a12 RSI: 943276c49700 RDI: 94327fe3e000
[58034.620913] RBP: 94327f803fb8 R08: 3753c7b87c93 R09: 
[58034.621835] R10:  R11:  R12: 94327f822c00
[58034.622723] R13:  R14:  R15: 
[58034.623539] FS:  () GS:94327f80() 
knlGS:
[58034.624513] CS:  0010 DS:  ES:  CR0: 80050033
[58034.625214] CR2: 943276c49f64 CR3: 76544000 CR4: 003406f0
[58034.626268] Call Trace:
[58034.626605]  
[58034.626924]  scheduler_ipi+0xa9/0x130
[58034.627400]  smp_reschedule_interrupt+0x39/0xe0
[58034.627925]  reschedule_interrupt+0xf/0x20
[58034.628398]  
[58034.628659] RIP: 0010:rcu_idle_exit+0x40/0x70
[58034.629181] Code: fa 66 0f 1f 44 00 00 48 c7 c3 80 a6 01 00 65 48 03 1d ec 
4b 50 4e 48 8b 03 48 85 c0 74 16 48 83 c0 01 48 89 03 4c 89 e7 57 9d <0f> 1f 44 
00 00 5b 41 5c 5d c3 e8 a1 c6 ff ff 48 b8 00 00 00 0>
[58034.631577] RSP: 0018:b2e03e48 EFLAGS: 0202 ORIG_RAX: 
ff02
[58034.632566] RAX: 4000 RBX: 94327f81a680 RCX: 94327f81a680
[58034.633557] RDX:  RSI: 94327f81a680 RDI: 0202
[58034.634416] RBP: b2e03e58 R08: 0001cc00 R09: 0001
[58034.635292] R10: b2e03d98 R11:  R12: 0202
[58034.636107] R13:  R14:  R15: 7e369c93
[58034.637052]  do_idle+0x13f/0x280
[58034.637453]  cpu_startup_entry+0x73/0x80
[58034.638067]  rest_init+0xae/0xb0
[58034.638506]  start_kernel+0x539/0x55a
[58034.638938]  x86_64_start_reservations+0x24/0x26
[58034.639470]  x86_64_start_kernel+0x74/0x77
[58034.639958]  secondary_startup_64+0xa5/0xb0
[58034.640441] Modules linked in: cfg80211 veth xt_nat xt_tcpudp ipt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_fi>

None of the server has experienced any kernel panic itself.

After analysing many of the crashes and seeing many of them handling
interrupts, we decided to reboot the instances with the  noapic
parameter.

No kernel panic has been seen since but this is just a workaround until
a solution is found.

AMD has been informed of the issue.

TIA,

...Louis (aka Caribou)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834505

Title:
  Random kernel panics in QEMU instances when running on EPYC
  architecture

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834505/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1834505] Re: Random kernel panics in QEMU instances when running on EPYC architecture

[Louis Bouchard]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: linux (Ubuntu)
   Status: Opinion => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834505

Title:
  Random kernel panics in QEMU instances when running on EPYC
  architecture

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834505/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

[Louis Bouchard]

** Changed in: systemd (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Louis Bouchard (louis)

** Changed in: systemd (Ubuntu Bionic)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805183

Title:
  systemd-resolved constantly restarts on Bionic upgraded from Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1662345] Re: smbios parameter settings not visible in guest

[Louis Bouchard]

Hello,
I have revived this bug and assigned myself to it.

It turns out that -smbios type=1,manufacturer=Scaleway is required by us
to trigger cloud-init's DataSourceScaleway on our infrastructure.

And, moreover, the functionality works as designed on Bionic :

# dmidecode | head
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Table at 0xBC03.

Handle 0x0100, DMI type 1, 27 bytes
System Information
Manufacturer: Scaleway
Product Name: KVM Virtual Machine
Version: 1.0
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename:   bionic
# arch
aarch64

So I am going to work on trying to identify what was added to version
1:2.11+dfsg-1ubuntu7.4 to make it work as expected.

** Changed in: qemu (Ubuntu)
   Importance: Wishlist => Medium

** Changed in: qemu (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis)

** Also affects: qemu (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: qemu (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: qemu (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: qemu (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: qemu (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: qemu (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: qemu (Ubuntu Xenial)
 Assignee: (unassigned) => Louis Bouchard (louis)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662345

Title:
  smbios parameter settings not visible in guest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1662345/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1775086] Re: cloud-init fails to recognize scaleway

[Louis Bouchard]

Hello,

Indeed, scw-generate-network-config does create a circular dependancy
hence systemd ends up shooting the cloud-init unit which breaks the
cloud-init.process.

We are in the process of implementing cloud-init on our platform. Please
keep yourself up to date, there should be some announcement soon.

Kind regards,

...Louis

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775086

Title:
  cloud-init fails to recognize scaleway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1775086/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.

[Louis Bouchard]

Hello,
For information, the current presence of kexec-tools in -proposed causes a 
dependency problem when installing the linux-crashdump meta-package :

# apt update
Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu xenial-security InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
11 packages can be upgraded. Run 'apt list --upgradable' to see them.
# apt install linux-crashdump
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-crashdump : Depends: kdump-tools but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

When adding the -proposed archive, linux-crashdump installs correctly.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743529

Title:
  Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic
  -not syncing: Out of memory message when crash is triggered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1743529/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1780817] [NEW] kernel panic in nested VM with latest 4.15 kernel (4.15.0-24-generic)

[Louis Bouchard]

Public bug reported:

When starting a nested VM in a Bionic VM, the "host" VM kernel panics
following a simple drop to QEMU monitor by hitting A-c. For some
reason kdump is unable to capture the kernel panic so I only have a
screen capture of the panic.

It also happens on the latest mainline kernel(4.18-rc4). It is fairly
trivial to reproduce. In a Bionic VM, install qemu & ovmf and run the
following :

qemu-system-x86_64 -enable-kvm \
-name balloontest \
-display none \
-monitor none \
-nographic \
-nodefaults \
-m 2048M \
-serial mon:stdio \
-smp 2 \
-cpu host \
-drive 
if=pflash,format=raw,readonly,file=/usr/share/OVMF/OVMF_CODE.fd \
-drive 
if=pflash,format=raw,file=/home/caribou/balloon/efi.vars

Use A-c to drop to QEMU monitor and .

^[]0;/opt/ocs/gotty-serial/nolp-cli^G^[]2;Loading...^G^[]2;avogadro^G[  
267.784299] general protection fault:  [#1] SMP PTI
[  267.785834] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo xt_addrtype ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter i>
[  267.804312]  xor raid6_pq libcrc32c raid1 raid0 multipath linear floppy 
aesni_intel pata_acpi aes_x86_64 crypto_simd cryptd glue_helper psmouse 
i2c_piix4 virtio_net virtio_blk
[  267.807946] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-24-generic 
#26-Ubuntu
[  267.809710] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 
0.0.0 02/06/2015
[  267.811666] RIP: 0010:native_write_cr4+0x4/0x10
[  267.812727] RSP: 0018:8c01ffd83f48 EFLAGS: 00010006
[  267.813960] RAX: 003626e0 RBX: 0046 RCX: 8c01ffd8
[  267.815582] RDX: 8c01ffd94020 RSI: 8c01ffda5040 RDI: 003606e0
[  267.817095] RBP: 8c01ffd83f48 R08: 00478079a547 R09: 
[  267.818625] R10:  R11:  R12: 00025040
[  267.820130] R13: 0001 R14:  R15: 
[  267.821638] FS:  () GS:8c01ffd8() 
knlGS:
[  267.823352] CS:  0010 DS:  ES:  CR0: 80050033
[  267.824592] CR2:  CR3: 00058c00a006 CR4: 003626e0
[  267.826108] DR0:  DR1:  DR2: 
[  267.827567] DR3:  DR6: fffe0ff0 DR7: 0400
[  267.828973] Call Trace:
[  267.829470]  
[  267.829893]  hardware_disable+0xaa/0xc0 [kvm_intel]
[  267.830897]  kvm_arch_hardware_disable+0x19/0x40 [kvm]
[  267.831928]  hardware_disable_nolock+0x2b/0x30 [kvm]
[  267.832912]  flush_smp_call_function_queue+0x4c/0xf0
[  267.833911]  generic_smp_call_function_single_interrupt+0x13/0x30
[  267.835121]  smp_call_function_interrupt+0x36/0xd0
[  267.836069]  call_function_interrupt+0x84/0x90
[  267.836950]  
[  267.837396] RIP: 0010:native_safe_halt+0x6/0x10
[  267.838272] RSP: 0018:a2e1431afe80 EFLAGS: 0246 ORIG_RAX: 
ff03
[  267.839698] RAX: acd97150 RBX: 0006 RCX: 
[  267.840978] RDX:  RSI:  RDI: 
[  267.842258] RBP: a2e1431afe80 R08: 0002 R09: 
[  267.843554] R10: 00b3 R11: 00a6 R12: 0006
[  267.844826] R13:  R14:  R15: 
[  267.846107]  ? __cpuidle_text_start+0x8/0x8
[  267.846875]  default_idle+0x20/0x100
[  267.847533]  arch_cpu_idle+0x15/0x20
[  267.848186]  default_idle_call+0x23/0x30
[  267.848917]  do_idle+0x172/0x1f0
[  267.849516]  cpu_startup_entry+0x73/0x80
[  267.850255]  start_secondary+0x1ab/0x200
[  267.850971]  secondary_startup_64+0xa5/0xb0
[  267.851700] Code: 0f 1f 80 00 00 00 00 55 48 89 e5 0f 20 d8 5d c3 0f 1f 80 
00 00 00 00 55 48 89 e5 0f 22 df 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 <0f> 22 
e7 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 44 0f 20 c0>
[  267.854894] RIP: native_write_cr4+0x4/0x10 RSP: 8c01ffd83f48
[  268.848104] invalid opcode:  [#2] SMP PTI
[  268.848524] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo xt_addrtype ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter i>
[  268.854013]  xor raid6_pq libcrc32c raid1 raid0 multipath linear floppy 
aesni_intel pata_acpi aes_x86_64 crypto_simd cryptd glue_helper psmouse 
i2c_piix4 virtio_net virtio_blk
[  268.855212] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-24-generic 
#26-Ubuntu
[  268.855790] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 
0.0.0 02/06/2015
[  268.856438] RIP: 0010:native_machine_crash_shutdown+0x136/0x190
[  268.856893] RSP: 0018:8c01ffd83cc0 EFLAGS: 00010002
[  268.857295] RAX: 0

[Bug 1780062] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels

[Louis Bouchard]

Hello,
I have noticed the same issue on our recently released scaleway images with 
cloud-init enabled on Bionic running 4.15.0-24.

Testing with the 4.15.0-26-generic kernel in -proposed _DOES_ fix the
delay issue on our image.

I'm taking the liberty of marking the bug tested.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780062

Title:
  Cloud-init causes potentially huge boot delays with 4.15 kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1780062/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

[Louis Bouchard]

Brief update to tell everyone that I have a fix ready for all stable
releases. I will update it to Artful soon and the SRU will follow soon.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654600

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

[Louis Bouchard]

Fixes to the debdiff look ok to me. Sponsored to Trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530837

Title:
  Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running
  corosync -v

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1530837/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1470167] Re: mstflint doesn't support Mellanox ConnectX-4 HCAs

[Louis Bouchard]

** Changed in: mstflint (Ubuntu Vivid)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: mstflint (Ubuntu Wily)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470167

Title:
  mstflint doesn't support Mellanox ConnectX-4 HCAs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/1470167/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1470167] Re: mstflint doesn't support Mellanox ConnectX-4 HCAs

[Louis Bouchard]

Thanks for the test.

I will work on getting it to Trusty & Wily. Vivid is now EOL

** Changed in: mstflint (Ubuntu Vivid)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470167

Title:
  mstflint doesn't support Mellanox ConnectX-4 HCAs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/1470167/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1555139] [NEW] needs a mstflint4 transitional package to allow for smooth upgrade from mstflint4

[Louis Bouchard]

Public bug reported:

Introduction of mstflint4 in Trusty & Wily required such a transitional
package to handle smooth upgrade

** Affects: mstflint (Ubuntu)
 Importance: Low
 Assignee: Louis Bouchard (louis-bouchard)
 Status: Confirmed

** Changed in: mstflint (Ubuntu)
   Status: New => Confirmed

** Changed in: mstflint (Ubuntu)
   Importance: Undecided => Low

** Changed in: mstflint (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555139

Title:
  needs a mstflint4 transitional package to allow for smooth upgrade
  from mstflint4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/1555139/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1555159] Re: Crashkernel parameter is not available

[Louis Bouchard]

Hi,

The crashkernel parameter is added when the "linux-crashdump"
metapackage is install.

linux-crashdump depends on kdump-tools which in turns depends on kexec-
tools.

Maybe this should be adapted to z as I don't know how the  linux kernel
is brought in and linux-crashdump is a metapackage of the linux kernel
package.

Kind regards,

...Louis

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555159

Title:
  Crashkernel parameter is not available

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1555159/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1555139] Re: needs a mstflint4 transitional package to allow for smooth upgrade from mstflint4

[Louis Bouchard]

The mstflint4 package has been introduced in Trusty & Wily to use the
latest mstflint version which is the only one working with recent
Mellanox adapters.

The upgrade path needs to be secured for people moving from trusty/Wily
to Xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555139

Title:
  needs a mstflint4 transitional package to allow for smooth upgrade
  from mstflint4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/1555139/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1555244] [NEW] crash fails to load with 4.4+ kernels

[Louis Bouchard]

Public bug reported:

When loading a crash dump on 4.4+ kernel, crash fails to load with the
following msg :

root@DEVAC02:/var/crash/201603092003# crash
/usr/lib/debug/boot/vmlinux-4.4.0-11-generic dump.201603092003

crash 7.1.4
Copyright (C) 2002-2015  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.
 
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu"...

please wait... (gathering module symbol data)   
crash: invalid structure member offset: module_core_size
   FILE: kernel.c  LINE: 3422  FUNCTION: module_init()

[/usr/bin/crash] error trace: 2aa19f62a78 => 2aa19fe1de6 => 2aa1a026e2c
=> 2aa1a026d88


This has been reported upstream here :

https://www.redhat.com/archives/crash-utility/2016-January/msg00031.html

Crash version on Xenial should be upgraded to crash-7.1.5

** Affects: crash (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: s390x

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555244

Title:
  crash fails to load with 4.4+ kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1555244/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1555244] Re: crash fails to load with 4.4+ kernels

[Louis Bouchard]

** Also affects: crash (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: crash (Ubuntu)
   Status: New => Confirmed

** Changed in: crash (Ubuntu)
   Importance: Undecided => Medium

** Changed in: crash (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555244

Title:
  crash fails to load with 4.4+ kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1555244/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1555244] Re: crash fails to load with 4.4+ kernels

[Louis Bouchard]

Opened related debian bug : https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=817798

** Bug watch added: Debian Bug tracker #817798
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817798

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555244

Title:
  crash fails to load with 4.4+ kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1555244/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1554004] Re: Segfault on X startup with VX900

[Louis Bouchard]

** Also affects: xserver-xorg-video-openchrome (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: xserver-xorg-video-openchrome (Ubuntu Wily)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554004

Title:
  Segfault on X startup with VX900

To manage notifications about this bug go to:
https://bugs.launchpad.net/openchrome/+bug/1554004/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1555244] Re: crash fails to load with 4.4+ kernels

[Louis Bouchard]

** Changed in: crash (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555244

Title:
  crash fails to load with 4.4+ kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1555244/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538148] Re: man kdump-config is missing the propagate option

[Louis Bouchard]

Fixed in makedumpfile (1:1.5.9-4) from Debian/sid

** Changed in: kexec-tools (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: kexec-tools (Ubuntu)
 Assignee: Louis Bouchard (louis-bouchard) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538148

Title:
  man kdump-config is missing the propagate option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1538148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1554004] Re: Segfault on X startup with VX900

[Louis Bouchard]

** Changed in: xserver-xorg-video-openchrome (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: xserver-xorg-video-openchrome (Ubuntu Wily)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554004

Title:
  Segfault on X startup with VX900

To manage notifications about this bug go to:
https://bugs.launchpad.net/openchrome/+bug/1554004/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1103398] Re: While adding new printer, got error popup "Query type 'postscript-driver' is not supported"

[Louis Bouchard]

** Changed in: makedumpfile (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103398

Title:
  While adding new printer, got error popup "Query type 'postscript-
  driver' is not supported"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1103398/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1626269] Re: Ubuntu 16.10: kdump is not working in 4.8 kernel.

[Louis Bouchard]

Hello,

The fix for this issue has been uploaded for Xenial and Yakkety and is
awaiting SRU approval.

** Description changed:

+ [SRU justification]
+ makedumpfile fails to execute if executed on a 4.8 kernel
+ 
+ [Impact]
+ Unable to generate compressed kernel dumps on those platform
+ 
+ [Fix]
+ Backport commits 2c21d4656e8d3c2af2b1e14809d076941ae69e96 and 
+ 0c9dd01d8ee2e4ec1821a11f5e174fdba56012b8.
+ 
+ The second commit is required since, once the initial issue is fixed, it
+ triggers a second issue fixed on Debian by https://bugs.debian.org/cgi-
+ bin/bugreport.cgi?bug=842019
+ 
+ [Test Case]
+ - Install kernel 4.8 along with the linux-crashdump metapackage
+ - Reboot to enable kdump
+ - Trigger a kernel panic with "echo c > /proc/sysrq-trigger"
+ 
+ Without the patch, the following message will appear and makedumpfile
+ will fail :
+ 
+  get_mem_map: Can't distinguish the memory type.
+ 
+ With the fix, makedumpfile completes correctly.
+ 
+ [Regression]
+ None expected. The modification keeps the initial structure when kernels 
before 4.8 are used.
+ 
+ [Original description of the problem]
+ 
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-09-21 00:50:22 ==
  ---Problem Description---
  
  Ubuntu 16.10: kdump is not working in 4.8 kernel.
  
  ---Steps to Reproduce---
  
  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg
  
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=2G-
  4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M"
  
  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show
  6) echo "c" > /proc/sysrq-trigger
  
  Logs
  
  
  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  
- 
  root@ubuntu:/home/ubuntu# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
- crashkernel addr: 
-/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-11-generic
- kdump initrd: 
-/var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-11-generic
+ crashkernel addr:
+    /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-11-generic
+ kdump initrd:
+    /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-11-generic
  current state:ready to kdump
  
  kexec command:
-   /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-11-generic 
root=UUID=7ea3831b-f4c3-4f69-8f77-79aefcda70e3 ro splash quiet irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
+   /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-11-generic 
root=UUID=7ea3831b-f4c3-4f69-8f77-79aefcda70e3 ro splash quiet irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:/home/ubuntu# cd
  root@ubuntu:~# echo "c" > /proc/sysrq-trigger
  [   50.733424] sysrq: SysRq : Trigger a crash
  [   50.733437] Unable to handle kernel paging request for data at address 
0x
  [   50.733441] Faulting instruction address: 0xc05af3f4
  [   50.733444] Oops: Kernel access of bad area, sig: 11 [#1]
  [   50.733446] SMP NR_CPUS=2048 NUMA pSeries
  [   50.733450] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag pseries_rng sg 
rng_core binfmt_misc ghash_generic gf128mul vmx_crypto ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache sr_mod cdrom sd_mod bnx2x ibmvscsi 
ibmveth scsi_transport_srp ptp pps_core mdio libcrc32c crc32c_generic 
crc32c_vpmsum
  [   50.733477] CPU: 2 PID: 1517 Comm: bash Not tainted 4.8.0-11-generic 
#12-Ubuntu
  [   50.733480] task: c004f7906880 task.stack: c004f7898000
  [   50.733482] NIP: c05af3f4 LR: c05b04d8 CTR: 
c05af3c0
  [   50.733485] REGS: c004f789b990 TRAP: 0300   Not tainted  
(4.8.0-11-generic)
  [   50.733488] MSR: 80009033   CR: 28242422  
XER: 0001
- [   50.733496] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1 
- GPR00: c05b04d8 c004f789bc10 c0f46700 0063 
- GPR04: c005ef78a9b8 c005ef79f7d8 c0063fe82300 5970 
- GPR08: 0007 0001  0001 
- GPR12: c05af3c0 c7b31200  2200 
- GPR16: 10170dc8 0100111c0538 10140f58 100c7570 
- GPR20:  1017dd58 10153618 1017b608 
- GPR24: 310b9624 0001 c0e9fd40 0004 
- GPR28: c0ea0100 0063 c0e528e8  
+ [   50.733496] CFAR: c00087d0 DAR: 0

[Bug 1643618] [NEW] Please merge nut 2.7.4-4 (main) from Debian unstable (main)

[Louis Bouchard]

Public bug reported:

Merge bug

** Affects: nut (Ubuntu)
 Importance: Wishlist
 Assignee: Louis Bouchard (louis-bouchard)
 Status: In Progress

** Changed in: nut (Ubuntu)
   Status: New => In Progress

** Changed in: nut (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: nut (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643618

Title:
   Please merge nut 2.7.4-4 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1643618/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643837] [NEW] Please merge clamav (0.99.2+dfsg-4) from Debian unstable

[Louis Bouchard]

Public bug reported:

merge bug

** Affects: clamav (Ubuntu)
 Importance: Wishlist
 Assignee: Louis Bouchard (louis-bouchard)
 Status: In Progress

** Changed in: clamav (Ubuntu)
   Status: New => In Progress

** Changed in: clamav (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: clamav (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643837

Title:
  Please merge clamav (0.99.2+dfsg-4) from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1643837/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1644428] Re: Unable to log in with AD account after update

[Louis Bouchard]

Hello,

The safest route for the time being is to revert back to 2:4.3.11+dfsg-
0ubuntu0.14.04.1 as outlined in the other bug while we investigate the
issue.

** Also affects: samba (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: samba (Ubuntu Trusty)
   Status: New => Triaged

** Changed in: samba (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: samba (Ubuntu Trusty)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644428

Title:
  Unable to log in with AD account after update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1644428/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1644771] [NEW] kdump-tools: Fails to load kdump kernel when /proc/cmdline contains double quotes

[Louis Bouchard]

Public bug reported:

kdump-tools fails to load if one of the kernel parameter has double-
quotes

** Affects: makedumpfile (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: makedumpfile (Ubuntu Xenial)
 Importance: High
 Assignee: Louis Bouchard (louis-bouchard)
 Status: In Progress

** Affects: makedumpfile (Ubuntu Yakkety)
 Importance: High
 Assignee: Louis Bouchard (louis-bouchard)
 Status: In Progress

** Also affects: makedumpfile (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: makedumpfile (Ubuntu)
   Status: New => Fix Released

** Changed in: makedumpfile (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: makedumpfile (Ubuntu Yakkety)
   Importance: Undecided => High

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: makedumpfile (Ubuntu Yakkety)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: makedumpfile (Ubuntu Yakkety)
   Status: New => In Progress

** Bug watch added: Debian Bug tracker #835600
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835600

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644771

Title:
  kdump-tools: Fails to load kdump kernel when /proc/cmdline contains
  double quotes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1644771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1644771] Re: kdump-tools: Fails to load kdump kernel when /proc/cmdline contains double quotes

[Louis Bouchard]

Debian bug for reference : https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=835600

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644771

Title:
  kdump-tools: Fails to load kdump kernel when /proc/cmdline contains
  double quotes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1644771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1644771] Re: kdump-tools: Fails to load kdump kernel when /proc/cmdline contains double quotes

[Louis Bouchard]

** Description changed:

- kdump-tools fails to load if one of the kernel parameter has double-
- quotes
+ [SRU justification]
+ This fix is needed to avoid failure to load kdump-tools when one kernel boot 
parameter has double-quotes.
+ 
+ [Impact]
+ kdump functionality becomes unusable
+ 
+ [Fix]
+ Modify kdump-config to handle the presence of double-quotes in the cmdline
+ 
+ [Test Case]
+ Edit /etc/default/grub and add the following to GRUB_CMDLINE_LINUX_DEFAULT :
+ 
+ \"acpi_osi=!Windows 2012\"
+ $ sudo update-grub
+ $ sudo reboot
+ 
+ kdump-config will show the following error upon reboot :
+ 
+ [   11.595868] kdump-tools[1710]: Cannot open `2012 irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service': No s
+ uch file or directory 
 
+ [   11.602563] kdump-tools[1710]:  * failed to load kdump kernel  
 
+ 
+ With this fix, the kdump-config command will run successfully
+ 
+ [Regression]
+ None expected. Fix is already in Zesty & Debian. Only one line added to the 
sed statement.
+ 
+ [Original description of the problem]
+ kdump-tools fails to load if one of the kernel parameter has double-quotes

** Tags added: sts-sru

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644771

Title:
  kdump-tools: Fails to load kdump kernel when /proc/cmdline contains
  double quotes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1644771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1644428] Re: Unable to log in with AD account after update

[Louis Bouchard]

** Changed in: samba (Ubuntu)
   Status: Invalid => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644428

Title:
  Unable to log in with AD account after update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1644428/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1619239] Re: [MIR] tomsfastmath (runtime dependency of clamav)

[Louis Bouchard]

Debian has accepted basic enablement of stest in the latest tomsfastmath
package (0.13-4) :

Maintainer: ClamAV Team 
Changed-By: Sebastian Andrzej Siewior 
Description:
 libtfm-dev - Fast multiple-precision integer library [development files]
 libtfm1- Fast multiple-precision integer library [runtime]
Closes: 838497
Changes:
 tomsfastmath (0.13-4) unstable; urgency=medium
 .
   * Run stest after compile for basic testing (Closes: #838497).

MIR for tomsfastmath is the last hurdle in dropping the last clamav
delta and being able to sync to Debian.

Please have a look to know if any security review is required

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619239

Title:
  [MIR] tomsfastmath (runtime dependency of clamav)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomsfastmath/+bug/1619239/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1636322] Re: upstart: ceph-all service starts before networks up

[Louis Bouchard]

** Also affects: ceph (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ceph (Ubuntu Zesty)
   Importance: High
 Assignee: Billy Olsen (billy-olsen)
   Status: Triaged

** Also affects: ceph (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: ceph (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: ceph (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: ceph (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: ceph (Ubuntu Zesty)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636322

Title:
  upstart: ceph-all service starts before networks up

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1636322/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1648380] Re: cloud-init fails to find CloudSigma datasource with cloud-init 0.7.8-1-g3705bb5-0ubuntu1

[Louis Bouchard]

** Tags removed: verification-needed
** Tags added: verification-done-xenial verification-needed-yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648380

Title:
  cloud-init fails to find CloudSigma datasource with cloud-init
  0.7.8-1-g3705bb5-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1648380/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1666239] Re: Add ZFS sosreport plugin

[Louis Bouchard]

** Also affects: sosreport (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: sosreport (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: sosreport (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: sosreport (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: sosreport (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: sosreport (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: sosreport (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: sosreport (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: sosreport (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: sosreport (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: sosreport (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: sosreport (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: sosreport (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: sosreport (Ubuntu Trusty)
 Assignee: (unassigned) => Louis Bouchard (louis)

** Changed in: sosreport (Ubuntu Xenial)
 Assignee: (unassigned) => Louis Bouchard (louis)

** Changed in: sosreport (Ubuntu Yakkety)
     Assignee: (unassigned) => Louis Bouchard (louis)

** Changed in: sosreport (Ubuntu Zesty)
 Assignee: (unassigned) => Louis Bouchard (louis)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666239

Title:
  Add ZFS sosreport plugin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1666239/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1614052] Re: SOSREPORT need to collect OPAL msglog

[Louis Bouchard]

** Also affects: sosreport (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: sosreport (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: sosreport (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: sosreport (Ubuntu Trusty)
 Assignee: (unassigned) => Louis Bouchard (louis)

** Changed in: sosreport (Ubuntu Yakkety)
 Assignee: (unassigned) => Louis Bouchard (louis)

** Changed in: sosreport (Ubuntu Zesty)
 Assignee: (unassigned) => Louis Bouchard (louis)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614052

Title:
  SOSREPORT need to collect OPAL msglog

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1614052/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1605243] Re: iscsi initiator related configs and logs are not recorded

[Louis Bouchard]

** Also affects: sosreport (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: sosreport (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: sosreport (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: sosreport (Ubuntu Zesty)
 Assignee: (unassigned) => Louis Bouchard (louis)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605243

Title:
  iscsi initiator related configs and logs are not recorded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1605243/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

[Louis Bouchard]

** Description changed:

  [SRU justification]
  This fix is needed to make sure that the system does not hang on shutdown 
when /var is a speparate file system
  
  [Impact]
  System can hang up to 10 minutes if not fixed.
  
  [Fix]
  Change the systemd unit's ExecStart to an ExecStop so the unit is correctly 
sequenced.
+ Change WantedBy to multi-user.target. This requires working around Debian Bug 
#797108 which causes the new unit not to be enabled.
+ Remove the unneeded override_dh_isntallinit
+ Add Default-Start levels to the SysV initscript
+ Improve DEP8 testing
  
  [Test Case]
  In a VM with /var separated from the / file system, shutdown the VM. It will 
hang for 10 minutes
  
  [Regression]
- None to be expected. A ExecStop unit will be sequenced before the Before= 
units which is earlier than previously.
+ Upgrade has been tested on Xenial, Yakkety, Zesty. do-release-upgrade has 
been tested from Trusty to Xenial. All behave as expected.
+ 
+ A change of behavior may occur now that the systemd unit is correctly
+ enabled, which would make functionalities like InstallOnShutdown to work
+ as expected whereas it could have been broken previously. This cannot be
+ considered as a regression as it is expected behavior.
+ 
+ Shutdown may be slowed down as it now correctly depends on /var and
+ /boot to be available so the unit will run earlier than previously.
  
  [Original description of the problem]
  The systemd unit file unattended-upgrades.service is used to stop a running 
unattended-upgrade
  process during shutdown. This unit file is running together with all 
filesystem
  unmount services.
  
  The unattended-upgrades service checks if the lockfile for unattended-upgrade
  (in /var/run) exists, and if it does, there is an unattended-upgrade in 
progress
  and the service will wait until it finishes (and therefore automatically wait 
at
  shutdown).
  
  However, if /var is a separate filesystem, it will get unmounted even though 
/var/run
  is a tmpfs that's still mounted on top of the /var/run directory in the /var 
filesystem.
  The unattended-upgrade script will fail to find lockfile, sleeps for 5 
seconds, and
  tries to check the lockfile again. After 10 minutes (the default timeout), it 
will finally
  exit and the system will continue shutdown.
  
  The problem is the error handling in 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
  where it tries to lock itself:
  
  while True:
  res = apt_pkg.get_lock(options.lock_file)
  logging.debug("get_lock returned %i" % res)
  # exit here if there is no lock
  if res > 0:
  logging.debug("lock not taken")
  break
  lock_was_taken = True
  
  The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an 
error.
  File descriptors are just C file descriptors, so they are always positive 
integers.
  The code should check the result to be negative, not positive. I have 
attached a patch
  to reverse the logic.
  
  Additional information:
  
  1)
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  
  2)
  unattended-upgrades:
    Installed: 0.90ubuntu0.3
    Candidate: 0.90ubuntu0.3
    Version table:
   *** 0.90ubuntu0.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  3)
  Fast reboot
  4)
  Very slow reboot (after a 10 minutes timeout)

** Changed in: unattended-upgrades (Ubuntu Yakkety)
   Status: Triaged => In Progress

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: unattended-upgrades (Ubuntu)
 Assignee: Louis Bouchard (louis) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654600

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

[Louis Bouchard]

** Tags removed: sts-sru-needed verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654600

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

[Louis Bouchard]

Test performed for verification-done for :
 - Xenial
 - Yakkety
 - Zesty
1) Installed unattended-upgrades from -proposed
2) Verified the status of the unattended-upgrades service. All displayed :

# systemctl status unattended-upgrades
● unattended-upgrades.service - Unattended Upgrades Shutdown
   Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Fri 2017-04-28 14:02:35 CEST; 47s ago
 Docs: man:unattended-upgrade(8)

3) Enabled Unattended-Upgrade::InstallOnShutdown "true"; in
/etc/apt/apt.conf.d/50unattended-upgrades and rebooted. All releases
applied the upgradeable packages upon reboot (some had too many and the
timeout ran out before end of update)

4) Ran apt -y dist-upgrade on all releases. Rebooted. systems rebooted
normally.

5) Enabled trusty-proposed on a Trusty system and ran do-release-upgrade
to go to Xenial. After completion of the full upgrade, unattended-
upgrades service was active (as seen in #2)

6) Enabled zesty-proposed on a system with /var as a separate file
system. Upgraded unattended-upgrades. After upgrade, unattended-upgrades
service was active (as seen in #2)

7) Verified that the workaround for Debian Bug #809669 left the upgraded
system in an adequate configuration :

cat 
/var/lib/systemd/deb-systemd-helper-enabled/unattended-upgrades.service.dsh-also
 
/etc/systemd/system/multi-user.target.wants/unattended-upgrades.service

# find /etc/systemd | grep unatt
/etc/systemd/system/multi-user.target.wants/unattended-upgrades.service

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654600

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

[Louis Bouchard]

Re-targetting the bug to the linux kernel as this is not a makedumpfile
issue

** Package changed: makedumpfile (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687779

Title:
  Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

[Louis Bouchard]

** Also affects: makedumpfile (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687779

Title:
  Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1605243] Re: iscsi initiator related configs and logs are not recorded

[Louis Bouchard]

Test done for the following releases : Trusty, Xenial, Yakkety, Zesty

1) Launch a container
2) Enable proposed
3) apt update
4) apt install sosreport and open-iscsi(if absent)
5) sosreport --batch -oiscsi
6) Extract sosreport tarball locally
7) Verify collected files :
# ls sosreport-zesty-sosiscsi-20170505095538/etc/isc*
initiatorname.iscsi  iscsid.conf
8) Verify the output of the collected commands :
find sosreport-zesty-sosiscsi-20170505095538/sos_commands/iscsi/* -exec cat {} 
\; -ls
# find sosreport-zesty-sosiscsi-20170505095538/sos_commands/iscsi/* -exec cat 
{} \; -ls
Iface: default
Iface: iser
34041  5 -rw-r--r--   1 root root   27 May  5 09:55 
sosreport-zesty-sosiscsi-20170505095538/sos_commands/iscsi/iscsiadm_-m_iface_-P_1
iscsiadm: No records found
34043  5 -rw-r--r--   1 root root   27 May  5 09:55 
sosreport-zesty-sosiscsi-20170505095538/sos_commands/iscsi/iscsiadm_-m_node_--op_show
iscsiadm: No records found
34044  5 -rw-r--r--   1 root root   27 May  5 09:55 
sosreport-zesty-sosiscsi-20170505095538/sos_commands/iscsi/iscsiadm_-m_node_-P_1
iscsiadm: No active sessions.
iSCSI Transport Class version 2.0-870
version 2.0-873
34042  5 -rw-r--r--   1 root root   84 May  5 09:55 
sosreport-zesty-sosiscsi-20170505095538/sos_commands/iscsi/iscsiadm_-m_session_-P_3


** Tags removed: sts-sru-needed verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605243

Title:
  iscsi initiator related configs and logs are not recorded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1605243/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1614052] Re: SOSREPORT need to collect OPAL msglog

[Louis Bouchard]

Hello,

could someone from the reporter team or with access to the proper
hardware test the package in -proposed for the following releases ?

 - Trusty
 - Xenial
 - Yakkety
 - Zesty

This is the last bug which requires testing, hence it is holding the
release of the sosreport with the requested fix.

TIA,

...Louis

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614052

Title:
  SOSREPORT need to collect OPAL msglog

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1614052/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1687791] Re: Install of kdump-tools fails

[Louis Bouchard]

Hello,

I am surprised by a few things : first of all, linux-crashdump, hence
kdump-tools, is not installed by default on a server install. So you
must have added that step somehow.

I have just installed Xenial using the mini.iso network install and
kdump-tool is not installed after completion. I installed it without any
issue, rebooted and the functionality works as expected.

Now your output shows that it is the kernel's post-install trigger that
fails, so this is where you should but the -x (add it to the sh -e
shebang at the top of the script). Then you can run the following &
paste the output here :

/etc/kernel/postinst.d/kdump-tools $(uname -r)

FYI, this script is responsible for building the smaller initrd used by
kdump when rebooting after a crash.

...Louis

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687791

Title:
  Install of kdump-tools fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1687791/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1666207] [NEW] Unable to create VPN connection on Zesty

[Louis Bouchard]

Public bug reported:

When trying to create a new VPN connection with nm-connection-editor,
the new connection cannot be saved and the editor issues the following
error :

LC_ALL="C" nm-connection-editor
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
** Message: Cannot save connection due to error: Editor initializing...
** Message: Cannot save connection due to error: Invalid setting VPN: remote

dpkg -l | grep network-manager-gnome
network-manager-gnome   1.4.2-1ubuntu2

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666207

Title:
  Unable to create VPN connection on Zesty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1666207/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1666207] Re: Unable to create VPN connection on Zesty

[Louis Bouchard]

This is not a bug, but seems to happen when some required fields are not
yet filled. While the 'remote' field can be obvious,it is much less
evident when the interface refuses to allow the configuration to be
saved, because the certificate provided requires a password and the
password field has been left blank.

The UI should be more explicit on why it does not allow the
configuration to be saved.

Marking the bug as invalid

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666207

Title:
  Unable to create VPN connection on Zesty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1666207/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

[Louis Bouchard]

** Tags removed: sts-sponsor

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647485

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1647485/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1550983] Re: Fails to start with "Couldn't open libGL.so.1" (missing dependency?)

[Louis Bouchard]

** Tags removed: sts-sponsor

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550983

Title:
  Fails to start with "Couldn't open libGL.so.1" (missing dependency?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1550983/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1641875] Re: Scheduled events (e.g. LDAP connection retries) are affected by clock adjustments

[Louis Bouchard]

** Changed in: sssd (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: sssd (Ubuntu Yakkety)
   Status: New => Triaged

** Changed in: sssd (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: sssd (Ubuntu Trusty)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641875

Title:
  Scheduled events (e.g. LDAP connection retries) are affected by clock
  adjustments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1641875/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1638695] Re: Python 2.7.12 performance regression

[Louis Bouchard]

Hello,

The tests are run in LXC containers on a bare metal server with two
physical CPU, 6 cores, 2 threads per core (Intel(R) Xeon(R) CPU E5-2640
0 @ 2.50GHz).

Following's doko's advice, I have built two new versions, one with LTO
optimisation disabled and the other one with PGO optimisation disabled.
In both cases, it makes things worse.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638695

Title:
  Python 2.7.12 performance regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1666827] Re: Backport fixes for Rename Network return 403 Error

[Louis Bouchard]

** Also affects: horizon (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: horizon (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: horizon (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: horizon (Ubuntu Yakkety)
   Status: New => Fix Released

** Changed in: horizon (Ubuntu Trusty)
   Status: New => Triaged

** Changed in: horizon (Ubuntu Xenial)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666827

Title:
  Backport fixes for Rename Network return 403 Error

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1666827/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1638695] Re: Python 2.7.12 performance regression

[Louis Bouchard]

Hello,

Following doko's advice, I ran a set of test with PGO & LTO optimization
disabled.

Here are the results :
https://docs.google.com/spreadsheets/d/1tTlEOvMypwKwi99XHjvuQFE14_jpBBLy0-Mk6bjkvL0/edit#gid=1169944329

This may bring more light to the investigation as it appear that with
LTO & PGO optimisation disabled on Trusty, the trusty version becomes
slower than the Xenial stock version. Disabling optimisation on Xenial
makes little difference though.

So maybe the PGO & LTO optimisation on Trusty is more efficient than on
Xenial and leads to better results,hence better performance. Just a
thought

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638695

Title:
  Python 2.7.12 performance regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1557751] Re: makedumpfile generates kernel version error

[Louis Bouchard]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557751

Title:
  makedumpfile generates kernel version error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1557751/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1641875] Re: Scheduled events (e.g. LDAP connection retries) are affected by clock adjustments

[Louis Bouchard]

Fixed debdiff used for sponsorship (fixed versionning to stay coherent
with other releases)

** Patch added: "yakkety-sssd_1.13.4-3ubuntu0.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1641875/+attachment/4825142/+files/yakkety-sssd_1.13.4-3ubuntu0.1.debdiff

** Patch removed: "yakkety-sssd_1.13.4-3ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1641875/+attachment/4824488/+files/yakkety-sssd_1.13.4-3ubuntu1.debdiff

** Tags removed: sts-sponsor

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641875

Title:
  Scheduled events (e.g. LDAP connection retries) are affected by clock
  adjustments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1641875/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1636322] Re: upstart: ceph-all service starts before networks up

[Louis Bouchard]

** Tags removed: sts-sponsor

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636322

Title:
  upstart: ceph-all service starts before networks up

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1636322/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645324] Re: ebtables: Lock file should be moved from /var/lib/ebtables to /run

[Louis Bouchard]

** Tags removed: sts-sponsor

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645324

Title:
  ebtables: Lock file should be moved from /var/lib/ebtables to /run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1664203] Re: v1 driver does not delete namespace when pool deleted

[Louis Bouchard]

** Also affects: neutron-lbaas (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: neutron-lbaas (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: neutron-lbaas (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: neutron-lbaas (Ubuntu Yakkety)
   Status: New => Won't Fix

** Changed in: neutron-lbaas (Ubuntu Xenial)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664203

Title:
  [SRU] v1 driver does not delete namespace when pool deleted

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1664203/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1638695] Re: Python 2.7.12 performance regression

[Louis Bouchard]

** Changed in: python2.7 (Ubuntu)
 Assignee: Jorge Niedbalski (niedbalski) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638695

Title:
  Python 2.7.12 performance regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1638695] Re: Python 2.7.12 performance regression

[Louis Bouchard]

Following the results of the previous comparison, i've used Jorge's
profiling example on the 'call_method' bench for trusty stock, no LTO,
no PGO and Xenial stock, no PGO and no LTO. Here are the results. Notice
the difference between Trusty Stock & Trusty nopgo, as opposed to the
execution profiles of the other tests.

Trusty Stock

callgrind_annotate:
Profiled target:  /home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python 
/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/li
b/python2.7/site-packages/performance/benchmarks/bm_call_method.py --worker 
--pipe 4 --worker-task=0 --samples 3 --
warmups 1 --loops 1 --min-time 0.1 (PID 25150, part 1)
4,918,198,605  ???:PyEval_EvalFrameEx'2 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]
1,180,507,700  ???:0x005368f0 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]
1,109,707,368  ???:PyObject_GetAttr 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]
  823,065,734  ???:PyFrame_New 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]
  552,755,137  ???:0x004a5c90 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7] 
  525,836,692  ???:0x004bedf0 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]
   12,732,711  ???:PyParser_AddToken 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]
6,120,934  ???:PyDict_GetItem 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]
4,700,333  ???:0x004bc0e0 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]
4,647,564  ???:0x004afe90'2 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]
3,724,240  ???:PyObject_Free 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]
3,526,112  ???:PyDict_SetItem 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]
3,407,575  ???:0x00571fd0 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]
3,304,198  ???:PyObject_Hash 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]
3,055,436  ???:0x005495a0 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]
2,796,306  ???:0x00535070 
[/home/ubuntu/venv/cpython2.7-d0d7712d4e1d/bin/python2.7]

Trusty nopgo:
=
Profiled target:  /home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python 
/home/ubuntu/venv/cpython2.7-d217262e7ee7/li
b/python2.7/site-packages/performance/benchmarks/bm_call_method.py --worker 
--pipe 4 --worker-task=0 --samples 3 --
warmups 1 --loops 1 --min-time 0.1 (PID 28073, part 1)
5,362,602,828  ???:PyEval_EvalFrameEx'2 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
1,250,195,637  ???:0x00585e90 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
  890,479,191  ???:PyFrame_New 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
  836,574,419  ???:PyObject_GenericGetAttr 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
  552,808,267  ???:0x0049ef00 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
  539,318,922  ???:0x00493710 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
  488,401,927  ???:_PyType_Lookup 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
  258,028,053  ???:PyObject_GetAttr 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
   12,247,026  ???:0x005937f0 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
   11,727,983  ???:PyParser_AddToken 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
6,409,083  ???:PyDict_GetItem 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
4,948,165  ???:PyObject_Malloc 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
4,746,403  ???:0x004f7b70'2 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
4,525,638  ???:PyNode_AddChild 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
4,429,698  ???:PyObject_Free 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
3,582,953  ???:0x0041aff0 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]
3,240,230  ???:PyObject_Hash 
[/home/ubuntu/venv/cpython2.7-d217262e7ee7/bin/python2.7]

Trusty nolto:
=
Profiled target:  /home/ubuntu/venv/cpython2.7-d8da6ef977cc/bin/python2.7 
/home/ubuntu/venv/cpython2.7-d8da6ef977cc
/lib/python2.7/site-packages/performance/benchmarks/bm_call_method.py --worker 
--pipe 4 --worker-task=0 --samples 3
 --warmups 1 --loops 1 --min-time 0.1 (PID 27353, part 1)
4,930,764,066  ???:PyEval_EvalFrameEx'2 
[/home/ubuntu/venv/cpython2.7-d8da6ef977cc/bin/python2.7]
1,059,123,292  ???:0x00486370 
[/home/ubuntu/venv/cpython2.7-d8da6ef977cc/bin/python2.7]
  879,185,389  ???:PyObject_GetAttr 
[/home/ubuntu/venv/cpython2.7-d8da6ef977cc/bin/python2.7]
  823,049,135  ???:PyFrame_New 
[/home/ubuntu/venv/cpython2.7-d8da6ef977cc/bin/python2.7]
  552,712,907  ???:0x00477410 
[/home/ubuntu/venv/cpython2.7-d8da6ef977cc/bin/python2.7]
  539,326,714  ???:PyMethod_New 
[/home/ubuntu/venv/cpython2.7-d8da6ef97

[Bug 1638695] Re: Python 2.7.12 performance regression

[Louis Bouchard]

Here is the pastebin for better readability :
http://paste.ubuntu.com/24078834/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638695

Title:
  Python 2.7.12 performance regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1652595] Re: Ubuntu 16.04.02: crash tool fails with error "cannot find 'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or 'cpu_active_map' symbols".

[Louis Bouchard]

So correct me if I'm wrong,but you are basically stating that this bug
should be Marked as "Fix Released" since it is corrected by the latest
crash/makedumpfile SRU ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652595

Title:
  Ubuntu 16.04.02: crash tool fails with error "cannot find
  'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or
  'cpu_active_map' symbols".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1652595/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Louis Bouchard]

** Also affects: rsyslog (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: rsyslog (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: rsyslog (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668639

Title:
  Add a trigger to reload rsyslog when a new configuration file is
  dropped in /etc/rsyslog.d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1652595] Re: Ubuntu 16.04.02: crash tool fails with error "cannot find 'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or 'cpu_active_map' symbols".

[Louis Bouchard]

*** This bug is a duplicate of bug 1655625 ***
https://bugs.launchpad.net/bugs/1655625

** This bug has been marked a duplicate of bug 1655625
   ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652595

Title:
  Ubuntu 16.04.02: crash tool fails with error "cannot find
  'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or
  'cpu_active_map' symbols".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1652595/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1661611] Re: apt/unattended-upgrades stalls shutdown

[Louis Bouchard]

*** This bug is a duplicate of bug 1654600 ***
https://bugs.launchpad.net/bugs/1654600

This is a duplicate of another bug I'm working on and is caused by a
systemd ordering issue.

** This bug has been marked a duplicate of bug 1654600
   unattended-upgrade-shutdown hangs when /var is a separate filesystem

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661611

Title:
  apt/unattended-upgrades stalls shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1661611/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

[Louis Bouchard]

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654600

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1535898] Re: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

[Louis Bouchard]

** Description changed:

+ [SRU justification]
+ Without this patch, multipathd may exit in SEGV in trying to add a map that 
aleady exists
+ 
+ [Impact]
+ multipathd crashes with SIGSEGV
+ A typical trace of such a situation is a message similar to this one in 
/var/log/syslog :
+ 
+ multipathd: 360060160164034004cd59cfdb22ce611: failed in domap for
+ addition of new path sdr
+ 
+ [Fix]
+ Check if the map already exists and do a RELOAD in domap() instead of failing.
+ 
+ [Test Case]
+ Problem was encountered in a complex Openstack test environment where the 
following was done :
+ A test tool which runs which :
+ - first boots a number of virtual machines. 
+ - then it creates a number of threads and in each thread it 
+ creates volumes, takes snapshots of the volumes, and attaches the volumes to 
the initially booted virtual machines. After a short while the volumes are 
detached, and snapshots and volumes are deleted.
+ 
+ Running this tool overnight normally result in running in the multipathd
+ SEGV situation.
+ 
+ [Regression]
+ This is a straight backport of the code being used in 0.5.0. No regression is 
to be expected.
+ 
+ It is important to note that the reproducer in the original description
+ did not lead to such a problem.
+ 
+ [Original description of the problem]
+ 
  We have a problem on multipath-tools.
  
  Usually after a path removal and a re-scan, the multipathd process dies.
  
  I created 2 hosts:
  
  iscsi-server
  iscsi-client
  
  With 4 NICs in between them and with a simple multibus multipath. With
  that I was able to check that there is a regression in multipath-tools.
  
  It looks like the patches brought from upstream:
  
  0017-multipath-get-right-sysfs-value-for-checker_timeout.patch
  0018-multipath-handle-offlined-paths.patch
  #
  # from here
  #
  0019-multipath-fix-scsi-timeout-code.patch
  0020-multipath-make-tgt_node_name-work-for-iscsi-devices.patch
  0021-multipath-cleanup-dev_loss_tmo-issues.patch
  0022-Fix-for-setting-0-to-fast_io_fail.patch
  0023-Fix-fast_io_fail-capping.patch
  0024-multipath-enable-getting-uevents-through-libudev.patch
  0025-Use-devpath-as-argument-for-sysfs-functions.patch
  0026-multipathd-remove-references-to-sysfs_device.patch
  0027-multipathd-use-struct-path-as-argument-for-event-pro.patch
  0028-Add-global-udev-reference-pointer-to-config.patch
  0029-Use-udev-enumeration-during-discovery.patch
  0030-use-struct-udev_device-during-discovery.patch
  0031-More-debugging-output-when-synchronizing-path-states.patch
  0032-Use-struct-udev_device-instead-of-sysdev.patch
  0033-discovery-Fixup-cciss-discovery.patch
  0035-Use-udev-devices-during-discovery.patch
  0036-Remove-all-references-to-hand-craftes-sysfs-code.patch
  #
  # to here
  #
  # 0037-multipath-libudev-cleanup-and-bugfixes.patch
  # 0038-multipath-check-if-a-device-belongs-to-multipath.patch
  # 0039-multipath-and-wwids_file-multipath.conf-option.patch
  # 0040-multipath-Check-blacklists-as-soon-as-possible.patch
  # 0041-add-wwids-file-cleanup-options.patch
  # 0042-add-find_multipaths-option.patch
  # 0043-alloc-keywords.patch
  # lp1503305_libmultipath_info_on_1st_path_down_dbd131e.patch
  
  In the range 19-36 caused a regression.
  
  Whenever I generate the package (for trusty) including those patches I'm
  able to generate a core dump indicating a possible double-free or null-
  dereference related to a path removal (that is why I can reproduce with
  the test case). Unfortunately it usually explodes inside malloc() or
  somewhere in glibc.
  
  Using valgrind I was able to verify some free() errors:
  
  ==30415== Invalid free() / delete / delete[] / realloc()
  ==30415==at 0x4C2BDEC: free (vg_replace_malloc.c:473)
  ==30415==by 0x54E243C: vector_del_slot (vector.c:95)
  ==30415==by 0x550A516: _remove_map (structs_vec.c:139)
  ==30415==by 0x550A5C3: _remove_maps (structs_vec.c:170)
  ==30415==by 0x550A64B: remove_maps (structs_vec.c:181)
  ==30415==by 0x40713F: configure (main.c:1153)
  ==30415==by 0x407A74: child (main.c:1419)
  ==30415==by 0x40837D: main (main.c:1618)
  
  And they are exactly aligned to a core dump (multipathd) I got from
  another user. (wrong free was coming from _remove_map).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535898

Title:
  Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1535898/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1621835] Re: multipathd reconfigure does not update /etc/multipath/wwids file on trusty

[Louis Bouchard]

Marking Yakkety as Invalid since it already has the fix.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621835

Title:
  multipathd reconfigure does not update /etc/multipath/wwids file on
  trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1621835/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1621835] [NEW] multipathd reconfigure does not update /etc/multipath/wwids file on trusty

[Louis Bouchard]

Public bug reported:

[Description of the problem]
[SRU justification]
When running "multipathd reconfigure", which is done when one does a "service 
multipath-tools restart", the file /etc/multipath/wwids does not get updated 
with the wwid entries. Only the header is found.

[Impact]
The content of the file may contain stale values or remain with only the file 
header if the file was removed.

[Fix]
Add a call to remember_wwid(mpp->wwid)

[Test Case]
With an up-to-date Trusty system running multipath-tools-0.4.9-3ubuntu7.13 do 
the following :

$ sudo cat /etc/multipath/wwids
# Multipath wwids, Version : 1.0
# NOTE: This file is automatically maintained by multipath and multipathd.
# You should not need to edit this file in normal circumstances.
#
# Valid WWIDs:
/1494554006c756e31/
/1494554006c756e32/
/1494554006c756e30/

$ sudo rm /etc/multipath/wwids
$ sudo service multipath-tools restart
$ sudo cat /etc/multipath/wwids
# Multipath wwids, Version : 1.0
# NOTE: This file is automatically maintained by multipath and multipathd.
# You should not need to edit this file in normal circumstances.
#
# Valid WWIDs:

With the proposed fix, the last command would give :
$ sudo cat /etc/multipath/wwids
# Multipath wwids, Version : 1.0
# NOTE: This file is automatically maintained by multipath and multipathd.
# You should not need to edit this file in normal circumstances.
#
# Valid WWIDs:
/1494554006c756e31/
/1494554006c756e32/
/1494554006c756e30/

[Regression]
Only one call to remember_wwid() is added. This is what is currently done in 
0.5.0

** Affects: multipath-tools (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: multipath-tools (Ubuntu Trusty)
 Importance: Medium
 Assignee: Louis Bouchard (louis-bouchard)
 Status: Confirmed

** Also affects: multipath-tools (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: multipath-tools (Ubuntu)
   Status: New => Invalid

** Changed in: multipath-tools (Ubuntu Trusty)
   Status: New => Confirmed

** Changed in: multipath-tools (Ubuntu Trusty)
     Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: multipath-tools (Ubuntu Trusty)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621835

Title:
  multipathd reconfigure does not update /etc/multipath/wwids file on
  trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1621835/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1621835] Re: multipathd reconfigure does not update /etc/multipath/wwids file on trusty

[Louis Bouchard]

Upstream commits :
- 
http://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=commit;h=0245b3ac6e34dee1ab039bba71806bc35c286ab8
- 
http://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=commit;h=e7d716fabe85acaaa61ec7065a103ac3a2f16cc2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621835

Title:
  multipathd reconfigure does not update /etc/multipath/wwids file on
  trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1621835/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1619239] Re: [MIR] tomsfastmath (runtime dependency of clamav)

[Louis Bouchard]

** Description changed:

- clamav is stalled in proposed ...
+ [Availability]
+ Currently in universe
+ 
+ [Rationale]
+ Most recent version of clamav has removed 'in-tree' version of libtfm-dev and 
now has a Build-Depends on libtfm-dev package
+ 
+ [Security]
+ 
+ 
+ [Quality Assurance]
+ 
+ 
+ [Dependencies]
+ All in main (debhelper, libtool-bin)
+ 
+ [Standards Compliance]
+ FHS and Debian Policy compliant.
+ 
+ [Maintenance]
+ 
+ 
+ [Background]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619239

Title:
  [MIR] tomsfastmath (runtime dependency of clamav)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomsfastmath/+bug/1619239/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs