[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
Sigh. This appears to be how the python logging module works.
http://docs.python.org/2/library/logging.html
Under logger.debug they have an example use of 'extra'...and then under
it states:
"If you choose to use these attributes in logged messages, you need to
exercise some care. In the above
This bug does not have impact to Horizon, the issue is limited only to
the client CLI.
Horizon has its own authentication backend that will take care of
authenticating with Keystone V3 endpoint. The related patch is in here:
https://github.com/gabrielhurley/django_openstack_auth/pull/41
Once Hor
This bug does not have impact to Horizon, the issue is for the client
CLI.
Horizon has its own authentication backend that will take care of
authenticating with Keystone V3 endpoint. The related patch is in here:
https://github.com/gabrielhurley/django_openstack_auth/pull/41
Once Horizon gets ho
Public bug reported:
rootwrap script return 0 when when it fail finding a given command or
when a command doesn't have a filter.
Patch coming with more detail.
** Affects: quantum
Importance: Undecided
Status: Invalid
** Tags: grizzly-backport-potential
** Tags added: grizzly-ba
Hi,
Thanks for reporting this.
It is not a bug and is something that landed for Havana. What you're
looking for is [0] which was introduced by this commit [1] the same that
removed the bin/ folder.
[0] https://github.com/openstack/glance/tree/master/glance/cmd
[1]
https://github.com/openstack/g
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: python-keystoneclient
Status: New => Confirmed
** Changed in: python-keystoneclient
Importance: Undecided => Critical
** Also affects: keystone/folsom
Importance: Undecided
Statu
The way we update the user now, we don't track the failed bits anymore,
therefore the lazy translation error doesn't happen anymore.
(For the record, this was happening because we were storing the strings
as tuples inside a list, so the force_unicode mapping function never had
a chance of being ap
Sorry for the noise it has a with clause it should close the connection
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1172167
Title
9 matches
Mail list logo