Public bug reported:
ceph-mgr-dashboards fail to load due to missing python3-setuptools:
ceph-mgr[5125]: 2025-03-19T14:28:13.333+ 7af7b3ec3000 -1 mgr[py] Module not
found: 'dashboard'
ceph-mgr[5125]: 2025-03-19T14:28:13.333+ 7af7b3ec3000 -1 mgr[py] Traceback
(most recent call last):
cep
Public bug reported:
The ceph mgr dashboard modules do not run on noble anymore at all:
ceph-mgr[21215]: 2025-03-19T14:11:13.632+ 785315e006c0 -1
log_channel(cluster) log [ERR] : Unhandled exception from module 'dashboard'
while running on mgr.core1a: PyO3 modules compiled for CPython 3.8 o
Public bug reported:
Neutron agents are missing a package dependency on iptables, since
iptables is not installed by default:
neutron-l3-agent:
Aug 20 13:16:34 gateway1a neutron-l3-agent[1498]:
Failed to process floating IPs.
Traceback (most recent call last):
File
"/usr/lib/py
Public bug reported:
neutron-l3-agent fails to handle notifications on Ubuntu 24.04:
Error during notification for
neutron.agent.metadata.driver.after_router_updated-7849645393520 router,
after_update
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/neut
Compared to v23, in v24, all migration files are missing from the
package:
> diff -r python3-neutron-dynamic-routing_23.0.0-0ubuntu1~cloud0
> python3-neutron-dynamic-routing_24.0.0-0ubuntu1
Only in
python3-neutron-dynamic-routing_23.0.0-0ubuntu1~cloud0/usr/lib/python3/dist-packages/neutron_dynam
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069814
Title:
alembic.script.revision.ResolutionError: No such revision or branch
'f399fa0f5f25'
To manage notifications about this bug go to:
https:
Public bug reported:
Migrating the database fails when upgrading to Caracal:
$ neutron-db-manage upgrade --expand
INFO [alembic.runtime.migration] Context impl MySQLImpl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
Running upgrade (expand) for neutron ...
INFO [alembi
We're not yet on 24.04 and still have a few OpenStack upgrades to do
before we can try 24.04. For now, we're running 22.04 and do specify the
bridges that neutron-linuxbridge-agent would create directly in systemd-
networkd, which mostly works, like this:
# /etc/systemd/network/10-brqe240c66b-
> I think it's fine. It sounds like there will just be no way to
override package-installed blacklists any more. That's unfortunate, but
it's a very rare situation.
The i6300esb watchdog driver is required for every KVM/qemu virtual
machine with an emulated watchdog
(https://wiki.openstack.org/wik
Note that relaxing the watchdog module blacklist would solve this issue
too: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1767172.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948040
Title
The fix seems to still not be available in Ubuntu 18.04 and 20.04 as
well as their cloud images. The current images still list the LXD data
source before the OpenStack data source.
Is there any additional step needed to fix the issue in the LTS
releases?
--
You received this bug notification bec
We use nova-compute-lxd to run OpenStack "VMs" not as libvirt+QEMU
virtual machines, but as LXD containers. The nova-compute-lxd connects
to the local LXD daemon and creates containers, using a rootfs image
from Glance, and attaching it to networks managed by Neutron (VXLANs in
our case). As far as
Public bug reported:
Some time ago, cloud-init version 21 was pushed to all LTS releases
including 20.04, and 18.04. It will be installed by default and present
in all LTS cloud images.
We are running LXD in OpenStack using nova-compute-lxd and unmodified
cloud images. Since cloud-init was upgrad
Thanks a lot for your work, Dan! Unfortunately, I wasn't able to pick up
the new bug from here, sorry for that. (It appears I did not get any
notification on your comments, need to check that)
The bridges are managed by OpenStack Neutron from Ubuntu cloud archives
and with names derived from the n
This backport to 18.04 LTS broke all our OpenStack compute nodes. We use
systemd-network to configure interfaces etc. and neutron-linuxbridge-
agent with some flat networks. In this scenario, the neutron agent
creates bridges for the flat networks and assigns them to physical
interfaces based on a
15 matches
Mail list logo
