** Also affects: grub2 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Confirmed
** Also affects: grub2 (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
So testing with Fedora's boot/efi/EFI/fedora/grubx64.efi in place of the
Ubuntu version solves the problem.
So it is indeed the situation that you describe in comment #15
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi xnox,
Thanks for the reply. I'll test both options and report to you here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955655
Title:
kernel-5.13.0-23-generic : Unable to boot when Secure
Recent tests with the most recent 5.15 kernel (5.15.0-25-generic) do
display the same problem, though the symptom is different.
Booting w/o the swiotlb=262144 leads to the boot sequence stopping after
these messages :
[1.376749] i2c i2c-0: Memory type 0x07 not supported yet, not
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956575
Title:
[Regression] Focal kernel 5.4.0-92.103 fails to boot
Here is the result of a similar bisect on the bionic kernel :
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/commit/?id=091554e4a5b2a7647830a1c7beea781148b51509
091554e4a5b2a7647830a1c7beea781148b51509 is the first bad commit
commit 091554e4a5b2a7647830a1c7beea781148b51509
Hello @kmously, yes I am able to reproduce the same panic on 4.15.0-166.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956575
Title:
[Regression] Focal kernel 5.4.0-92.103 fails to boot when
According to the following advisory[1] from HP, this is a known issue
which is fixed upstream :
"Advisory: Red Hat Enterprise Linux 8.3 - Guest Stops Responding at
efi_mokvar_sysfs_init+0xa9/0x19d with AMD Secure Encrypted
Virtualization (SEV) Enabled"
The upstream fix cited in the article is
** Description changed:
The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot
when SEV is enabled.
The kernel panics with the following backtrace :
[1.531125] ledtrig-cpu: registered to indicate activity on CPUs
[1.531760] EFI Variables Facility v0.08
Details of the bisected commit :
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
focal.git/commit/?id=5f79bc17fd8d078378a9f3c8773ebcb506cb6f40
Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert
lists that aren't present."
BugLink: https://bugs.launchpad.net/bugs/1932029
Public bug reported:
The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot
when SEV is enabled.
The kernel panics with the following backtrace :
[1.531125] ledtrig-cpu: registered to indicate activity on CPUs
[1.531760] EFI Variables Facility v0.08 2004-May-17
[
Hello,
The kernel panic occurs very early in the boot sequence, even before the root
fs is mounted to capture the log. Here is the kenrel backtrace :
[1.251773] Kernel panic - not syncing: Can not allocate SWIOTLB buffer
earlier and can't now provide you with the DMA bounce buffer
[
As a complement of information, here are the messages pertaining to the
TLB during the log :
$ grep -i tlb swiotlb_crash.out
[0.003802] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
[0.037784] kvm-guest: KVM setup pv remote TLB flush
[0.040674] software IO TLB:
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1955655/+attachment/5549376/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955655
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1955655/+attachment/5549375/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955655
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1955655/+attachment/5549374/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955655
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1955655/+attachment/5549373/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955655
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1955655/+attachment/5549372/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1955655/+attachment/5549371/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1955655/+attachment/5549370/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955655
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1955655/+attachment/5549369/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955655
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1955655/+attachment/5549368/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955655
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1955655/+attachment/5549367/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
While investigating LP: #1955395 by using the -generic kernel image, it
appeared that it is impossible to boot the kernel unless the boot
parameter swiotlb is set to 512M (swiotlb=262144).
Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb it
fails and
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1955395/+attachment/5548709/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955395
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1955395/+attachment/5548710/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955395
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1955395/+attachment/5548708/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955395
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1955395/+attachment/5548707/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955395
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1955395/+attachment/5548706/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1955395/+attachment/5548705/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1955395/+attachment/5548704/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955395
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1955395/+attachment/5548703/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955395
apport information
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => Confirmed
** Tags added: apport-collected uec-images
** Description changed:
Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm flavor
of the kernel does not boot on a QEMU server with Secure
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1955395/+attachment/5548702/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955395
Title:
KVM
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+attachment/5548694/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955395
Title:
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+attachment/5548693/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955395
Public bug reported:
Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm flavor
of the kernel does not boot on a QEMU server with Secure Encrypted
Virtualization( SEV) enabled.
Using the same kernel without the -kvm optimisation does boot correctly
** Affects: linux (Ubuntu)
** 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
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
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
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
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
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.
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
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:~#
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
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
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
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
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
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
-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
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.
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
>
Public bug reported:
On Bionic, Qemu complains that it cannot acquire write lock when
commiting a snapshot if a read-only backing-store is opened by another
qemu process. This behavior does not happen with version 2.12 in Cosmic.
Reproducer
==
Create two QCOW2 containers sharing the same
For Info, I'm repearing an SRU upload for Bionic hopefully available by
End Of Day
** Description changed:
[Impact]
Log noise due to needless restart of resolved on lease expiry, maybe loss of
cached state?
+ Application that require Name Resolution may fail while the service is being
** 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 notificatio
** 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:
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
** 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
** 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.
** 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
** 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 syst
** 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 i
** 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.
** Summary changed:
- 18.04: Raid5 performances on kernel 4.15 are suboptimal
+ 18.04: Raid performances on kernel 4.15 and newer are suboptimal when used on
NVMe devices
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815178
Title:
18.04: Raid5 performances on kernel 4.15 are suboptimal
To manage
Public bug reported:
Hello,
We have been running multiple tests using the md driver to build various type
of RAID devices. Performances on RAID5 are particularly disappointing so we
would like to know if there are any known issue with the md driver on Bionic
kernels. Here are some of our
emu (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 =>
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:
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
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
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
Public bug reported:
The linux-crashdump meta-package should be enabled for arm64 now that
kdump-tools & makedumpfile are enabled for this architecture
** Affects: linux-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
Hello,
I would like to add that triggering a kernel dump in seconds following
the installation of the package remains a corner case in a test context
and not the usual behavior.
I have seen that too in my test scripts and syncing right after the
installation fixed the issue as well.
Bringing in
** Also affects: makedumpfile (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Bionic)
Importance: High
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: In Progress
** Also affects: makedumpfile (Ubuntu Xenial)
*** This bug is a duplicate of bug 1635597 ***
https://bugs.launchpad.net/bugs/1635597
This bug is a duplicate of bug #1635597.
As outlined in the other bug, could you test the potential fix in the
following PPA :
ppa:louis/kdump-tools-multipath
** This bug has been marked a duplicate of
Hello,
Would it be possible to test a potential fix in the following PPA :
ppa:louis/kdump-tools-multipath
I do not have the hardware to fully test a kernel dump but the partial
test I have confirm that the modules are correctly loaded.
Please let me know the outcome of you tests whenever
New
** Changed in: linux (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux (Ubuntu Zesty)
Status: New => Invalid
** Changed in: makedumpfile (Ubuntu Trusty)
Assignee: (unassigned) => Louis
** Also affects: kexec-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: kexec-tools (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects:
** Changed in: kexec-tools (Ubuntu)
Assignee: Nish Aravamudan (nacc) => Louis Bouchard (louis)
** Changed in: makedumpfile (Ubuntu)
Assignee: Nish Aravamudan (nacc) => Louis Bouchard (louis)
** Changed in: kexec-tools (Ubuntu)
Status: Confirmed => Invalid
*
Hello,
Well, this is to be expected as the postinst script will only change the
target of the symlink if the architecture is ppc64EL and not ppc64LE (
EL != LE).
Now if both are interchangeable (I must admit my ignorance of this
architecture), I don't mind fixing the script to apply to both EL
** Changed in: makedumpfile (Ubuntu)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: makedumpfile (Ubuntu Wily)
Assignee: Louis Bouchard (louis) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: crash (Ubuntu Xenial)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: Louis Bouchard (louis) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** 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/1366103
Title:
sosreport doesn't collect all data f
** 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/1356211
Title:
cannot collect rotated syslo
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: makedumpfile (Ubuntu Trusty)
Assignee: Louis Bouchard (louis) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: sosreport (Ubuntu Trusty)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: sosreport (Ubuntu Xenial)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: sosreport (Ubuntu Yakkety)
Assignee: Louis Bouchard (louis) => (u
** Changed in: sosreport (Ubuntu)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: sosreport (Ubuntu Trusty)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: sosreport (Ubuntu Xenial)
Assignee: Louis Bouchard (louis) => (unassigned)
*
** Changed in: python2.7 (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/1638695
Title:
Python 2.7.12 performance regression
To man
** Changed in: clamav (Ubuntu)
Status: In Progress => Fix Released
** Changed in: clamav (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.launchp
** Changed in: sosreport (Ubuntu Trusty)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: sosreport (Ubuntu Xenial)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: sosreport (Ubuntu Yakkety)
Assignee: Louis Bouchard (louis) => (u
** 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/1614052
Title:
SOSREPORT need to collect OPAL msglog
To manage notifications
** Changed in: unattended-upgrades (Ubuntu Xenial)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: unattended-upgrades (Ubuntu Yakkety)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: unattended-upgrades (Ubuntu Zesty)
Assignee: Louis Bo
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
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
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
** 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
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:
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
1 - 100 of 1690 matches
Mail list logo
