Public bug reported:
This is actually a follow-up from
https://bugs.launchpad.net/neutron/+bug/2077879 as this is having a
slightly different use-case then was originally described.
Description
===
The problem is that FIP created in a geneve network, which is marked as
access_as_externa
** Changed in: neutron
Status: New => 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/2077879
Title:
[OVN] Router gateway does not have a chassis defined
Status in ne
Public bug reported:
With upgrade of Neutron from 23.2.0 to 24.0.0.b1 there is a 2 times
regression in response time for security groups listing.
Moreover, on 23.2.0 this listing could be coming from smth like cache
from time to time, as API response was super low after multiple
subsequent reques
Public bug reported:
With upgrade from 2023.1 to 2024.1 with driver ML2/OVS we've spotted a
significant (10 times) performance regression on some operations.
As best example - we can take security groups operations.
Neutron is running in eventlet, since uWSGI is not yet fully functional
for 2024
Public bug reported:
With Dalmatian release (2024.2) Keystone has finally added support for domain
managers:
https://review.opendev.org/c/openstack/keystone/+/924132
This type of users have a Domain scoped tokens and have a `manager` role
assigned to the domain.
With these privileges they are a
Hey,
I think this bug is actually belonging to the Nova project rather then
OpenStack-Ansible, as that's basically a question regarding specific
service source code rather then a deployment of this service.
Next to that, I'd say that conductor part is likely to be catched not
through nova-api but
Hey,
Despite I do see this was deployed with OpenStack-Ansible, it feels this
has very little to do with deployment method, but rather service itself.
With that I will transfer this bug to Nova project, so that they could
assist you.
** Project changed: openstack-ansible => nova
--
You receive
Public bug reported:
I do have a basic OpenStack-Ansible All-in-One deployment of the current
master branch.
Horizon SHA: a77818d745f25ed1e5b576760d3481f0f62ce042
Deployment was done following way:
1. git clone https://opendev.org/openstack/openstack-ansible
2. cd openstack-ansible
3. ./scripts/
it's weird that routers were scheduled to compute nodes - we usually
suggested using either standalone net nodes or controllers as
destination for L3 agents
Also we haven't seen issues like that really for a while now. Since Rocky is
not supported and reach it's End Of Life, at this point there i
Public bug reported:
Description
===
After upgrade of nova, including compute and conductor nodes, VM rebuild
fails. All computes, that have service state UP, and all conductors are
having version 66. Though, there was 1 compute during upgrade that is
DOWN, which does have version 64.
Du
Public bug reported:
Description
===
With upgrade from 2023.1 to 2023.2 when running nova-status upgrade
check it fails with exit code 2.
According to the documentation [1], this command was run with the new codebase
(2023.2) but before any service (api/conductor/scheduler/compute) was
** Changed in: openstack-ansible
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/2028809
Title:
Upgrades from Zed to Antel
Hey,
Sorry, I am inclined to say that the problem you are describing is
specifically nova issue. I will change affected project to Nova, as I
believe this bug report fits better there.
As far as I know regarding the topic - this is pretty much intended
behavior and a known dropback. The only work
Public bug reported:
After upgrading to Xena we started noticing slow queries that were written down
in mysql slow log.
Most of them were including next subquery:
SELECT DISTINCT ports.id AS ports_id FROM ports, networks WHERE
ports.project_id = '' OR ports.network_id = networks.id AND
networks
There's a typo in flavor specification I was copy-pasting several times
;(
| properties | resouces:PCPU='4', trait:CUSTOM_HIGHCPU='required' |
s/resouces/resources/
** Changed in: nova
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
When instance is being created from flavor with `--property
resources:PCPU=4`, generated XML doesn't include vcpupin directives that
basically does pinning.
Instead only 4 is present in libvirt for
flavor with PCPU resource.
Nova version: Xena
Sample flavor that's being use
Public bug reported:
Description
===
When neutron port has MAC address defined in upper case and libvirt stores MAC
in XML in lower case, migration is failed with KeyError:
```
Sep 30 10:31:38 cc-compute08-dx1 nova-compute[3054313]: 2021-09-30 10:31:38.028
3054313 ERROR nova.virt.libvir
Public bug reported:
Description
===
In case, when some request (ie instance shutdown) is sent to the compute
that is not available, request continue hanging in queue. In the
meanwhile, instance can be evacuated from this host to the new available
compute. However once original compute ho
Public bug reported:
Issue descripton
Train is supposed to be the last release that support python 2.7. In the
meanwhile, https://review.opendev.org/c/openstack/keystone/+/755736 has been
backported back to Train.
It implements usage of the weakref.finalize which is valid attri
Public bug reported:
Description
===
When you use templates for cell creation and re-run create_cell command,
duplicate cell will be created
This happens because logic is broken here for templates:
https://opendev.org/openstack/nova/src/commit/9e5feb051c15166988e87b10132927135bd56884/nov
Fix has been released for Victoria
** Changed in: openstack-ansible
Status: New => 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/1846198
Title:
packet loss during
** Changed in: openstack-ansible
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1718356
Title:
Include default config fil
This has been fixed for a while and IMAGES_ALLOW_LOCATION is present in
local_settings.py
** Changed in: openstack-ansible
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboar
t;http://172.29.236.100:9292/v2/";,
>>> token=conn.auth_token, insecure=True)
>>> glanceclient.schemas.get('image').raw()['properties']['disk_format']['enum']
[None, 'raw']
>>>
[1] https://docs.openstack.org/api-ref/im
7:37:11.620 17205 ERROR
neutron_vpnaas.services.vpn.device_drivers.ipsec
2019-10-08 17:37:11.620 17205 ERROR
neutron_vpnaas.services.vpn.device_drivers.ipsec
[1] https://opendev.org/openstack/neutron-
vpnaas/src/branch/master/neutron_vpnaas/services/vpn/device_drivers/libreswan_ipsec.py#L22
**
Public bug reported:
Description
===
During routine operations or things like running regular tempest checks
nova-compute tries to reach database and fails with DBNotAllowed error:
https://logs.opendev.org/33/660333/10/check/openstack-ansible-deploy-aio_metal-ubuntu-bionic/97d8bc3/logs/h
26 matches
Mail list logo
