Public bug reported:
If we use an invalid CIDR as the source_ip_address, such as
2:3dc2:c893:514a:966b:7969:42b0:00900/108, it can still be successfully
submitted after creating a firewall rule. The main reason is that
netaddr formats this address.
The command is like:
openstack firewall group
This bug was fixed in the package glance -
2:29.0.0~b2+git2024080717.695fcb67-0ubuntu1~cloud0
---
glance (2:29.0.0~b2+git2024080717.695fcb67-0ubuntu1~cloud0) noble-dalmatian;
urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
glance (2:29.0.0~b2+git2024080
This bug was fixed in the package horizon -
4:25.0.0+git2024080809.d171cee3-0ubuntu1~cloud0
---
horizon (4:25.0.0+git2024080809.d171cee3-0ubuntu1~cloud0) noble-dalmatian;
urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
horizon (4:25.0.0+git2024080809.d1
This bug was fixed in the package horizon -
4:25.0.0+git2024080809.d171cee3-0ubuntu1~cloud0
---
horizon (4:25.0.0+git2024080809.d171cee3-0ubuntu1~cloud0) noble-dalmatian;
urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
horizon (4:25.0.0+git2024080809.d1
Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/924059
Committed:
https://opendev.org/openstack/ovn-octavia-provider/commit/efd63d1721742400e7ba2c0bfc55249ef15fc549
Submitter: "Zuul (22348)"
Branch:master
commit efd63d1721742400e7ba2c0bfc55249ef15fc549
Author: Chris B
Public bug reported:
I investigated the customer's issue and concluded that this code:
https://opendev.org/openstack/neutron/src/commit/0807c94dc9843fff318c21d1f6f7b8838f948f5f/neutron/agent/l3/dvr_fip_ns.py#L155-L160
which deletes the fip-namespace during router processing, leads to connectivity
Reviewed:
https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/926201
Committed:
https://opendev.org/openstack/neutron-tempest-plugin/commit/0274381d31b7a5e6dff7a8e3ce8ff53d5c97d443
Submitter: "Zuul (22348)"
Branch:master
commit 0274381d31b7a5e6dff7a8e3ce8ff53d5c97d443
Author: ya
Public bug reported:
During the processing of a router by the L3 agent in
`agent_mode={dvr|dvr_snat}`, we create a floatingip_agent_gateway port.
The code in the L3-agent [0] and the neutron-server [1] assumes that there
should be only one such port per L3-agent per network. However, this is no
Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/923196
Committed:
https://opendev.org/openstack/ovn-octavia-provider/commit/ae1540bb1a04464c7065e542ec5e981947247f3b
Submitter: "Zuul (22348)"
Branch:master
commit ae1540bb1a04464c7065e542ec5e981947247f3b
Author: Vasyl S
Public bug reported:
nova 26.2.1 (zed) looks like same code path in master
If we issue a resize the _terminate_volume_connections() function in
nova/compute/manager.py will call cinder to delete the attachments, but
we never check the actual volume status before doing this so if the
volume(s) is
10 matches
Mail list logo