yahoo-eng-team team mailing list archive

[Julie Pichon <1167416@xxxxxxxxxxxxxxxxxx>]

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 applied to the string itself -
https://github.com/openstack/horizon/blob/495dcb94e6f724fee534d4cb23daccf7580e4d92/openstack_dashboard/dashboards/admin/users/forms.py#L195)

I'm also removing the keystone component from this bug -- the strings
with the failure information originated from Horizon.

** Changed in: horizon
       Status: Confirmed => Invalid

** Changed in: horizon
    Milestone: havana-1 => None

** Changed in: keystone
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1167416

Title:
  Lazy translation object not translated when setting user's default
  role to a project they have a role on

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in OpenStack Identity (Keystone):
  Invalid

Bug description:
  Steps to reproduce (related to bug 1161963):
   1. As an admin, go to Admin -> Users and Edit the demo user
   2. Change the demo's email. It's not possible to submit the form without a primary project so select "demo"
   3. Try to edit the demo user again to revert your change. "demo" will be preselected as a Primary project. Submit the form.
   4. A message "Error: Unable to update (<django.utils.functional.__proxy__ object at 0x7f6a818d7790>,) for the user" is displayed.

  The actual list of attributes that failed should be displayed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1167416/+subscriptions