Hi {Danilo, Lukas},
Tried the PPA out, it working correctly with the fix, thanks!
root@lp2070318:~# grep card /etc/netplan/10-lxc.yaml
ovn-cms-options: "card-serial-number=MT42424242N8,enable-chassis-as-gw"
root@lp2070318:~# sudo netplan apply
# Second time
root@lp2070318:~# sudo netplan
Tested the proposed focal kernel - looks good as well:
$ uname -r
5.4.0-98-generic
$ apt policy linux-image-5.4.0-98-generic
linux-image-5.4.0-98-generic:
Installed: 5.4.0-98.111
Candidate: 5.4.0-98.111
Version table:
*** 5.4.0-98.111 500
500 http://ppa.launchpad.net/canonical-kern
Tried the proposed impish kernel - looks good:
$ uname -r
5.13.0-29-generic
$ apt policy linux-image-5.13.0-29-generic
linux-image-5.13.0-29-generic:
Installed: 5.13.0-29.32
Candidate: 5.13.0-29.32
Version table:
*** 5.13.0-29.32 500
500 http://ppa.launchpad.net/canonical-kernel-t
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957753
Title:
net/mlx5e: EPERM on vlan 0 programming
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/l
And, finally, the Jammy kernel:
$ uname -r
5.15.0-17-generic
$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0
$ sudo ip link set enp130s0f0 vf 2 vlan 1 ; echo $?
RTNETLINK answers: Operation not permitted
2
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Confirmed
** Cha
Impish kernel looks good:
$ uname -r
5.13.0-28-generic
$ sudo ip link set enp130s0f0 vf 2 vlan 1 ; echo $?
RTNETLINK answers: Operation not permitted
2
$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hirsute kernel looks good as well:
$ uname -r
5.11.0-50-generic
$ sudo ip link set enp130s0f0 vf 2 vlan 1 ; echo $?
RTNETLINK answers: Operation not permitted
2
$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Focal:
$ uname -r
5.4.0-97-generic
$ sudo ip link set enp130s0f0 vf 2 vlan 1
RTNETLINK answers: Operation not permitted
$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0
Looks good - vlan 0 programming doesn't result in EPERM as expected
contrary to non-zero vlans.
Will try others as well.
Public bug reported:
There is an issue with hypervisor host side mlx5 driver operation on
Bluefield devices in kernels <=5.16 that was recently fixed in master
with a one-liner:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37
Also I seem to be getting a SIGBUS signal only when function addresses
are not 4-byte aligned:
Thread 1 "curl" received signal SIGBUS, Bus error.
0x006358f58d277bf1 in ?? ()
Thread 1 "curl" received signal SIGBUS, Bus error.
0xb1b30b5cc1eb2dda in ?? ()
Thread 1 "curl" received signal SIGBUS, Bus
Vladimir,
stracing reveals that si_code is set to BUS_ADRALN so there is a problem
with address alignment.
strace curl https://example.com
--- SIGBUS {si_signo=SIGBUS, si_code=BUS_ADRALN, si_addr=0x3efd151115865b} ---
+++ killed by SIGBUS (core dumped) +++
Bus error (core dumped)
The fault is r
Marked as Fix-Committed for Focal and Groovy based on:
https://code.launchpad.net/~fnordahl/ubuntu/+source/openvswitch/+git/openvswitch/+merge/399763
https://code.launchpad.net/~fnordahl/ubuntu/+source/openvswitch/+git/openvswitch/+merge/399764
https://launchpad.net/ubuntu/focal/+queue?queue_stat
** 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/1918583
Title:
Switch to libgpiod and disable CONFIG_GPIO_SYSFS
To manage notifica
Public bug reported:
Ubuntu kernels are built with CONFIG_GPIO_SYSFS=y after
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342153
debian.master/config/config.common.ubuntu: CONFIG_GPIO_SYSFS=y
However, this interface got deprecated for removal:
https://git.kernel.org/pub/scm/linux/kerne
** Also affects: neutron (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/1884723
Title:
[OVS] multicast between VM instances on different compute n
ip address show output on one of the affected nodes (for reference on
how large it is):
https://paste.ubuntu.com/p/cRf655Y8kt/
** Also affects: oslo.privsep
Importance: Undecided
Status: New
** Description changed:
+ When there is a large amount of netdevs registered in the kernel and
~nikolay.vinogradov and I found the root cause after a long debugging
session.
What we have:
* a bionic-ussuri deployment with the HWE (focal 5.4) kernel;
* 2 processes communicating over a type=STREAM unix socket (blocking);
* Unix sockets have max buffer limits which means the amount of data t
Verified xenial/queens (the updated packages got uploaded compared to
the check in comment #45):
lxc launch ubuntu:xenial oslop-xq
Creating oslop-xq
Starting oslop-xq
lxc exec oslop-bq bash
root@oslop-xq:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 1
Also checked the python2.7 package on bionic just in case (unit tests
use `six` for compatibility so they work either way):
lxc exec oslop bash
root@oslop:~# cat # Enable Ubuntu proposed archive
> deb http://archive.ubuntu.com/ubu
xenial + proposed Queens cloud archive (doesn't look like the changes
are there):
lxc launch ubuntu:xenial oslop-xq
Creating oslop-xq
Starting oslop-xq
lxc exec oslop-bq bash
root@oslop-xq:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.6 LTS
Bionic:
---
lxc launch ubuntu:bionic oslop-b
Creating oslop-b
Starting oslop-b
lxc exec oslop-b bash
root@oslop-b:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename: bionic
root@oslop-b:~# cat
Focal verification:
lxc launch ubuntu:focal oslop-f
Creating oslop-f
Starting oslop-f
lxc exec oslop-f bash
root@oslop-f:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename: focal
root@oslop-f:~# cat
** Also affects: horizon (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/1886678
Title:
TypeError at /project/network_topology/
To manage notifica
Verified bionic/ussuri:
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename: bionic
git show
commit 19b9bc6128af181df0da9e2e3f2e2001c93b758a (HEAD -> stable/ussuri, tag:
debian/3.1.0-0ubuntu1.1, origin/stabl
Verified for Bionic/Stein:
git show HEAD
commit f05aa4863cdeff0406f73c02e9209842aab4369f (HEAD -> stable/stein, tag:
debian/2.1.1-0ubuntu1_cloud1, origin/stable/stein)
Author: Corey Bryant
Date: Thu Jun 25 14:40:43 2020 -0400
releasing package python-oslo.policy version 2.1.1-0ubuntu1~clo
Verified on Bionic/Train.
git show HEAD
commit f61adf33af13ea725acebf4246caaa6949e86000 (HEAD -> stable/train, tag:
debian/2.3.2-0ubuntu1_cloud1, origin/stable/train)
Author: Corey Bryant
Date: Thu Jun 25 14:33:54 2020 -0400
releasing package python-oslo.policy version 2.3.2-0ubuntu1~clou
Verified Ussuri (on Focal):
root@oslop-f:/tmp/oslo.policy/python-oslo.policy# git remote show origin
* remote origin
Fetch URL:
https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/python-oslo.policy
Push URL:
https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/python-oslo.po
Yes, the backports themselves include the unit tests necessary to
validate the change.
https://review.opendev.org/#/q/topic:bug/1880959+(status:open+OR+status:merged)
We just need to get a second +2 on some of them.
Rocky and Queens backports are blocked on devstack backports to
devstack/rocky a
You may be right.
I have this in monkey_patch.py:
# Monkey patch the original current_thread to use the up-to-date _active
# global variable. See https://bugs.launchpad.net/bugs/1863021 and
# https://github.com/eventlet/eventlet/issues/592
import __original_module_threading as ori
I was trying to disable .pyc files by having PIP_COMPILE=false and
PYTHONDONTWRITEBYTECODE=false.
But this isn't possible based on the below.
https://pip.pypa.io/en/stable/user_guide/#environment-variables (pip allows
environment variables instead of command-line arguments)
https://docs.python.o
** Description changed:
TL;DR: as of python 3.7, .pyc files by default include a timestamp and a size
of the source file which results in a change of a hash every time a .pyc file
is generated for a given source file. This results in staging conflicts for
python parts.
https://docs.python.o
To sum up:
* snapcraft still needs to pass the same SOURCE_DATE_EPOCH for different parts
to change the invalidation mode to PycInvalidationMode.CHECKED_HASH;
note: it needs to be set to something after 1980 apparently, otherwise
ValueError('ZIP does not support timestamps before 1980')
wil
** Bug watch added: github.com/pypa/pip/issues #8414
https://github.com/pypa/pip/issues/8414
** Also affects: pip via
https://github.com/pypa/pip/issues/8414
Importance: Unknown
Status: Unknown
** No longer affects: python3.8 (Ubuntu)
--
You received this bug notification becaus
** Also affects: python-pip (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/1882535
Title:
[focal/core20][python3.7+] staging conflicts when multip
source_to_code is used to load the code object which has a source path
specified:
https://github.com/python/cpython/blob/0f5a28f834bdac2da8a04597dc0fc5b71e50da9d/Lib/py_compile.py#L144-L145
https://docs.python.org/3/library/importlib.html#importlib.abc.InspectLoader.source_to_code
"The path argume
Going further:
* _code_to_hash_pyc takes a code object in (not the source code itself)
https://github.com/python/cpython/blob/843c27765652e2322011fb3e5d88f4837de38c06/Lib/importlib/_bootstrap_external.py#L608-L616
* MAGIC_NUMBER is the same across different invocations and other
transformations a
** Description changed:
[Impact]
Based on the investigation here
https://bugs.launchpad.net/charm-keystone/+bug/1880847 it was determined that
rules from policy files located in the directory specified in the policy_dirs
option (/etc//policy.d by default) are not re-applied after the
rules
Corey,
The simplest way to test this for a particular version would be to put
the attached test under oslo_policy/tests/test_1880959.py in a checked
out version of oslo.policy and running:
tox -e cover -- oslo_policy.tests.test_1880959.EnforcerTest
It will fail like below without the patch appli
Corey, I believe the issue got introduced in Liberty and affects all
releases since then:
https://opendev.org/openstack/oslo.policy/commit/b5f07dfe4cd4a5d12c7fecbc3954694d934de642
The check in question is still the same in Ussuri and that code hasn't seen
much change:
https://opendev.org/openstac
** Also affects: oslo.policy
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/1880959
Title:
Rules from the policy directory files are not reapplied after ch
Public bug reported:
Based on the investigation here https://bugs.launchpad.net/charm-
keystone/+bug/1880847 it was determined that rules from policy files
located in the directory specified in the policy_dirs option
(/etc//policy.d by default) are not re-applied after the
rules from the primary p
Public bug reported:
While investigating https://bugs.launchpad.net/charm-manila-
ganesha/+bug/1879908, I encountered errors related to neutron-dynamic-
routing:
2020-05-20 23:11:14.050 40970 ERROR neutron_lib.callbacks.manager
[req-74431ceb-ff96-4906-9a44-48d5bb630e31 dee5f0d2f3674b299f50b71400
For context: focal kernels seem to contain raharper's patch for bcache
that fixed LP: #1729145.
https://paste.ubuntu.com/p/VkfPDBzqyt/
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?id=67553dcd79051be43ef73207309bee4cb72e5189
--
You received this bug notificatio
I no longer get that issue with latest updates for Focal so something
must have fixed it.
Setting to incomplete.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
Status: Confirmed => Incomplete
** C
Found another way to trigger this problem by opening up various
documents in libreoffice and using zoom back and forth (also happens
sometimes when comments are created).
https://errors.ubuntu.com/oops/a906d424-6cc2-11ea-aa90-fa163e983629
--
You received this bug notification because you are a m
Recently hit that on Focal due to the fact that quotas were enabled by
LXD.
This renders the system completely unresponsive if you use btrfs as a
rootfs with btrfs-transaction or btrfs-cleaner kernel threads hogging a
100% of 1 CPU core.
Booting using a live USB, disabling quotas and temporarily
albertomilone, looks good to me.
I tried switching from nvidia to intel and back rebooting on each
attempt and haven't managed to reproduce the issue. Looks like
reordering udev rules and/or adding another device class in your change
helped (thanks a lot!).
I don't see an nvidia device in lspci o
I'm on focal now, just got the updated packages.
I will give it a try soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error booting with prime-select intel: prime-selec
Thanks, will help you with testing for sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error booting with prime-select intel: prime-select does not
update initramfs to
Happened to me when using virt-viewer and connecting to an Ubuntu 18.04
VM via SPICE as well so this isn't specific to a guest VM it seems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863142
Title:
Hi Daniel,
I submitted a new crash dump via `ubuntu-bug`:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1863142
I'm going to set the status for this one to "New" as I provided the info
but maybe it should be duplicated to the new bug.
** Changed in: xorg-server (Ubuntu)
Statu
Public bug reported:
I observed the following on Eoan as well with nvidia drivers older than
440.
1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type,
QXL + SPICE:
2) When a host is booted with `prime-select intel` observing guest
I see, thanks for the clarification.
I will need to read through other cases as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862531
Title:
[focal] Wayland session is not available when a la
Hi Daniel, thank you for the quick response and prior work.
I think the upstream check for the nvidia driver in 61-gdm.rules is too
broad to be useful as the nvidia driver might be loaded for other
reasons (e.g. CUDA usage or hw accelerated video encoding/decoding while
nvidia-drm.ko is blackliste
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error booting with prime-select intel: prime-select does not
update initramfs to blacklist nvidia mo
Public bug reported:
A Wayland session present at /usr/share/wayland-sessions/ubuntu-
wayland.desktop is not displayed at the login screen when a system has
an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used:
prime-select query
intel
Only sessions at /usr/share/xsessions are present.
➜
Based on a discussion with ~albertomilone, powering down the NVIDIA GPU
while keeping the modules loaded is the way to go long-term as opposed
to blacklisting the modules.
The power management feature is described here (requires Turing GPUs and above):
http://us.download.nvidia.com/XFree86/Linux-x
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838151
Title:
Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing
wide band speech support.
To manage no
Tried rev 951 now and I cannot reproduce the same behavior anymore.
➜ ~ snap refresh chromium --beta
Download snap "chromium" (951) from channel "beta"
77%
251kBDownloadchromium (beta) 79.0.3945.
English (US) to Russian: en -> ru.
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853420
Title:
[19.10][snap][beta] Switchi
updateinitramfs used to be run previously, however, this was removed at
some point (introduced into the distro in Cosmic/18.10):
https://github.com/tseliot/nvidia-
prime/commit/7595f47b84f713dc969440e31d0e53708fddd71f
https://git.launchpad.net/~usd-import-team/ubuntu/+source/nvidia-
prime/commit/
Managed to reproduce it:
1) switched to nvidia;
2) worked for a while with it for a while with 5.3.0-19-generic;
3) got a kernel update to 5.3.0-23-generic;
4) switched to intel;
5) reproduced the problem.
What I found is:
1) /lib/modprobe.d/blacklist-nvidia.conf gets created if you switch to
"i
Public bug reported:
Unable to switch an input method from English in chromium by changing it
via ibus.
➜ ~ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 19.10
Release:19.10
Codename: eoan
➜ ~ snap list chromium
Name Version
If anybody still has a reproducer, it would be useful to set a trace
point like this:
sudo vim /usr/bin/prime-select
# ...
import pdb
pdb.set_trace()
if profile == 'nvidia':
# Always allow enabling nvidia
# (No need to check if nvidia is available)
I had the same problem (the system got upgraded from 19.04 to 19.10,
nvidia-430 driver).
I noticed that nvidia drivers were loaded in the rescue mode - so they
were likely not blacklisted properly.
When I did not enter the rescue mode I had the following message displayed:
"A start job is running
If I am not mistaken, Disco/19.04 doesn't have the fix backported yet:
https://git.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/tree/DistUpgrade/DistUpgradeController.py?h=ubuntu/disco-updates#n362
binaries_and_dirnames = [("python", "python"), ("python2", "python"),
On 19.04 I can see the following (correct) behavior.
With VPN (turned on via NetworkManager):
# note: no "global" DNS servers have been configured by hand through
systemd-resolved conf using "DNS=" directive
systemd-resolved --status
# ...
Link 15 (tun0)
Current Scopes: DNS
DefaultRoute
** Also affects: keystone (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-archive
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/
Corey,
Created a separate bug, feel free to add other affected charms
https://bugs.launchpad.net/charm-openstack-dashboard/+bug/1837457
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828293
Title:
Disco verification:
apt policy liblasso3
liblasso3:
Installed: 2.6.0-2ubuntu0.1
Candidate: 2.6.0-2ubuntu0.1
Version table:
*** 2.6.0-2ubuntu0.1 1000
399 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 Packages
100 /var/lib/dpkg/status
2.6.0-2build1 400
Bionic verification:
apt policy liblasso3
liblasso3:
Installed: 2.5.1-0ubuntu1.1
Candidate: 2.5.1-0ubuntu1.1
Version table:
*** 2.5.1-0ubuntu1.1 1000
400 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
2.5.1-0ubuntu1 500
Will do.
On Wed., Jul. 17, 2019, 01:35 Christian Ehrhardt , <
1833...@bugs.launchpad.net> wrote:
> @Dmitriis - I'd expect this testing and verification is on you as you
> have done so before, so give it a go once you have some time.
>
> --
> You received this bug notification because you are sub
Christian,
I updated the description based on the SRU template and also modified
the changelogs and commit messages.
** Description changed:
- See comments on the bug:
- https://bugs.launchpad.net/charm-keystone-saml-mellon/+bug/1833134
+ [Impact]
+
+ * Usage of ECP is not possible with mod_aut
Hi Christian,
Thanks, please do, no last minute changes from my side.
On Thu., Jul. 11, 2019, 06:27 Christian Ehrhardt , <
1833...@bugs.launchpad.net> wrote:
> Hi,
> I reviewed the MPs and they are (aside some potential polishing of the
> changelog) ok to me.
> You'll need an SRU template for t
xnox,
Hmm, based on my previous notes in #18 it is not clear whether that's
the case.
We would have to test with vaultlocker patched to have the workaround
removed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834577
Title:
[security] Consider upgrading mellon for Bionic to be able to change
Tried to reproduce the same but hit this
https://bugs.launchpad.net/ubuntu/+source/neutron-fwaas-
dashboard/+bug/1828293 as the fix was not synced into the archive yet.
I am pretty sure the issue was due to the lack of a relation between
Vault and Heat.
I will try it again if I get a chance after
Looks like Rocky UCA hasn't been updated with 1.5.0-0ubuntu3.1 yet:
http://ubuntu-cloud.archive.canonical.com/ubuntu/dists/bionic-
updates/rocky/main/binary-amd64/Packages
Package: python3-neutron-fwaas-dashboard
Source: neutron-fwaas-dashboard
Priority: optional
Section: python
Installed-Size: 6
Sandor,
Not on the VRF usage side but there is a feature in MAAS 2.6 to have a
better way to work in multi-homed environments (for bionic+ machines):
https://docs.maas.io/2.6/en/intro-new
"Networking - Multiple default gateways"
It relies on "routing policy database" (RPDB) functionality
https:/
I have suggested a patch upstream which then got merged:
https://dev.entrouvert.org/issues/34409#note-10
The branches related to this bug apply the patch to different distro
versions.
** Changed in: lasso (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you
** Merge proposal linked:
https://code.launchpad.net/~dmitriis/ubuntu/+source/lasso/+git/lasso/+merge/369737
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833299
Title:
lasso includes "Destinat
Attached logs from a healthy unit as well.
** Attachment added: "/var/log/ from designate/0 (healthy)"
https://bugs.launchpad.net/charm-designate/+bug/1828534/+attachment/5275082/+files/var-log-designate-0.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Managed to reproduce it (only on one unit though), this time with
debug=true - looks like it is a py2 - py3 issue:
designate/0 activeidle 2/lxd/2 10.232.46.209
9001/tcpUnit is ready
hacluster-designate/0* activeidle10.2
I am upgrading an env to Rocky now.
I suspect that this might have been due to a missing relation between
heat and vault.
I will verify again and comment on the bug. Thanks for double-checking.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm going to do another upgrade attempt.
https://pastebin.canonical.com/p/72XWqsjMdr/ (bundle)
https://paste.ubuntu.com/p/JSSFZvp3bB/ (upgrade script: os-upgrade.py
with a `juju --wait` and service list modification)
~/bundles/os-upgrade-queens-rocky.py -p
Let's see if I can reproduce it again.
Looks like it was introduced by this:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832522
** Also affects: openssl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Also tested with cosmic-proposed with the same test case as in #14 with
a positive outcome.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
https://dev.entrouvert.org/issues/34409
** Bug watch added: dev.entrouvert.org/issues #34409
https://dev.entrouvert.org/issues/34409
** Patch added: "0001-PAOS-Do-not-populate-Destination-attribute.patch"
https://bugs.launchpad.net/ubuntu/+source/lasso/+bug/1833299/+attachment/5273832/+fil
** Description changed:
See comments on the bug:
https://bugs.launchpad.net/charm-keystone-saml-mellon/+bug/1833134
Lasso is used by libapache2-mod-auth-mellon to create SAML messages.
When ECP profile (http://docs.oasis-open.org/security/saml/Post2.0/saml-
ecp/v2.0/cs01/saml-ecp-v2.0
Tested with stein-proposed:
apt policy apt policy libapache2-mod-auth-mellon
apt:
Installed: 1.6.11
Candidate: 1.6.11
Version table:
*** 1.6.11 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
# grep MellonDiag /etc/apac
Public bug reported:
On "Stacks" tab access:
==> /var/log/apache2/error.log <==
[Sat Jun 22 13:47:19.508215 2019] [wsgi:error] [pid 429649:tid 140430026204928]
[remote 10.232.46.207:53860] Recoverable error: ERROR: Internal Error
==> /var/log/apache2/ssl_access.log <==
10.232.46.207 - - [22/Jun
** Attachment added: "rocky-heat-dashboard-stack-list.png"
https://bugs.launchpad.net/ubuntu/+source/heat-dashboard/+bug/1833814/+attachment/5272337/+files/rocky-heat-dashboard-stack-list.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "heat-cannot-get-openstack-resources.png"
https://bugs.launchpad.net/ubuntu/+source/heat-dashboard/+bug/1833814/+attachment/5272336/+files/heat-cannot-get-openstack-resources.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Ran into a related problem during debugging of dashboard errors ("Unable
to retrieve key pairs") with a Rocky cloud & identity federation.
There was no clear indication as to why failures occurred.
https://paste.ubuntu.com/p/v5HXyyWXC2/ (full pdb trace)
At a high level I was getting validation f
Public bug reported:
See comments on the bug:
https://bugs.launchpad.net/charm-keystone-saml-mellon/+bug/1833134
Lasso is used by libapache2-mod-auth-mellon to create SAML messages.
When ECP profile (http://docs.oasis-open.org/security/saml/Post2.0/saml-
ecp/v2.0/cs01/saml-ecp-v2.0-cs01.pdf) is u
Tested on rocky-proposed:
apt policy libapache2-mod-auth-mellon
libapache2-mod-auth-mellon:
Installed: 0.14.0-1ubuntu0.2~cloud0
Candidate: 0.14.0-1ubuntu0.2~cloud0
Version table:
*** 0.14.0-1ubuntu0.2~cloud0 500
500 http://ubuntu-cloud.archive.canonical.com/ubuntu
bionic-proposed/r
Verified with a Queens -> Rocky upgrade with a workaround for lp:1832075
(pre-installing python3-pymysql).
apt policy python3-neutron-fwaas-dashboard
python3-neutron-fwaas-dashboard:
Installed: 1.5.0-0ubuntu3.1~cloud0
Candidate: 1.5.0-0ubuntu3.1~cloud0
Version table:
*** 1.5.0-0ubuntu3.1~cl
I can confirm that this no longer occurs with proposed.
apt policy python3-neutron-fwaas-dashboard
python3-neutron-fwaas-dashboard:
Installed: 2.0.1-0ubuntu1.1~cloud0
Candidate: 2.0.1-0ubuntu1.1~cloud0
I did run into a different problem though for which I filed a separate bug:
https://bugs.
Public bug reported:
Ran an upgrade from bionic-queens to bionic-rocky and encountered the
following:
/var/log/apt/term.log
https://paste.ubuntu.com/p/n6WZJbDy6p/
File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", line
25, in
import pymysql
ModuleNotFoundError: No m
Hi Colleen,
Thanks for the response.
Migrating to fernet was not a problem for my case and I think it is a
logical thing to do considering UUID tokens were removed in Rocky.
I agree that fixing it in an older release is a more expensive operation
than migration to fernet tokens so for my case it
1 - 100 of 372 matches
Mail list logo
