Public bug reported:
Hello,
We have a Mitaka deploy with several projects running, with 3 controller
nodes and 4 compute nodes. After restarting the L3 agent, for one
specific tenant the floating IPs that are attached to an instance are
not actually attached, L3 agent is throwing the following
Public bug reported:
In Icehouse if a user is unauthorized to access volumes, horizon shows a
popup upon login as well as when accesing volumes. In Juno, horizon
shows no warning upon login, and as one access volumes it shows a
stacktrace.
One way to reproduce is to remove cinder endpoint from
2 matches
Mail list logo
