v2.0 calls
on the v3 endpoint.
This was noticed when neutronclient had to authenticate (which is
usually not the case from horizon, since we have the token).
** Affects: horizon
Importance: Undecided
Assignee: Vincent Untz (vuntz)
Status: In Progress
--
You received this bug
Public bug reported:
The registry_client_* options are missing from glance-scrubber.conf by
default, but it would be very useful to have them there: it took me
quite some time to find out how to make glance-scrubber work with
keystone using SSL with custom certificates, and
Public bug reported:
glance-scrubber fails to work with:
08:52:43 2016-02-21 07:52:43.009 16387 ERROR glance.registry.client.v1.client
[req-3200d95d-a3d7-4347-a4a3-9e00dc2fbc53 glance service - - -] Registry client
request GET /images/detail raised AuthUrlNotFound
08:52:43 2016-02-21
Public bug reported:
This is really the same bug as
https://bugs.launchpad.net/horizon/+bug/1457028 except that it's for the
NG launch instance dialog.
** Affects: horizon
Importance: Undecided
Assignee: Vincent Untz (vuntz)
Status: In Progress
--
You received this bug
Public bug reported:
We just happened to have broken dhcp because the dhcp ports were in
binding_failed state.
We tried to disable/enable dhcp again, but apparently (not 100% sure,
unfortunately), disabling didn't remove the ports (assuming that it was
because they were in binding_failed state)
Public bug reported:
This is Kilo specific (and works in Liberty, thanks to the move to os-
brick).
When attaching a volume, I'm seeing a failure like this:
Traceback (most recent call last):
File /usr/lib/python2.7/site-packages/nova/virt/block_device.py, line
255, in attach
Public bug reported:
I'm trying to create an image from an instance with non-ascii characters
in the name, by using this command:
nova image-create e6bd72dd-ab8f-4802-8e29-faf90eeceb1c ééé
It turns out that nova-compute fails with this:
015-04-22 16:23:20.537 8401 ERROR
Public bug reported:
From time to time, I could see that neutron net-external-list was
returning something empty for a non-admin user while this is not true on
my setup.
After quite some debugging, it turned out that it was failing because of
the policy (using the default policy.json, btw):
8 matches
Mail list logo