yahoo-eng-team team mailing list archive

[OpenStack Infra <1607751@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/348881
Committed: https://git.openstack.org/cgit/openstack/python-keystoneclient/commit/?id=2b3258dcd0581e3a1291bd0e9277698b5631dced
Submitter: Jenkins
Branch:    master

commit 2b3258dcd0581e3a1291bd0e9277698b5631dced
Author: Boris Bobrov <bbobrov@xxxxxxxxxxxx>
Date:   Fri Jul 29 16:17:44 2016 +0300

    Do not send user ids as payload
    
    User ids are already in the URL. Keystone doesn't consume ids in the
    body.
    
    Change-Id: Ie90ebd32fe584dd1b360dc75a828316b1a9aedde
    Closes-Bug: 1607751


** Changed in: python-keystoneclient
       Status: In Progress => Fix Released

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

Title:
  Schema for enabling users breaks keystoneclient and other projects

Status in OpenStack Identity (keystone):
  Fix Released
Status in python-keystoneclient:
  Fix Released

Bug description:
  Patch https://review.openstack.org/#/c/344057/ introduced schema
  validation for enabling a user. In the schema, it forbid passing any
  parameters other than "enabled". It causes failures to at least rally:
  http://logs.openstack.org/88/348788/1/check/gate-rally-dsvm-keystone-
  v2api-rally/992e7ee/rally-
  plot/results.html.gz#/KeystoneBasic.create_user_set_enabled_and_delete/failures

  It happens because keystoneclient passes "id" and "enabled":
  https://github.com/openstack/python-
  keystoneclient/blob/master/keystoneclient/v2_0/users.py#L60-L62 , so
  the change broke anybody who uses the method in keystoneclient.

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