Public bug reported:
Hi,
I have a user (rallyadmin) that is given the admin role to the domain
(rally). If I pull in the keystone v3 policy.json file to horizon (copy
it to the location holding keystone_policy.json) I can create projects
within the domain.
However, for some reason, I cannot crea
I've added Keystone, in case this is keystone-related.
Basically, if the API is v2.0, then we support pagination on the
Identity => Projects page, which can help with performance.
If the API is v3, we don't perform any pagination. Essentially, if
someone has hundreds of projects, then this page i
Public bug reported:
Hello,
The Identity dashboard, responsible for showing Domains, Users, Groups,
Projects, and Roles, suffers terribly when viewing items like Projects.
Our private production runs about 435 projects, and slightly more than
350 users.
For example, to view all projects, the UI
Public bug reported:
The compute resource tracker is ignoring values coming from compute
drivers such as vSphere. Specifically, the resource tracker is accepting
disk_total from the driver, but not disk_available and disk_used.
We've checked the vSphere driver, and the driver is indeed reporting
Public bug reported:
The MAC Learning checkbox when editing a port does not take into account
the fact that the port must not have port security enabled nor security
groups assigned to it. The UI will generate a non-descriptive error if
either of these are enabled when the user tries to enable MA
Public bug reported:
This policy file works using the CLI clients; however, it does NOT work
with Horizon, yet again. This is the same problem I observed with
Mitaka, that forced me to revert to the liberty policy file. I've had
to do that again.
Error message for user who just logged in linked
Public bug reported:
Pulled down project from git (stable/newton).
Used OpenStack global requirements and installed in a virtualenv under
Ubuntu 14.04 (python 2.7).
Problem manifested during compress operation, when setting up the web
application for use.
Code excerpt attached.
To workaround,
Public bug reported:
If a user wishes to upload an image to Glance that is an OVA file, the
import fails because the disk_format gets marked as "bare" and the
container_format is not taken into account.
I've checked the dashboard for images and found this problem can be very
easily fixed by check
Looking at 2.0 vals was removed.
This appears to be an issue still because if we are selecting >-1.16.0
and 2.0 gets selected vals is missing from the line.
https://github.com/paramiko/paramiko/blob/2.0/paramiko/rsakey.py#L39
We need to remove the invalid state.
** Changed in: nova
Statu
Public bug reported:
When creating a keypair, we get the following tracelog in nova api log:
2016-11-03 14:47:35.484 649 ERROR nova.api.openstack.extensions
[req-4aeca8b7-2616-4eea-a092-c18c669ba91b 57b7e0d93f354d789392d8f06561f85f
2a12f4e0d4e54a18a7102087eb7def77 - - -] Unexpected exception in
Public bug reported:
We have a multi-domain configuration in our private cloud that I've had
to revert to using the Liberty policy.v3cloudsample.json file instead of
Mitaka or master.
Horizon is generating the following trace when a domain admin is trying
to look at projects/users:
[pid: 22842|a
Would like to hear from folks - this is impacting a lot of projects, and
people can't build from git branches...
IMO this is extremely critical and we need to get a response.
** Also affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you ar
I added oslo.messaging to this. If it needs to be marked duplicate then
that is fine, but considering nobody can build Openstack in this state,
there needs to be some urgency on this. I tested a couple of
workarounds, but the best one so far for us has been to uninstall amqp
and reinstall the 1.4
Added affected projects that we've tested so far. I have not
specifically tested Glance in my sandbox. Overall, AMQP 2.0 is breaking
everything. Our automation is working around the problem by
uninstalling 2.0 and installing 1.4.9 manually.
Would like to hear feedback on this. Some folks are s
Public bug reported:
We are running nova from the stable/mitaka branch (not using packages).
Our build process has flagged this. Previously, when we've built, we've
used the requirements.txt file to pull in dependencies, and one of the
dependencies pulls in AMQP.
Initial investigation leads us
15 matches
Mail list logo
