Public bug reported:
I'm trying to disable FIPS from an Ubuntu Pro FIPS 18.04 image in AWS. I
updated to the latest ua client in the daily PPA. I have a prompt to
disable it but it fails:
ubuntu@ip-172-31-60-238:~$ sudo add-apt-repository ppa:canonical-server
/ua-client-daily
ubuntu@ip-172-31-6
wrong project
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916773
Title:
ua disable fips doesn't work in ua client 27
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
Josh gave this answer to Marcello's question "Just to confirm. It's not
necessary to include these config changes to the 4.13 azure kernel in
xenial, correct?":
--> 'No, this is upcoming new hardware in Azure and I'd prefer to keep
new feature work in 4.15.'
--
You received this bug notification
I have confirmation that the kernel in -proposed fixes the issue in
xenial.
** Tags removed: verification-needed-xenial
** Tags added: 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
I have confirmation that the kernel in -proposed fixes the issue in
xenial.
** Tags removed: verification-needed-xenial
** Tags added: 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
There is a similar situation where apt-get wants to remove packages when
strict dependencies (equal version number) cannot be met. For example
dovecot-core/dovecot-pop3d/dovecot-imapd.
After installing Ubuntu 16.04.3 LTS from the ISO, install the 3 packages
from the release pocket:
$ sudo apt ins
** 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/1793430
Title:
Page leaking in cachefiles_read_backing_file while vm
@Guillaume: I am Eric's colleague from comment #21. I was able to
reproduce the issue in Azure with your reproducer in comment #5. I'll
show Eric how I reproduced the issue and he'll be able to follow up with
you. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bu
I tested friendly-recovery 0.2.31ubuntu2 in Xenial/16.04.3 LTS.
Selecting network Enable networking" from the Recovery Menu now enables
the network and DNS successfully. I can "cat /etc/resolv.conf" vs before
I couldn't. I don't see any issues with dependencies or asking for tty-
ask-password or a
I tested the new package ubiquity 2.21.63.9 from xenial-proposed with
Ubuntu 16.04.3 and confirm the Cancel button on the select language
screen now reboots the system. I tested multiple times and ended up
doing a full real OEM install without any issues.
** Tags removed: verification-needed-xenia
I tested the package cloud-init 0.7.5-0ubuntu1.23 from trusty-proposed
and confirm it works as expected.
# TEST KEYS
$ cat googlekeys
test:ssh-rsa [...]+1LRl t...@example.com
ubuntu:ssh-rsa [...]+2LRl t...@example.com
cloudinit:ssh-rsa [...]+3LRl test
# CREATE THE INSTANCE
$ gcloud
I have a user who confirms the 4.15.0-39 kernel fixes this issue:
# uname -a
Linux 4.15.0-39-generic #42~16.04.1-Ubuntu SMP Wed Oct 24 17:09:54
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
# cat /proc/fs/fscache/stats
FS-Cache statistics
Cookies: idx=2 dat=283731 spc=0
Objects: alc=278557 nal=0 avl
Hi Guillaume, would it be possible to provide step-by-step instructions
to reproduce this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796376
Title:
Bug #1739107 fix causes linux-cloud-tool
Hi Eric,
I confirm with the sosreport in ppa:slashd/lp1775195 I no longer see the
passwords anymore:
# grep password
sosreport-xeniallandscape-20181114150420/etc/landscape/service.conf
password = []
password = []
store_password = []
I couldn't find any other issues with
I upgraded walinuxagent to version 2.2.32-0ubuntu1 (from -proposed) on 4
instances (trusty, xenial, bionic and cosmic). I rebooted the 4
instances and verified the serial console still works for each one. I
didn't run additional tests. Maybe the Azure team has more in-depth
automated tests they can
I also noticed walinuxagent in Ubuntu 18.10 (cosmic) installed the
python3-distro dependency when upgrading the walinuxagent package (which
was expected).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I can reproduce the issue in Azure with Ubuntu 18.04 and the kernel
linux-azure-edge 4.18.0.1004.5 from bionic-proposed.
I use an instance of type "Standard F4s_v2 (4 vcpus, 8 GB memory)"
I launch the instance and get the 4.15.0-1030-azure kernel:
$ lsb_release -a
No LSB modules are available.
D
Hi Chris. I spoke to Joseph and I think we have everything we need to
start the bisect. We'll get started and keep you posted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794477
Title:
Accelerate
Hi Joseph,
Is there a special way I should install these? I tried:
sudo dpkg -i *
But I get:
Selecting previously unselected package linux-azure-cloud-tools-4.17.0-1001.
(Reading database ... 56547 files and directories currently installed.)
Preparing to unpack
linux-azure-cloud-tools-4.17.0-1
These are the packages I see installed out of the box in the instance:
ubuntu@lp1794477:~/41701001$ dpkg -l | grep 4.15.0-1030.31 | sort
ii linux-azure-cloud-tools-4.15.0-1030 4.15.0-1030.31
amd64Linux kernel version specific cloud tools for version
4.15.0-
I can see the Mellanox devices with that 4.17.0-1001-azure kernel.
I installed the new kernel:
sudo dpkg -i linux-
modules-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb linux-
modules-extra-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb linux-
image-unsigned-4.17.0-1001-azure_4.17.0-10
4.18.0-1001:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1001-azure #2~lp1794477 SMP Wed Nov 21 16:06:45 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.701988] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.730013] mlx4_ib_add: mlx4_ib:
4.18.0-1002:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1002-azure #3~lp1794477 SMP Wed Nov 21 16:41:12 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.723350] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.751281] mlx4_ib_add: mlx4_ib:
4.18.0-1003:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1003-azure #4~lp1794477 SMP Wed Nov 21 18:32:18 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.701478] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.732267] mlx4_ib_add: mlx4_ib:
4.18.0-1004:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1004-azure #5~lp1794477 SMP Wed Nov 21 19:19:16 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[6.009608] mlx4_core: Mellanox ConnectX core driver v4.0-0
[6.045063] mlx4_ib_add: mlx4_ib:
bionic-tree/4.18.0-1004:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1004-azure #4~18.04.1 SMP Wed Nov 21 20:07:48 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[6.337786] mlx4_core: Mellanox ConnectX core driver v4.0-0
[6.374260] mlx4_ib_add
bionic-tree/4.18.0-1004 with all the packages:
$ sudo dpkg -i
linux-modules-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64.deb \
linux-modules-extra-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64.deb
\
linux-image-unsigned-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64
Hi Marcelo,
Maybe I'm doing something wrong but I still don't see the Mellanox
devices with this 4.18.0-1005 kernel from the CKT PPA:
ubuntu@lp1794477:~$ sudo add-apt-repository ppa:canonical-kernel-team/ppa
ubuntu@lp1794477:~$ sudo apt install linux-azure-edge
ubuntu@lp1794477:~$ sudo update-gru
Public bug reported:
The new Minimal Ubuntu 18.10 image has iptables test failures in Azure
because iptables isn't present in the Minimal image.
This is a request to add a dependency to iptables in the walinuxagent
package.
** Affects: walinuxagent (Ubuntu)
Importance: Undecided
St
Ran test in Xenial LXD container:
# dpkg -l | grep sosreport
ii sosreport3.6-1ubuntu0.16.04.1
amd64Set of tools to gather troubleshooting data from
a system
# apt-cache policy sosreport
sosreport:
Installed: 3.6-1ubuntu0
Hi Ivan, the best way to engage Canonical Support to get assistance with
this issue will be to file a support case on support.canonical.com and
attach an sosreport of the affected system that is collected when the
issue happens. See my previous comment #5 for the details of sosreport.
Please check
Marking bug as Invalid since this looks like this might have been
related to the South Central US datacenter outage.
** Changed in: python3-stdlib-extensions (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@Corey, I'm sorry the deployment I had was in bionic only. Can you queue
it up on your side?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750384
Title:
Cannot Delete Recordset / Zone in ng_dns pan
I tested python-designate-dashboard version 6.0.0-0ubuntu1.2 from
bionic-proposed on Ubuntu 18.04.3 LTS and I confirm I can delete the DNS
zone successfully now.
ubuntu@juju-96d97f-22-lxd-14:~$ grep proposed /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu/ bionic-proposed restricted mai
subscribed ~field-medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750384
Title:
Cannot Delete Recordset / Zone in ng_dns panels
To manage notifications about this bug go to:
https://bugs.laun
I just found out about this. I wanted to get rid of the screen tearing
that I observed on my Nitro AN515-53 laptop running Ubuntu 18.04.3 LTS
with NVIDIA GeForce GTX 1050 Mobile GPU.
I used https://askubuntu.com/a/020 and set nvidia_drm modeset=1 but
then my external monitors didn't work after
I just hit this issue with an Ubuntu 20.04 daily build. I noticed it
when I tried to split my Terminator shell. I used ibus-setup to change
the emoji shortcut to something else.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
On the running system after you rollback to the previous kernel, can you
paste your /etc/fstab for the filesystems that failed to mount and the
corresponding lines from mount -v? I assume the issues are with nfshome
and officeshare:
cat /etc/fstab | grep -i -e nfshome -e officeshare -e office_shar
I forgot to mention that I was still able to reproduce the bug with the
kernel you built with a revert of commit ff467fd from
http://kernel.ubuntu.com/~jsalisbury/lp1737033
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Hi Joseph,
I'm able to reproduce Benjamin's original issue with kernel
4.4.0-103-generic #126-Ubuntu:
# mount -t ceph :6789:/ /mnt/mycephfs -o name=admin,secret=
mount error 5 = Input/output error
I don't get this problem with 4.4.0-101-generic #124-Ubuntu. I'm working
with Jay Vosburgh to test
I tested a kernel without the following commits from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728739 and I was
able to mount the CephFS filesystem successfully:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/commit/?id=f14ca6ac3b198f30ee138f02c3c7d380d165736e
http://kernel.ub
FYI, this patch seems to have introduced a regression, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737033
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728739
Title:
Attempt to map rb
I also confirm the kernel 4.4.0-104.127 in xenial-proposed fixes the
issue. I am able to mount my CephFS filesystem normally. Benjamin also
confirmed the kernel works for him in comments #26 and #27. I am
changing the tag to verification-done-xenial. Thanks!
** Tags removed: verification-needed-xe
I tested this in a VM using the default xenial cloud image (ie. "uvt-kvm
create xenialoem release=xenial").
With the current nvidia-384 384.90-0ubuntu0.16.04.2 package, the nvidia
dkms module doesn't get built after the reboot:
$ sudo apt update
$ sudo touch /tmp/do_not_build_dkms_module
$ sudo a
My last comment #5 still stands. My tests show that this fix works for
the cloud image of Ubuntu, but there are use cases where users need the
nvidia drivers for GPU processing but are not running a display manager
on the machine. In such a case, the display-manager.service systemd
service will not
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-failed verification-failed-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732206
Title:
nvidia-grap
Public bug reported:
This is a request to make a change in the hv-kvp-daemon systemd service
which is part of the linux-cloud-tools-common package to ensure the hv-
kvp-daemon service starts before the walinuxagent service. The default
dependencies make hv-kvp-daemon wait until the whole system is
** Also affects: snapd (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/1721518
Title:
Latest snapd in Trusty is broken after reboot because of syst
Marked as Fix Released. I tested this on snapd 2.29.4.2~14.04 and works
as expected.
** Changed in: snapd
Status: Fix Committed => Fix Released
** Changed in: snapd (Ubuntu Trusty)
Status: New => Fix Released
** Changed in: snapd (Ubuntu)
Status: New => Fix Released
--
You
@Marcelo, Josh requested that these patches be backported to the 4.13
azure kernel:
"[...]Since 4.13 needs to be the default until the 26th, could we get
them added to the 4.13 kernel?"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
nouveau driver updates causing problems with other kernels with
provisioning on GPU instances in Azure.
This is a request to disable the nouveau driver from the linux-azure
kernel.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You rece
Subscribed Canonical Kernel Distro Team to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763456
Title:
Disable nouveau driver in linux-azure kernel
To manage notifications about this bug
I confirm this issue still exists when doing a PXE netboot of Ubuntu
16.04 Desktop and also with a PXE netboot of an Ubuntu 18.04 LTS (Bionic
Beaver) Desktop Daily Build.
I also use the workaround to comment out the all the interfaces in
/etc/network/interfaces except the loopback adapter and the
Public bug reported:
When doing a PXE netboot of Ubuntu Desktop over NFS, the installer adds
the following lines for each network interface to
/etc/network/interfaces (I think this is to keep the root fs available
during the live session):
auto ens3
iface ens3 inet manual
I was able to repro
** Attachment added: "netboot-pxe-issue.png"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1750597/+attachment/5059018/+files/netboot-pxe-issue.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Attachment added: "netboot-pxe-issue-after-workaround.png"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1750597/+attachment/5059019/+files/netboot-pxe-issue-after-workaround.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I have information that the original Desktop team confirmed that
limiting the themes available via the Appearance panel was a design
choice. They decided to create a "whitelist" of themes known to look in
an acceptable way.
I don't think this will change in Unity in the future. I suggest we
close
I also confirm I tested the new gnome-themes-standard and gnome-
accessibility-themes packages from -proposed in artful and xenial and it
fixes the issue with the missing icons.
xenial:
gnome-themes-standard | 3.18.0-2ubuntu2
gnome-accessibility-themes | 3.18.0-2ubuntu2
artful:
gnome-themes-stand
Public bug reported:
Using an Ubuntu Server 16.04-based host with KVM hypervisor installed,
we are unable to launch a vanilla Ubuntu Server 16.04.4 guest with >= 32
PCIe devices. It is 100% reproducible. Using fewer PCIe devices works
fine. We are using the vanilla kvm and qemu packages from the C
** Changed in: qemu (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769053
Title:
Cannot start a guest with more than 1TB of RAM
To manage notifications
** Changed in: qemu (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771238
Title:
Not able to passthrough > 32 PCIe devices to a KVM Guest
To manage notifica
** Changed in: qemu (Ubuntu)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771238
Title:
Not able to passthrough > 32 PCIe devices to a KVM Guest
To manage notific
I removed upstream QEMU from this bug pending further analysis and so we
can go through the right channels if this needs to go upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771238
Title:
@Khaled El Mously: It's more a feature request.
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771238
Title:
Not able to passthrough > 32 PCIe devices to a KVM Guest
To
I tested the test package for Xenial in ppa:dgadomski/ubiquity-lp1749289
and it gives me a choice instead of failing now. After pressing Cancel
on the first screen, I get:
Your system is not yet configured. Press 'a' to try again, 's' for a recovery
shell, or 'r' to reboot.
[asr]
I did an OEM in
@Tomasz: The d-i based install image is "the traditional installer found
on the alternative downloads page" as you can read from the Download
Ubuntu Server 18.04 page[1][2][3]:
Alternative Ubuntu Server installer
If you require advanced networking and storage features such as; LVM, RAID,
multipat
We're seeing a new issue with cloud-init 19.2.36 failing with python
exception "Not all expected physical devices present ..." during bionic
image deployment from MAAS. The issue seems to happen when bonds are
used. Tagged this SRU with regression-update.
See https://bugs.launchpad.net/cloud-init/
As an FYI, my workaround for this is to grab the squasfh file from
https://images.maas.io/ephemeral-v3/daily/bionic/amd64/20190930/ and
copy it over the file /var/lib/maas/boot-
resources/current/ubuntu/amd64/ga-18.04/bionic/daily/squashfs on my MAAS
nodes (assuming you deploy Ubuntu 18.04 with the
@darmadoo: The cloud-init package is baked into the cloud images that
MAAS uses to deploy instances. You have to wait for the next cloud image
that will contain this fixed cloud-init, or you can use the workaround
in my comment #16 to use a previous image in the meantime.
--
You received this bug
Public bug reported:
When trying to launch an instance in OpenStack Queens on Ubuntu 18.04
with the new kernels, this error happens:
Error: Failed to perform requested operation on instance "david", the
instance has an error status: Please try again later [Error: Exceeded
maximum number of retrie
** Description changed:
When trying to launch an instance in OpenStack Queens on Ubuntu 18.04
with the new kernels, this error happens:
Error: Failed to perform requested operation on instance "david", the
instance has an error status: Please try again later [Error: Exceeded
maximum n
Subscribed ~field-medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853200
Title:
cpu features hle and rtm disabled for security are present in
/usr/share/libvirt/cpu_map.xml
To manage notifi
** Tags added: cpe-onsite
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794307
Title:
docker login fails Cannot autolaunch D-Bus without X11
To manage notifications about this bug go to:
https://b
Yes this works as expected now.
Only the esm-apps service as an impact on the "are receiving/could
receive security updates with ESM Apps" statement now, and the message
changes as expected depending on if esm-apps is enabled or disabled.
Thank you.
--
You received this bug notification because
** Attachment added: "Suggested flowchart of how the decision to reboot should
be when using livepatch"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1747499/+attachment/5390197/+files/livepatch-flowchart-davecore-suggestion.png
--
You received this bug notification because
Thanks @brian-murray. However it doesn't look like it fixed it, it seems
to be even worse now. It doesn't tell me I am getting the security
updates when I have ESM-apps enabled:
ubuntu@ip-172-31-55-253:~$ bzr branch lp:~brian-murray/update-manager/u-s-s-new
ubuntu@ip-172-31-55-253:~$ cd u-s-s-new/
Public bug reported:
Installing python3-distro-info on Ubuntu 16.04 breaks the ubuntu-
security-status script.
The script runs before I install python3-distro-info:
ubuntu@ip-172-31-14-142:~$ ./ubuntu-security-status --universe
473 packages installed on Ubuntu 16.04 LTS, of which:
2 packages a
Public bug reported:
It looks like ubuntu-security-status assumes that ESM Apps is enabled
when only ESM Infra is enabled.
There is no problem with ESM Apps and ubuntu-security-status. It's just
that it looks like ESM Infra gives a false positive about receiving the
updates.
Reproducer with an
Here are some extra details about the status of livepatch when a kernel
upgrade is required.
I am running an 18.04 VM with an old 4.15.0-20-generic kernel from April
2018. Here is status in yaml format:
ubuntu@bioniclivepatcholdkernel:~$ canonical-livepatch status --format yaml
client-version: 9.
[VERIFICATION BIONIC]
I can modprobe the mq-deadline, kyber and bfq schedulers but it looks
like doing a modprobe of the cfq and deadline schedulers doesn't list
them as choices in the available schedulers:
# uname -r
4.18.0-1009-azure
# modprobe bfq
# modprobe cfq-iosched
# modprobe mq-deadline
@lazamarius1: Just to clarify, the fix is scheduled to go in the 4.15
kernel in Bionic which is the same kernel as the Xenial HWE kernel. So
there's no need to add anything to the Affects section. You will see a
new linux-hwe 4.15 kernel in xenial-proposed once this is ready to test.
Thanks!
--
Y
Public bug reported:
Host changes have altered how the PCI GUID is presented to the guest and
the patches for PCI IDs in 4.15.0-1037 do not properly handle the new
condition.
Impact:
Instances with multiple GPUs are only seeing one.
Workaround:
4.15.0-1036 does not have this behavior.
Additiona
Public bug reported:
This is a request to enable CONFIG_NO_HZ_FULL=y in the linux-azure
kernels(currently 4.15 and 4.18) in order to increase NVME disks
performance.
The current CONFIG_NO_HZ configuration in linux-azure kernels is the
following (tested on 4.15.0-1037, 4.15.0-1039 and 4.18.0-1011)
Public bug reported:
The InfiniBand configuration settings from the 4.15 linux-azure kernel
are not in the 4.18 linux-azure kernel.
This is a request to apply the same InfiniBand settings to the 4.18
linux-azure kernel.
The following settings are only in the 4.15 linux-azure kernel (tested
with
Hi Corey, I don't have access to a Disco cloud to test. Can we still get
this fix in stein? This is a blocker for a customer deployment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808951
Title:
Hi Corey, I don't have access to a Disco cloud to test. Can we still get
this fix in stein? This is a blocker for a customer deployment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826875
Title:
subscribed ~field-medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835354
Title:
disco: ceph-mgr unable to load crash module under py3
To manage notifications about this bug go to:
https://bug
We're seeing this with ceph 13.2.6 on bionic with the stein cloud
archive
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835354
Title:
disco: ceph-mgr unable to load crash module under py3
To manag
Tested packages from stein-proposed on ceph-mon units:
BEFORE:
root@juju-1101fd-18-lxd-0:~# ceph -s
cluster:
id: 832cb0a6-a3e7-11e9-bedc-00163e7eca36
health: HEALTH_WARN
Module 'crash' has failed dependency: invalid syntax (module.py,
line 48)
[...]
root@juju-1101fd-18
I confirm the package in stein-proposed fixes the issue.
** Tags removed: verification-stein-needed
** Tags added: verification-stein-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808951
Title:
I also have verified that this fix works on bionic-stein, removing the
verification-stein-needed tag.
** Tags removed: verification-stein-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826875
I subscribed field-critical to this bug as this is affecting a customer
deployment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826875
Title:
[stein] 'Percona-XtraDB-Cluster prohibits use of DML
I subscribed field-critical to this bug as this is affecting a customer
deployment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808951
Title:
python3 + Fedora + SSL + wsgi nova deployment, nova a
Unsubscribed field-critical since there's a workaround to use package in
stein-proposed and fix seems to be on the way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826875
Title:
[stein] 'Percona-
I tested the systemd 229-4ubuntu21.11 package from xenial-proposed in
Ubuntu 16.04 in KVM and also confirm I cannot reproduce the issue with
this updated package:
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.5 LTS
Release:16.04
Codename
Public bug reported:
There was a previous request in bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
the IO scheduler to NOOP in linux-azure. The other schedulers were
turned off and NOOP was made the default.
However with new upstream releases, new schedulers where adde
Netbooting Ubuntu Desktop is not a supported installation method for
Ubuntu. The only supported way to install Ubuntu via netboot is with the
Netboot images of Ubuntu[1]. More information in the Ubuntu
documentation[2].
[1] http://cdimage.ubuntu.com/netboot/
[2] https://help.ubuntu.com/community/I
** Description changed:
+ [Impact]
+
Pressing Cancel during Ubuntu 16.04.3 Server installation after OEM
install and after running oem-config-prepare aborts the installation.
The behaviour is different from a regular Ubuntu 16.04.3 Server
installation (without OEM) where the option at
Hi Ivan. Can you post steps to reproduce this issue? Or at least steps
to get a similar environment running to get familiar with this bug? (for
those who are not familiar with HDInsight). Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Ivan. I'll have to learn about HDInsight then. I was hoping to get a
list of steps I can follow to fast track the learning process. I'll see
what I can do this week. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
1 - 100 of 170 matches
Mail list logo
