Okay, after lots of talk in #openstack-neutron we figured it out:
- networking-baremetal was released before the library freeze, as usual
- so was neutron-lib
This means if you run tests on (master or latest release) networking-
baremetal, it pulls in:
- 2023.2 neutron-lib
- 2023.1 neutron
Whic
Ironic CI didn't catch it because... it seems to be a neutron bug?
https://github.com/openstack/neutron/blob/master/neutron/db/qos/models.py#L135
still exists even though https://github.com/openstack/neutron-
lib/commit/673e48a1890c721654ce0de9cd9e0897c791bd6a is merged
** Project changed: networ
You have been subscribed to a public bug:
Hi,
Building networking-baremetal 6.2.0 together with the latest neutron-lib 3.8.0
in my bookworm-backports build server, I get a test discovery error from stestr
(see Debian package build log below). Apparently, it looks like it's because of
this comm
Hello Roman:
This is the default security policy for non-admin users. By default, a
non-admin user cannot create a port defining the flags "--disable-port-
security" or "--enable-port-security". A non-admin user must create a
port with "--enable-port-security" implicitly defined.
To avoid this de
Public bug reported:
The host aggregate cache reports an error when multiple images are not
sorted during deduplication
* Step-by-step reproduction steps:
Create aggregate
Create images
Aggregate cache images
[root@control1 ~]# openstack aggregate create agg1
+---+-
Public bug reported:
Hi. anyone can guide me how to configure the olla ansible- gloal.yaml
file correctly so that all the essentials services of openstack should
be installed with a running state?
** Affects: horizon
Importance: Undecided
Status: New
--
You received this bug notif
This issue was fixed in the openstack/nova 25.2.1 release.
** Changed in: nova/yoga
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/
Public bug reported:
When attempting to verify neutron change[1], we discovered that despite
options in DHCPv6 ADV and REQ/REPLY are correct network booting still
fails.
When comparing traffic capture between openvswitch+neutron-dhcp-agent setup to
the ovn setup a significant difference is that:
Reviewed: https://review.opendev.org/c/openstack/neutron/+/893962
Committed:
https://opendev.org/openstack/neutron/commit/8cba9a2ee86cb3b65645674ef315c14cfb261143
Submitter: "Zuul (22348)"
Branch:master
commit 8cba9a2ee86cb3b65645674ef315c14cfb261143
Author: Rodolfo Alonso Hernandez
Date:
9 matches
Mail list logo