Hi,
I've done some regression testing on qemu from mitaka-proposed,
following the procedure from comment #6:
$ dpkg -l | grep qemu
ii ipxe-qemu
1.0.0+git-2013.c3d1e78-2ubuntu1.1all PXE boot
firmware - ROM images for qemu
ii qemu-block
Hi,
I've done some regression testing on qemu from ocata-proposed, following
the procedure from comment #6:
$ dpkg -l | grep qemu
ii ipxe-qemu 1.0.0+git-20150424.a25a16d-1ubuntu1.2
all PXE boot firmware - ROM images for qemu
ii qemu-block-extra:amd64
Confirmed fix for Xenial, according to test case:
root@node1:~# pcs resource debug-start vg01
Operation start for vg01 (ocf:heartbeat:LVM) returned 0
> stdout: volume_list=["node1-vg","@tag1"]
> stdout: Volume group "vg01" successfully changed
> stdout: Volume group "vg01" successfully c
I've been doing some research on how we could implement a proper systemd
unit file for slapd, and came up with interesting results.
There are a number of options that we can pass to the slapd service that will
give us lots of troubles on an "idiomatic" service file. To give some examples:
- The P
** Bug watch added: Debian Bug tracker #926657
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926657
** Also affects: openldap (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926657
Importance: Unknown
Status: Unknown
** Patch added: "lp1821343-disco.debdiff"
@slashd I don't think we need anything special for systemd in the
debian/{control,rules} files, since we're not shipping full systemd
support with this. The slapd service is still handled by systemd-sysv-
generator(8), so there's no service units that we need to include or
activate in dh_systemd ru
** Changed in: resource-agents (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/1821380
Title:
HA-LVM can't parse vgchange_options with special character
ntu Disco)
Status: Triaged => Confirmed
** Changed in: open-iscsi (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: open-iscsi (Ubuntu Disco)
Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)
** Changed in: open-iscsi (Ubuntu Cosmic)
Assign
** Patch added: "lp1821255-bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1821255/+attachment/5250281/+files/lp1821255-bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Patch added: "lp1821255-cosmic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1821255/+attachment/5250282/+files/lp1821255-cosmic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Patch added: "lp1821255-disco.debdiff"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1821255/+attachment/5250283/+files/lp1821255-disco.debdiff
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I've updated the description with a simpler test case that doesn't require an
override file, but this bug can also be verified with the Restart=always
directive:
ubuntu@disco:~$ cat /etc/systemd/system/iscsid.service.d/override.conf
[Service]
Restart=always
ubuntu@disco:~$ sudo pkill iscsid
ubu
Hi Eric,
Xenial does not exhibit this bug since it does not ship iscsid.socket. This is
also the reason Debian is not affected, since they also don't have socket
activation for iscsid.
I did send a comment to the Debian bug that proposes changing iscsid to socket
activation [0], just so they're
@@corey.bryant I've checked Pike and it has the fix included already, so
I'm attaching a debdiff for Ocata only.
@hopem About Trusty-Mitaka, it seems that it automatically pulled the
patch from Xenial's release so it looks good too.
** Patch added: "lp1818880-ocata.debdiff"
https://bugs.launc
Public bug reported:
[Impact]
* TSC clocksource not available in nested guests
[Test Case]
* Spin up a nested Xenial/Bionic guest and check for 'tsc' at
/sys/devices/system/clocksource/clocksource0/available_clocksource
[Regression Potential]
* The regression potential is low. Upstream cod
This is easily verifiable on both Xenial and Bionic guests from uvt-kvm.
I've brought up both as nested instances, and TSC fails to show up as an
available clocksource:
== Xenial guest ==
$ uvt-kvm ssh bionic-l1
ubuntu@bionic-l1:~$ uvt-kvm ssh xenial-l2
ubuntu@xenial-l2:~$ uname -r
4.4.0-143-gen
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822821
Title:
TSC clocksource not available in nested guests
To manage notific
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Patches submitted to kernel-team list:
Xenial - https://lists.ubuntu.com/archives/kernel-team/2019-April/099810.html
Bionic - https://lists.ubuntu.com/archives/kernel-team/2019-April/099813.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Confirmed fix in bionic, according to test case:
ubuntu@bionic:~$ ./deploy-tgt.sh
ubuntu@bionic:~$ dpkg -l | grep open-iscsi
ii open-iscsi2.0.874-5ubuntu2.7 amd64iSCSI
initiator tools
ubuntu@bionic:~$ sudo pkill iscsid
ubuntu@bionic:~$ sudo systemctl stop isc
Confirmed fix in cosmic, according to test case:
ubuntu@cosmic:~$ ./deploy-tgt.sh
ubuntu@cosmic:~$ dpkg -l | grep open-iscsi
ii open-iscsi 2.0.874-5ubuntu9.4 amd64
iSCSI initiator tools
ubuntu@cosmic:~$ sudo pkill iscsid
ubuntu@cosmic:~$ sudo syste
** Patch added: "lp1821380-lvm-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1821380/+attachment/5252534/+files/lp1821380-lvm-xenial.debdiff
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Tested on linux-generic 3.13.0.168.179 from trusty-proposed. Tried
reproducing according to test case from description, and verified that
ixgbe is fixed:
# uname -r
3.13.0-168-generic
# apt-cache madison linux-generic
linux-generic | 3.13.0.168.179 |
http://archive.ubuntu.com/ubuntu/trusty-propo
Tested on pacemaker 1.1.14-2ubuntu1.5 from xenial-proposed. Tried
reproducing according to test case from description, and confirmed that
pacemaker is fixed:
# apt list pacemaker
pacemaker/xenial-proposed,now 1.1.14-2ubuntu1.5 amd64 [installed]
# echo "PCMK_logfile=/tmp/pacemaker.log" >> /etc/def
** Attachment added: "Helper script for continuous iperf tests in guest"
https://bugs.launchpad.net/cloud-archive/+bug/1818880/+attachment/5248210/+files/iperf-retry.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Hi,
As this bug is very hard to trigger, I've been running some tests with qemu
1:2.5+dfsg-5ubuntu10.35 to see if we didn't regress or break anything with the
new patch. My test setup is as follows:
1) Create new QEMU guest with uvt-kvm or virt-install
# uvt-kvm create xenial release=xenial -
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818880
Title:
Deadlock when d
should
make the slapd service behave like a "normal" forking service. Nonetheless,
we'll perform scripted test runs to make sure no regressions arise.
** Affects: openldap (Ubuntu)
Importance: Medium
Assignee: Heitor R. Alves de Siqueira (halves)
Status: Confirme
** Patch added: "debdiff for cosmic"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248490/+files/lp1821343-cosmic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Patch added: "debdiff for disco"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248489/+files/lp1821343-disco.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
** Patch added: "debdiff for bionic"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248492/+files/lp1821343-bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821343
Title:
slapd process failure is not detected by systemd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/
** Patch added: "debdiff for xenial"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248493/+files/lp1821343-xenial.debdiff
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
less, this fix
will be tested with different configuration options and autopkgtests.
** Affects: resource-agents (Ubuntu)
Importance: Medium
Status: Fix Released
** Affects: resource-agents (Ubuntu Xenial)
Importance: Medium
Assignee: Heitor R. Alves de Siqueira (halves)
The sysv init script does some funky parsing of configuration files that
might give us some trouble in an independent service file. I'll check if
we can't work around that and do away with the sysv init script
altogether, otherwise we might as well go with the drop-in override
since the new service
Tested on apt-1.0.1ubuntu2.20 from trusty-proposed. Tried reproducing
according to the test case from description, and verified that apt-cache
does not crash:
ubuntu@apt-stress:~/stress-ng$ dpkg -l | grep apt
ii apt 1.0.1ubuntu2.20
(while having stress-ng runn
There are two armhf autopkgtest regressions for apt-1.0.1ubuntu2.20, in
tests for apt [0] and autopkgtest [1]. From the autopkgtest pages we can
see that these regressions were introduced long before this SRU, so it
seems like a long standing issue unrelated to this patch.
[0] http://autopkgtest.u
** Description changed:
- Since kernel v4.5, the correct parameter to disable USB subsystem
- initialization is "usbcore.nousb" always (instead of "nousb" in case the
- subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb:
- make "nousb" a clear module parameter").
+ [Impact]
+ Cra
** Description changed:
- Kernel has the "reset_devices" parameter that drivers can opt-in, and
- perform special activity in case this parameter is parsed from command-
- line. For example, in kdump kernels it hints the drivers that they
- (maybe) are booting from a non-healthy condition and need
SRUv2 sent to kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2019-February/098451.htm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815501
Title:
ixgbe: Kernel Oops when at
** Patch added: "debdiff for disco"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239779/+files/disco_makedumpfile_1.6.5-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
** Patch added: "debdiff for bionic"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239781/+files/bionic_makedumpfile_1.6.3-2ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Patch added: "debdiff for cosmic"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239780/+files/cosmic_makedumpfile_1.6.4-2ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Patch added: "debdiff for xenial"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239782/+files/xenial_makedumpfile_1.6.3-2~16.04.1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Debdiffs for this bug were attached to LP#1800562
** Description changed:
[Impact]
Crash kernels do not advise some subsystems to perform a reset by default.
[Description]
Kernel has the "reset_devices" parameter that drivers can opt-in, and perform
special activity in case this param
** Description changed:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
Thanks for bringing that up, Cascardo. That was one scenario we didn't
consider, and you're right about it causing problems for users with
encrypted systems.
It does seem more sensible to just remove the 'nousb' option in this case,
since this parameter has no effect in recent kernels. I'll respi
** Patch removed: "debdiff for disco"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239779/+files/disco_makedumpfile_1.6.5-1ubuntu2.debdiff
** Patch removed: "debdiff for cosmic"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachm
** Description changed:
[Impact]
- Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
+ Crash kernels include an obsolete "nousb" parameter by default, which can
cause confusion since it's been deprecated in newer kernel versions.
[Descriptio
Qemu runs.
** Affects: qemu
Importance: Undecided
Status: Fix Released
** Affects: qemu (Ubuntu)
Importance: Undecided
Assignee: Heitor R. Alves de Siqueira (halves)
Status: Fix Released
** Affects: qemu (Ubuntu Xenial)
Importance: Undecided
Assignee: Heitor
nce: Undecided
Assignee: Heitor R. Alves de Siqueira (halves)
Status: Invalid
** Changed in: qemu (Ubuntu)
Status: Confirmed => Invalid
** Tags removed: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Duplicate of #1818880
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818882
Title:
Deadlock when detaching network interface
To manage notifications about this bug go to:
https://bugs.launchpad.ne
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: cloud-archive
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/1818880
Title:
** Patch added: "Debdiff for xenial"
https://bugs.launchpad.net/cloud-archive/+bug/1818880/+attachment/5244384/+files/xenial.debdiff
** Description changed:
[Impact]
Qemu guests hang indefinitely
[Description]
When running a Qemu guest with VirtIO network interfaces, detaching an
ts: pacemaker (Ubuntu)
Importance: Undecided
Assignee: Heitor R. Alves de Siqueira (halves)
Status: Fix Released
** Affects: pacemaker (Ubuntu Xenial)
Importance: Undecided
Assignee: Heitor R. Alves de Siqueira (halves)
Status: Confirmed
** Tags: sts
**
** Changed in: pacemaker (Ubuntu)
Assignee: Heitor R. Alves de Siqueira (halves) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819046
Title:
Systemd unit file reads setti
** Changed in: qemu (Ubuntu Disco)
Assignee: Heitor R. Alves de Siqueira (halves) => (unassigned)
** Changed in: qemu (Ubuntu Cosmic)
Assignee: Heitor R. Alves de Siqueira (halves) => (unassigned)
** Changed in: qemu (Ubuntu Bionic)
Assignee: Heitor R. Alves de Siqueira (
** Tags added: sts-sponsor
** Patch added: "Debdiff for xenial"
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1819046/+attachment/5244550/+files/xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Description changed:
[Impact]
Systemd Unit file doesn't read any settings by default
[Description]
The unit file shipped with the Xenial pacemaker package tries to read
environment settings from /etc/sysconfig/ instead of /etc/default/. The result
is that settings defined in /etc/d
Patch v2:
Instead of adding the /etc/default location, change all /etc/sysconfig files to
their /etc/default counterpart since the sysconfig folder does not exist in
Debian based distros.
** Patch added: "Debdiff for xenial v2"
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1819046
Patch v2:
Added missing DEP3 info and corrected pkg version
** Patch added: "Debdiff for xenial v2"
https://bugs.launchpad.net/cloud-archive/+bug/1818880/+attachment/5244567/+files/xenial_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Patch removed: "Debdiff for xenial v2"
https://bugs.launchpad.net/cloud-archive/+bug/1818880/+attachment/5244567/+files/xenial_v2.debdiff
** Patch added: "Correct debdiff for xenial v2"
https://bugs.launchpad.net/cloud-archive/+bug/1818880/+attachment/5244568/+files/lp1818880-v2.debdiff
Public bug reported:
[Impact]
apt crashes (core dump) during cache creation
[Description]
When executing apt-cache several times on a memory constrained system,
apt-cache can sometimes crash with a core dump file. This is related to mmap()
failing allocations during cache generation, according
** Description changed:
[Impact]
apt crashes (core dump) during cache creation
[Description]
When executing apt-cache several times on a memory constrained system,
apt-cache can sometimes crash with a core dump file. This is related to mmap()
failing allocations during cache generatio
ete
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Assignee: Heitor R. Alves de Siqueira (halves) => (unassigned)
--
You received this bug notification because you are a mem
SRU request sent to kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2019-February/098444.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815501
Title:
ixgbe: Kernel Oops
66 matches
Mail list logo
