← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1474501] Re: Bad search filter: None in query

 

*** This bug is a duplicate of bug 1454309 ***
    https://bugs.launchpad.net/bugs/1454309

I have verified the fix in https://review.openstack.org/#/c/184824/ does
fix my problem. Sorry, I missed the dup.  Thanks again.

** This bug has been marked a duplicate of bug 1454309
   Keystone v3 user/tenant lookup by name via OpenStack CLI client fails

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1474501

Title:
  Bad search filter: None in query

Status in Keystone:
  Triaged

Bug description:
  Environment: Ubuntu 14.04 with stable/kilo openstack packages
  installed

  I configured keystone to have one domain ('Default') configured with
  SQL as the backend to service the service users.  I configured a
  secondary domain ('ldap.vmware.com') to service all of the LDAP users.
  I did this using the multi-domain backend support.

  I was successful in creating users for the services (nova, cinder,
  glance, neutron, etc) and creating grants with admin role on service
  tenant.  Then I need to grant the admin role on a admin project on the
  ldap domain.  This is where things broke.

  In order to assign the admin role to the ldap user, I need to know the
  user id for the openstackclient.  To do this, I used:

  openstack --os-identity-api-version 3 --os-url
  "http://localhost:35357/v3"; --os-token 52c6706iDcaDAf7u45se user show
  --domain ldap.vmware.com vio-autouser@xxxxxxxxxx

  This command results in a 500 error from keystone.
  http://paste.openstack.org/show/375004/

  The root cause is that there is a 'None' in the search filter.
  "(&None(userPrincipalName=vio-autouser@xxxxxxxxxx))"

  Strangely, everything works perfectly if I stick with a single
  'Default' domain with LDAP backend.  It might be related to using the
  openstack CLI since that is also new in this environment.

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


References