I believe I've nailed this one down, after a day of heads-down testing.
The issue boils down to this bit of code, in /usr/lib/python3/dist-
packages/cmd2.py:
# The extraneous output bug in pyperclip on Linux using xclip was fixed in
more recent versions of pyperclip
if
James/Brian: Can this also be rebuild and SRU'd for Bionic as well?
This is intended to be a transitional step from Bionic/Ussuri to
Focal/Ussuri for $CUSTOMER, and they need to validate against their
existing env (Bionic) before moving to Focal with the same Ceph surface.
Thanks!
--
You
Disregard the previous, I was on the wrong local branch. This is _not_
fixed upstream, but this small patch adds the missing functionality to
make this work:
```
diff --git a/sos/policies/ubuntu.py b/sos/policies/ubuntu.py
index 8ec765e4..2b913669 100644
--- a/sos/policies/ubuntu.py
+++
This appears to be fixed in upstream github master branch. There are
varying levels of issues with DAV on nginx accepting the PUT over SSL
from sosreport, but that's unrelated to sosreport itself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
The current versions of sosreport (3.9 on Bionic and 4.0 on Focal) do
not appear to support passing the --upload-url to a non-Canonical URL,
for example a LAN-side host to collect those sosreports.
sudo sosreport --batch -o pci --upload --upload-
We've extensively tested rabbitmq-server 3.8.2 from Eric's PPA on an
existing, cleanly-built Bionic/Rocky OpenStack cluster and hammered it
with multiple concurrent VM builds, deletes and live-migrations between
compute hosts.
We also ran a full Rally suite against it with no errors or failures
Public bug reported:
This bug is easy to reproduce with the default configuration:
Install bird, 1.6.3-3 for example and start the service with the
defaults values. This will create and start the services to run as the
'bird' user and 'bird' group (BIRD_RUN_USER, BIRD_RUN_GROUP)
system(1) will
Just a quick heads-up that maas 2.6.0 (2.6.0-7802-g59416a869-0ubuntu1
from main) doesn't install nor run on Focal either, for the exact same
reason.
Adding group `bind' (GID 121) ...
Done.
Adding system user `bind' (UID 115) ...
Adding new user `bind' (UID 115) with group `bind' ...
Not creating
This is totally non-functional for those who don't run a GNOME 3
desktop, but have GNOME apps installed, such as gnome-todo + the todoist
extension.
Clicking on the button to add the todoist account inside gnome-todo,
does absolutely nothing. No error, no log entry, nothing except a button
Public bug reported:
When using v3.6 of sosreport and creating a sosreport with the default
values, for example an hourly sosreport that is created via cron, using
a syntax like the following:
sosreport --batch -a --all-logs -z xz -t 16 --verify --label hourly
The '--label' option here
I can also confirm that this happens for _some_ searches, while others
do produce results, although not entirely correct results. This looks to
be some regex fragility.
Review the following, for example, using apt-file 3.2.2 on Eoan:
$ dpkg -S $(which joe); apt-file search joe; echo $?
joe:
Public bug reported:
[impact]
This was discovered at a customer site and affects all of their Bionic
installs that have Micron NVME drives.
The version of nvme-cli present in Ubuntu 18.04 Bionic Beaver (1.5-1)
does not include support to manage updating the firmware on Micron NVME
drives.
$
Just adding that I've worked around this issue with the following added
to the lvm2-monitor overrides
(/etc/systemd/system/lvm2-monitor.service.d/custom.conf):
[Service]
ExecStartPre=/bin/sleep 60
This results in 100% success for every single boot, with no missed disks
nor missed LVM volumes
This manifests itself as the following, as reported by lsblk(1). Note
the missing Ceph LVM volume on the 6th NVME disk:
$ cat sos_commands/block/lsblk
NAME
MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda
Correction to my last comment (listen-on, not listen):
listen-on { !10.224.138.0/24; };
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd-bridge.service when MAAS is
Adding these two lines (specifically the second line) to
/etc/bind/named.conf.options and restarting bind, should solve this for
you:
listen-on-v6 { none; };
listen { !10.224.138.0/24; };
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Can confirm, NOT a hardware problem. Happens immediately after a bionic
install and update:
$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 6 not
Public bug reported:
Get:66 http://us.archive.ubuntu.com/ubuntu bionic-backports/universe amd64
DEP-11 Metadata [5,100 B]
Get:67 http://us.archive.ubuntu.com/ubuntu bionic-backports/universe DEP-11
64x64 Icons [1,789 B]
Can confirm, this also affects:
nvidia-settings; 396.18-0ubuntu0~gpu16.04.1
nvidia-390.48
Xenial 16.04.4 LTS
I have tried every NVIDIA driver from 390.48 direct from NVIDIA all the
way back to 304 from 'main' and the graphics PPA, all with 100% failure
correctly identifying or using my LCD panel
** Changed in: openssl (Ubuntu)
Importance: Low => Medium
** Changed in: openssl (Ubuntu)
Status: New => Triaged
** Changed in: openssl (Ubuntu)
Milestone: None => ubuntu-16.04.2
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You
*** This bug is a duplicate of bug 762964 ***
https://bugs.launchpad.net/bugs/762964
I can confirm this affects (minimally) the last 5 or so kernels in
Xenial on a Dell Precision 7510, where it worked before up to the recent
4.4.x kernel series.
The workaround specified in #2 does not work
This issue also affects attempting to run Firefox natively from within a
clean, xenial/amd64 UCA image from Cloud Archive, with the same errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550983
Doesn't adding "net.ifnames=0 biosdevname=0" to your kernel boot line
fix this for you? It will stop udev from creating the longer-than-
desired names.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This is very similar to bug #1428674, but slightly different, and easily
reproduced. With a solution below!
When creating cloud images using 'uvt-kvm create myvm', it will
incorrectly assert that the 'default' network is on vibr0, and when the
VM boots, net-dhcp-leases will
If you're unable modify your system's packages by installing patched
.deb packages or changing your default repositories to include
-proposed, you can use the following command:
sysctl -w kernel.pid_max=9
To make this permanent, you'll need to add the following line to
/etc/sysctl.conf:
25 matches
Mail list logo
