Due to a ping on IRC I wanted to summarize the situation here as it
seems this still affects people.
In nested LXD container we seem to have multiple issues:
- apparmor service failing to start (might need to work with LXD to sort out
why and how to fix it)
- if it doesn't work at least fail to
Public bug reported:
In master branch, when `auto_allocate` and `ndp_proxy` service plugin
were enabled simultaneously. Then, execute the below command to create a
`auto allocated topology create`, the neutron server log will report
ERROR [1].
openstack network auto allocated topology create --
Reviewed: https://review.opendev.org/c/openstack/neutron/+/844959
Committed:
https://opendev.org/openstack/neutron/commit/c25097b0b0da2af9021699036a69cd10e66533b1
Submitter: "Zuul (22348)"
Branch:master
commit c25097b0b0da2af9021699036a69cd10e66533b1
Author: Fernando Royo
Date: Tue Jun 7
** Also affects: nova/victoria
Importance: Undecided
Status: New
** Also affects: nova/train
Importance: Undecided
Status: New
** Also affects: nova/ussuri
Importance: Undecided
Status: New
** Also affects: nova/wallaby
Importance: Undecided
Status: New
-
** Changed in: cloud-archive
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1667736
Title:
gate-neutron-fwaas-dsvm-functional failure after r
** Changed in: cloud-archive
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1832210
Title:
fwaas netfilter_log: incorrect decode of log prefi
** Changed in: cloud-archive
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1831986
Title:
fwaas_v2 - unable to associate port with firewall
** Changed in: cloud-archive
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1667736
Title:
gate-neutron-fwaas-dsvm-functional failure after r
** Changed in: cloud-archive
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1831986
Title:
fwaas_v2 - unable to associate port with firewall
** Changed in: cloud-archive
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1832210
Title:
fwaas netfilter_log: incorrect decode of log prefi
Reviewed: https://review.opendev.org/c/openstack/nova/+/829248
Committed:
https://opendev.org/openstack/nova/commit/cd03bbc1c33e33872594cf002f0e7011ab8ea047
Submitter: "Zuul (22348)"
Branch:master
commit cd03bbc1c33e33872594cf002f0e7011ab8ea047
Author: Balazs Gibizer
Date: Tue Feb 15 14:3
Public bug reported:
Description
===
Using the libvirt driver and a host OS that uses cgroups v2 (RHEL 9,
Ubuntu Jammy), an instance with more than 16 CPUs cannot be booted.
Steps to reproduce
==
1. Boot an instance with 10 (or more) CPUs on RHEL 9 or Ubuntu Jammy
using
** Also affects: nova/ussuri
Importance: Undecided
Status: New
** Also affects: nova/wallaby
Importance: Undecided
Status: New
** Also affects: nova/victoria
Importance: Undecided
Status: New
** Also affects: nova/yoga
Importance: Undecided
Status: New
**
13 matches
Mail list logo
