[Bug 1945661] Re: openstack commands fail with GTK3 error
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 sys.platform.startswith('linux') and pyperclip_ver < 1.6:
# Avoid extraneous output to stderr from xclip when clipboard is empty
at cost of overwriting clipboard contents
pyperclip.copy('')
else:
# Try getting the contents of the clipboard
_ = pyperclip.paste()
Specifically that last line: `_ = pyperclip.paste()`, which assumes a
clipboard exists and has been initialized. In most cases, it has
not/will not be.
The attached diff to cmd2.py will allow these commands to succeed. I
initially added some debug to allow me to see if the clipboard was
accessible or not, and that's how I found this.
Let me know if this is sufficient to SRU into the python3-cmd2 package
to address this.
** Patch added: "cmd2-diff.patch"
https://bugs.launchpad.net/ubuntu/+source/python-openstackclient/+bug/1945661/+attachment/5761586/+files/cmd2-diff.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945661
Title:
openstack commands fail with GTK3 error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-openstackclient/+bug/1945661/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964802] Re: [SRU] ceph 15.2.16
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964802 Title: [SRU] ceph 15.2.16 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1964802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901786] Re: upload options do not support local SSL urls nor self-signed certificates
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 +++ b/sos/policies/ubuntu.py @@ -3,7 +3,6 @@ from sos.policies.debian import DebianPolicy import os - class UbuntuPolicy(DebianPolicy): distro = "Ubuntu" vendor = "Canonical" @@ -62,8 +61,10 @@ class UbuntuPolicy(DebianPolicy): return self.get_upload_url() def get_upload_url(self): +fname = os.path.basename(self.upload_archive) +if self.commons['cmdlineopts'].upload_url: +return self.commons['cmdlineopts'].upload_url + fname if not self.upload_url or self.upload_url.startswith(self._upload_url): -fname = os.path.basename(self.upload_archive) return self._upload_url + fname super(UbuntuPolicy, self).get_upload_url() ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901786 Title: upload options do not support local SSL urls nor self-signed certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1901786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901786] Re: upload options do not support local SSL urls nor self-signed certificates
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 to Ubuntu. https://bugs.launchpad.net/bugs/1901786 Title: upload options do not support local SSL urls nor self-signed certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1901786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901786] [NEW] upload options do not support local SSL urls nor self-signed certificates
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-
url=https://10.0.1.112/sos/
This results in the error of:
Your sosreport has been generated and saved in:
/tmp/sosreport-autosos-2020-10-27-chnzdgv.tar.xz
Size 7.04KiB
Owner root
md53095adb8d50728e477ee2fecd056296f
Please send this file to your support representative.
Upload attempt failed: No upload destination provided by policy or by
--upload-url
Additionally, when configuring a reproducer (nginx configured with SSL +
PUT support), sosreport appears to ignore that endpoint, and fails with:
Upload attempt failed: No upload destination provided by policy or by
--upload-url
Updating the `/usr/lib/python3/dist-packages/sos/policies/ubuntu.py`
file to hard-code the internal, self-signed SSL URI (_upload_url),
produces the following error when attempted:
Upload attempt failed: HTTPSConnectionPool(host='10.0.1.112',
port=443): Max retries exceeded with url: /sosreport-autosos-
focal-2020-10-27-ocmbmws.tar.xz (Caused by SSLError(SSLError("bad
handss_process_server_certificate', 'certificate verify failed')])")))
There does not appear to be a way to tell sosreport to ignore a self-
signed certificate, or ignore verification of that certificate, even
when it's correctly imported into /usr/local/share/ca-certificates/ and
added to the client cert chain.
There is a temporary workaround, using curl to directly push that file
to the nginx endpoint, using:
sudo curl -k -T sosreport-autosos-focal-2020-10-27-tugrwdk.tar.xz
https://10.0.1.112/
But sosreport itself, does not appear to support custom URLs, nor self-
signed certificates.
** Affects: sosreport (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/1901786
Title:
upload options do not support local SSL urls nor self-signed
certificates
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1901786/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864212] Re: Please backport rabbitmq-server 3.8.2-0ubuntu1 (main) from focal
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 related to anything in the messaging workflow. The customer pushing for this backport is satisfied with the testing they've done, and wants to push forward with the SRU into -backports, so they can consume it organically from their internal, daily aptly mirror ASAP, to mitigate some fatal issues they've seen with their 3.6.10 version on Rocky. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864212 Title: Please backport rabbitmq-server 3.8.2-0ubuntu1 (main) from focal To manage notifications about this bug go to: https://bugs.launchpad.net/bionic-backports/+bug/1864212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867934] [NEW] Updating bird.conf to point to non-syslog log file results in incorrect log ownership, no logs written, service failure
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 show this working correctly, and relevant bird log entries will appear in /var/log/syslog as expected: $ sudo service bird status ● bird.service - BIRD Internet Routing Daemon (IPv4) Loaded: loaded (/lib/systemd/system/bird.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-03-18 10:11:50 EDT; 14s ago Main PID: 23485 (bird) Tasks: 1 (limit: 4915) CGroup: /system.slice/bird.service └─23485 /usr/sbin/bird -f -u bird -g bird Mar 18 10:11:50 hades-nuc systemd[1]: Starting BIRD Internet Routing Daemon (IPv4)... Mar 18 10:11:50 hades-nuc systemd[1]: Started BIRD Internet Routing Daemon (IPv4). Mar 18 10:11:50 hades-nuc bird[23485]: Started Update your /etc/bird/bird.conf and point the 'log' line to something like the following: log "/var/log/bird.log" all; Now restart the bird service: $ sudo service bird status ● bird.service - BIRD Internet Routing Daemon (IPv4) Loaded: loaded (/lib/systemd/system/bird.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-03-18 10:20:44 EDT; 9s ago Process: 25376 ExecStart=/usr/sbin/bird -f -u $BIRD_RUN_USER -g $BIRD_RUN_GROUP $BIRD_ARGS $BIRD4_ARGS (code=exited, status=1/FAILURE) Process: 25375 ExecStartPre=/usr/sbin/bird -p (code=exited, status=0/SUCCESS) Process: 25369 ExecStartPre=/usr/lib/bird/prepare-environment (code=exited, status=0/SUCCESS) Main PID: 25376 (code=exited, status=1/FAILURE) Mar 18 10:20:44 hades-nuc systemd[1]: Stopped BIRD Internet Routing Daemon (IPv4). Mar 18 10:20:44 hades-nuc systemd[1]: Starting BIRD Internet Routing Daemon (IPv4)... Mar 18 10:20:44 hades-nuc systemd[1]: Started BIRD Internet Routing Daemon (IPv4). Mar 18 10:20:44 hades-nuc systemd[1]: bird.service: Main process exited, code=exited, status=1/FAILURE Mar 18 10:20:44 hades-nuc bird[25376]: bird: /etc/bird/bird.conf, line 8: Unable to open log file `/var/log/bird.log': Permission denied Mar 18 10:20:44 hades-nuc systemd[1]: bird.service: Failed with result 'exit-code'. If you look at /var/log/bird.log, you'll see it is owned by 'root:root', not the expected 'bird:bird' as the original socket files (/var/run/bird.ctl, /var/run/bird6.ctl). This appears to be related to the parsing of bird.conf before privs are dropped and files created. This can be mitigated with a static workaround in /usr/lib/bird/prepare- environment, but that's a brittle hammer, and not really the right place for this: diff -u prepare-environment.orig prepare-environment --- prepare-environment.orig2020-03-17 15:53:47.122726551 + +++ prepare-environment 2020-03-17 15:51:19.496622613 + @@ -2,11 +2,13 @@ set -eu+BIRD_LOG_FILE=/var/log/bird.log BIRD_RUN_DIR=/run/bird . /etc/bird/envvars mkdir --parents "$BIRD_RUN_DIR"; +touch "$BIRD_LOG_FILE" if [ -n "$BIRD_RUN_USER" ]; then if ! getent passwd $BIRD_RUN_USER >/dev/null; then @@ -22,7 +24,6 @@ fi fi-chown --silent "$BIRD_RUN_USER:$BIRD_RUN_GROUP" "$BIRD_RUN_DIR" +chown --silent "$BIRD_RUN_USER:$BIRD_RUN_GROUP" "$BIRD_RUN_DIR" "$BIRD_LOG_FILE" chmod 775 "$BIRD_RUN_DIR" - : Thoughts? ** Affects: bird (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/1867934 Title: Updating bird.conf to point to non-syslog log file results in incorrect log ownership, no logs written, service failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bird/+bug/1867934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859751] Re: Piston missing support for Django 2.2
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 home directory `/var/cache/bind'. wrote key file "/etc/bind/rndc.key" Created symlink /etc/systemd/system/multi-user.target.wants/bind9.service → /lib/systemd/system/bind9.service. bind9-pkcs11.service is a disabled or a static unit, not starting it. bind9-resolvconf.service is a disabled or a static unit, not starting it. Setting up python3-maas-provisioningserver (2.6.0-7802-g59416a869-0ubuntu1) ... Setting up postgresql (12+210) ... Setting up maas-dhcp (2.6.0-7802-g59416a869-0ubuntu1) ... Created symlink /etc/systemd/system/multi-user.target.wants/maas-dhcpd.service → /lib/systemd/system/maas-dhcpd.service. Created symlink /etc/systemd/system/multi-user.target.wants/maas-dhcpd6.service → /lib/systemd/system/maas-dhcpd6.service. Setting up freeipmi-tools (1.6.4-3ubuntu1) ... Setting up maas-common (2.6.0-7802-g59416a869-0ubuntu1) ... adduser: Warning: The home directory `/var/lib/maas' does not belong to the user you are currently creating. Created symlink /etc/systemd/system/multi-user.target.wants/maas-syslog.service → /lib/systemd/system/maas-syslog.service. Setting up maas-rack-controller (2.6.0-7802-g59416a869-0ubuntu1) ... Traceback (most recent call last): File "/usr/lib/python3/dist-packages/maasserver/utils/django_urls.py", line 34, in from django.urls.resolvers import ( ImportError: cannot import name 'RegexURLPattern' from 'django.urls.resolvers' (/usr/lib/python3/dist-packages/django/urls/resolvers.py) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/sbin/maas-region", line 65, in main() File "/usr/sbin/maas-region", line 61, in main run() File "/usr/sbin/maas-region", line 49, in run management.execute_from_command_line() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 357, in execute django.setup() File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 114, in populate app_config.import_models() File "/usr/lib/python3/dist-packages/django/apps/config.py", line 211, in import_models self.models_module = import_module(models_module_name) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1006, in _gcd_import File "", line 983, in _find_and_load File "", line 967, in _find_and_load_unlocked File "", line 677, in _load_unlocked File "", line 728, in exec_module File "", line 219, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/maasserver/models/__init__.py", line 104, in from maasserver.models.blockdevice import BlockDevice File "/usr/lib/python3/dist-packages/maasserver/models/blockdevice.py", line 34, in from maasserver.utils.converters import human_readable_bytes File "/usr/lib/python3/dist-packages/maasserver/utils/__init__.py", line 26, in from maasserver.utils.django_urls import reverse File "/usr/lib/python3/dist-packages/maasserver/utils/django_urls.py", line 39, in from django.core.urlresolvers import ( ModuleNotFoundError: No module named 'django.core.urlresolvers' dpkg: error processing package maas-rack-controller (--configure): installed maas-rack-controller package post-installation script subprocess returned error exit status 1 Setting up maas-region-api (2.6.0-7802-g59416a869-0ubuntu1) ... Traceback (most recent call last): File "/usr/lib/python3/dist-packages/maasserver/utils/django_urls.py", line 34, in from django.urls.resolvers import ( ImportError: cannot import name 'RegexURLPattern' from 'django.urls.resolvers' (/usr/lib/python3/dist-packages/django/urls/resolvers.py) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/sbin/maas-region", line 65, in main() File "/usr/sbin/maas-region", line 61, in main run() File "/usr/sbin/maas-region", line 49, in run management.execute_from_command_line() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 357, in execute django.setup() File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File
[Bug 1821814] Re: Todoist support missing
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 depresses and returns. Ideally, it should prompt me to add my credentials, whether I'm running a GNOME window manager like metacity or not. At worst, an error dialog or message indicating that this doesn't work unless your actively running a GNOME wm, would be better than nothing and guessing what went wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821814 Title: Todoist support missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-todo/+bug/1821814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852104] [NEW] Passing --label or --name (deprecated) does nothing
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 doesn't actually apply the label it claims to, per the manpage: --label LABEL Specify an arbitrary identifier to associate with the archive. Labels will be appended after the system's short hostname and may contain alphanumeric characters. The resulting sosreport gets named as follows: sosreport-cloudserver-r024n17-2019115506.tar.xz I would expect to see 'hourly' in the resulting report name as the intended label. While testing this, I also noticed that --case-id is ignored as well: sosreport --batch -z xz -t 16 --verify --label foo --case-id 123 --ticket-number 456 This generates a sosreport with the following name, but is missing the '123' passed above: sosreport-cloudserver-r024n17.456-2019120325.tar.xz My intent was to create an hourly sosreport that can be overwritten, because it will always be created with the same name, vs. creating a directory of pooled sosreports that have to be cleaned up later on with another reaping script. ** Affects: sosreport (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/1852104 Title: Passing --label or --name (deprecated) does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1852104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849587] Re: apt-file doesn't find anything
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: /usr/bin/joe 1 $ dpkg -S $(which bash); apt-file search bash; echo $? bash: /bin/bash librust-cargo-dev: /usr/share/cargo/registry/cargo-0.37.0/src/etc/cargo.bashcomp.sh linux-tools-common: /usr/share/bash-completion/completions/bpftool 0 Here's the same search done with apt-file 2.5.2ubuntu1 on Trusty: $ dpkg -S $(which bash); apt-file search 'bin/bash'; echo $? bash: /bin/bash bash: /bin/bash bash: /usr/bin/bashbug bash-static: /bin/bash-static bashburn: /usr/bin/bashburn bashdb: /usr/bin/bashdb 0 $ dpkg -S $(which joe); apt-file search 'bin/joe'; echo $? joe: /usr/bin/joe joe: /usr/bin/joe joe-jupp: /usr/bin/joe 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849587 Title: apt-file doesn't find anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-file/+bug/1849587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838555] [NEW] nvme-cli 1.5 in Bionic does not support Micron NVME drives
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. $ rmadison nvme-cli -a amd64 nvme-cli | 1.5-1 | bionic/universe | amd64 nvme-cli | 1.6-1 | cosmic/universe | amd64 nvme-cli | 1.7-1 | disco/universe | amd64 Version 1.6-1 and later versions do include this support, and can be used by rebuilding the package from upstream source as a static binary... not ideal, but a workaround. In lieu of pulling 1.7 from Disco back into Cosmic -> Bionic, can we cherry-pick this specific commit and backport it into 1.5 in Bionic? Or, can we do a micro-release of 1.6 into Bionic? https://github.com/linux-nvme/nvme-cli/releases/tag/v1.6 [test case] Install nvme-cli from Bionic, and attempt to update firmware for any Micron NVME drive, using a command similar to the below. It will fail, as the drive is not supported. nvme micron select-download /dev/n1 --fw ./Micron_9200_FW- 101008S0.tar --select=ALL [other info] The specific commit that adds the needed support for these drives appears to be: https://github.com/linux-nvme/nvme- cli/pull/353/commits/0124daa3331602365d009a9e8229454c41931c07 ** Affects: nvme-cli (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/1838555 Title: nvme-cli 1.5 in Bionic does not support Micron NVME drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1838555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828617] Re: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration
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 applied to those block devices. We've also disabled nvme multipathing on every Ceph storage node with the following in /etc/d/g kernel boot args: nvme_core.multipath=0 Note: This LP was cloned from an internal customer case where their Ceph storage nodes were directly impacted by this issue, and this is the current workaround deployed, until/unless we can find a consistent RC for this issue in an upstream package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828617 Title: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1828617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828617] Re: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration
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 8:00 1.8T 0 disk |-sda1 8:10 512M 0 part /boot/efi `-sda2 8:20 1.8T 0 part |-foobar--vg-root 253:00 1.8T 0 lvm / `-foobar--vg-swap_1 253:10 976M 0 lvm [SWAP] nvme0n1 259:00 1.8T 0 disk `-ceph--c576f63e--dfd4--48f7--9d60--6a7708cbccf6-osd--block--9fdd78b2--0745--47ae--b8d4--04d9803ab448 253:60 1.8T 0 lvm nvme1n1 259:10 1.8T 0 disk `-ceph--6eb6565f--6392--44a8--9213--833b09f7c0bc-osd--block--a7d3629c--724f--4218--9d15--593ec64781da 253:50 1.8T 0 lvm nvme2n1 259:20 1.8T 0 disk `-ceph--c14f9ee5--90d0--4306--9b18--99576516f76a-osd--block--bbf5bc79--edea--4e43--8414--b5140b409397 253:40 1.8T 0 lvm nvme3n1 259:30 1.8T 0 disk `-ceph--a821146b--7674--4bcc--b5e9--0126c4bd5e3b-osd--block--b9371499--ff99--4d3e--ab3f--62ec3cf918c4 253:30 1.8T 0 lvm nvme4n1 259:40 1.8T 0 disk `-ceph--2e39f75a--5d2a--49ee--beb1--5d0a2991fd6c-osd--block--a1be083e--1fa7--4397--acfa--2ff3d3491572 253:20 1.8T 0 lvm nvme5n1 259:50 1.8T 0 disk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828617 Title: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594317] Re: Cannot start lxd-bridge.service when MAAS is managing DNS
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 managing DNS
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1594317/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594317] Re: Cannot start lxd-bridge.service when MAAS is managing DNS
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 Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd-bridge.service when MAAS is managing DNS
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1594317/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782818] Re: package linux-image-4.15.0-29-generic 4.15.0-29.31~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135
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 upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up linux-image-4.15.0-29-generic (4.15.0-29.31) ... Processing triggers for linux-image-4.15.0-29-generic (4.15.0-29.31) ... /etc/kernel/postinst.d/dkms: Error! Could not locate dkms.conf file. File: does not exist. run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 dpkg: error processing package linux-image-4.15.0-29-generic (--configure): installed linux-image-4.15.0-29-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-4.15.0-29-generic needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) You have new mail in /var/mail/root -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782818 Title: package linux-image-4.15.0-29-generic 4.15.0-29.31~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1782818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783619] [NEW] do-release-upgrade fails to calculate upgrade, crashes because appstreamcli crashes iin a g_str* assertion
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] Fetched 76.8 MB in 6s (1,564 kB/s) (appstreamcli:29485): GLib-CRITICAL **: g_strchug: assertion 'string != NULL' failed (appstreamcli:29485): GLib-CRITICAL **: g_strchomp: assertion 'string != NULL' failed (appstreamcli:29485): GLib-CRITICAL **: g_strchug: assertion 'string != NULL' failed (appstreamcli:29485): GLib-CRITICAL **: g_strchomp: assertion 'string != NULL' failed (appstreamcli:29485): GLib-CRITICAL **: g_strchug: assertion 'string != NULL' failed (appstreamcli:29485): GLib-CRITICAL **: g_strchomp: assertion 'string != NULL' failed (appstreamcli:29485): GLib-CRITICAL **: g_strchug: assertion 'string != NULL' failed (appstreamcli:29485): GLib-CRITICAL **: g_strchomp: assertion 'string != NULL' failed (appstreamcli:29485): GLib-CRITICAL **: g_strchug: assertion 'string != NULL' failed (appstreamcli:29485): GLib-CRITICAL **: g_strchomp: assertion 'string != NULL' failed AppStream cache update completed, but some metadata was ignored due to errors. Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Calculating the changes Calculating the changes Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.25 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Jul 25 13:53:15 2018 InstallationDate: Installed on 2016-10-24 (638 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2018-07-25 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug dist-upgrade third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783619 Title: do-release-upgrade fails to calculate upgrade, crashes because appstreamcli crashes iin a g_str* assertion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1783619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1523274] Re: nvidia-settings: Couldn't connect to accessibility bus
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 or any externally connected displays. This _just_ started happening after 1 year of correctly configured and perfect use of all 3 panels. I can't figure out what happened that broke this, but now nothing works, and I'm stuck with the default Intel driver, which only supports 1600x1080 on my 4k panel. Booting Windows 7 on the same physical metal, all 3 panels work flawlessly, arranged correctly, at the native 4k resolution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523274 Title: nvidia-settings: Couldn't connect to accessibility bus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1523274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs
** 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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674399 Title: OpenSSL CPU detection for AMD Ryzen CPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771254] Re: bluetooth doesn't work until I "sudo hciconfig hci0 reset"
*** 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 to solve the issue. The only way I've been able to keep a paired Bluetooth mouse working (Logitech Anywhere MX/2) is by running 'sudo hciconfig -a hci0 reset' in a VERY tight, 5-second loop. Anything greater than that, and bluetooth just goes off into lala land and doesn't wake back up. This is EXTREMELY annoying, and was introduced very recently between June and October. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771254 Title: bluetooth doesn't work until I "sudo hciconfig hci0 reset" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/771254/+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?)
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 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 1567744] Re: USB NICs get too long name for ifupdown aliases
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. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609072] [NEW] uvt-kvm incorrectly asserts 'default' will be on vibr0, and ssh/networking fails
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 show its hostname as 'ubuntu' instead of 'myvm', despite the VM's hostname itself, being 'myvm'. $ uvt-kvm ssh ubuntu@myvm --insecure [12:39:55] uvt-kvm: error: no IP address found for libvirt machine u'myvm'. Has it had time to boot yet? If you interactively ssh into the VM (requires passing '--password foobar' to the 'uvt-kvm create' command), you can see that it does indeed have an IP address $ ssh ubuntu@10.0.5.190 "hostname -f; hostname -I" myvm 10.0.5.190 If you ssh into the guest (myvm) and then look at /etc/hosts, you'll notice the last line has an incorrect entry, pointing the loopback address to the hostname of 'myvm'. This is always wrong. Manually editing that to correctly point 10.0.5.190 to myvm, and rebooting the VM, then allows virsh net-dhcp-leases to correctly show 'myvm' in the list (vs. 'ubuntu' before), but 'uvt-kvm ssh --insecure myvm' still fails. $ sudo virsh --connect qemu:///system net-dhcp-leases default Expiry Time MAC addressProtocol IP address HostnameClient ID or DUID --- 2016-08-02 13:41:34 52:54:00:9d:ec:32 ipv4 10.0.5.190/24 myvm- I destroyed this VM, and edited the networks to make 'default' reside on vibr0 (using 'virsh net-edit'), then destroyed (stopped) those networks and restarted them. Now creating the vm using 'uvt-kvm create' as before, produces a 'myvm' that shows up in net-dhcp-leases (without editing /etc/hosts and rebooting), AND 'uvt-kvm ssh --insecure myvm' works perfectly as expected. The bug with /etc/hosts is still present, but I'll file that separately. The solution to this would be to have uvt-kvm use 'net-dumpxml default', parse the bridge out of the 'default' network and scan that for leases. It does not do that today. default dabf43c6-e876-436b-9a03-fcc7ede8619f Not everyone will have 'default' at vibr0, so we need to accommodate configurations where that isn't the first, or required bridge. ** Affects: uvtool (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/1609072 Title: uvt-kvm incorrectly asserts 'default' will be on vibr0, and ssh/networking fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/1609072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595627] Re: Pacemaker fails to start and reports a Library Error
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: kernel.pid_max = 9 **NOTE** This solution is not intended to be a long-term fix, but merely a hotfix or stopgap until you are able to install the updated package that contains the appropriate code-level fix. Using the 'pid_max' change above allows you to keep your package installation tree controlled and managed with stable packages, and limits the number of pids your machine will allocate to a total of 99,999 which is just enough NOT to reach the limit that this patch addresses. When the package reaches the standard repository (after leaving -proposed), you'll receive the patched version with your regular updates and can install it as you would normally. Hope that helps! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1595627 Title: Pacemaker fails to start and reports a Library Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libqb/+bug/1595627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
