Public bug reported:
Hitting a recursion error when generating documentation for the
senlin-dashboard that seems to be indirectly caused by Horizon.
> maximum recursion depth exceeded in __instancecheck__
e.g.
https://review.opendev.org/c/openstack/senlin-dashboard/+/787090
I wrote a simple
Public bug reported:
We are getting frequent instances stuck indefinitely in BUILD without an
error message. This seems to be triggered by high concurrency (e.g.
build a lot of instances with terraform).
We have multiple synthetic instances that are being built and destroyed
ever 10 minutes and
Public bug reported:
If for some reason eventlet throws a timeout during a build event on the
compute a eventlet.Timeout exception might be thrown and cause an
UnboundException. This is because we only catch Exception, but Timeout is based
on BaseException.
Public bug reported:
The admin portion of the external dns integration for designate never
passes the url or region to the client. This means that the
implementation isn't region aware at all.
** Affects: neutron
Importance: Undecided
Assignee: Erik Olof Gunnar Andersson (eandersson
Public bug reported:
We are occasionally seeing MaxRetriesExceeded causing an "Exception
during message handling" error. This prevents the database from setting
the instance into error'd state and causes it to get stuck scheduling.
Example logs:
WARNING nova.scheduler.client.report [req-] Unable
Public bug reported:
When you configure a region_name for Ironic, an endpoint isn't properly
passed on to the ironic client. This means that the region_name won't be
respected.
The current workaround is to provide an api_endpoint (or
endpoint_override) for Ironic.
** Affects: nova
Public bug reported:
This command should be invalid, but Neutron (Rocky) allows it to be created.
> openstack security group rule create xxx --protocol vrrp --ingress
> --remote-ip --dst-port 112
Since iptables does not allow dst-port being passed. It would trigger the
following error on the
Public bug reported:
Starting with Django 1.9 users are kicked out to the login screen after
the web server is restarted. This is especially severe when running
Horizon with a high number of processes.
However, if Horizon is running with Django 1.8.19 or older, Horizon can
be restarted with
Public bug reported:
The Horizon filtering is not fully thread-safe. If two users are
simultaneously filtering a resource (e.g. projects or instances), and
threading is enabled (e.g. 2 or more threads in Apache). It's possible
that the wrong filter will display in the form input.
I was able to
'] == service_type:
-return service
+for endpoint in service['endpoints']:
+if endpoint['region'] == region:
+return service
return None
** Affects: keystone
Importance: Medium
Assignee: Erik Olof Gunnar Andersson
10 matches
Mail list logo
