[Yahoo-eng-team] [Bug 1478579] [NEW] When user in AD doesn't have ID field all user handlers error out

2015-07-27 Thread Victor Denisov
Public bug reported:

We have keystone integrated with AD.

'user_id_attribute' is set to 'info'. So, when our users first get
created in AD, they don't always have this field populated. When a user
does not have a populated 'info' attribute, all keystone queries fail,
not just queries or rows containing that user.

Jul 7 14:02:12 node-38 keystone-all ID attribute info not found in LDAP
object 

Some examples of how I see keystone should be have in this situation:

List all users - list only correct users and ignore invalid.

Authenticate invalid user - this request should not be authenticated.

** Affects: keystone
 Importance: Undecided
 Status: New

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

Title:
  When user in AD doesn't have ID field all user handlers error out

Status in Keystone:
  New

Bug description:
  We have keystone integrated with AD.

  'user_id_attribute' is set to 'info'. So, when our users first get
  created in AD, they don't always have this field populated. When a
  user does not have a populated 'info' attribute, all keystone queries
  fail, not just queries or rows containing that user.

  Jul 7 14:02:12 node-38 keystone-all ID attribute info not found in
  LDAP object 

  Some examples of how I see keystone should be have in this situation:

  List all users - list only correct users and ignore invalid.

  Authenticate invalid user - this request should not be authenticated.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1418214] [NEW] Snapshot created from volume doesn't have disk_format field

2015-02-04 Thread Victor Denisov
Public bug reported:

If an image doesn't have disk_format field then you can't change its
name. Horizon will be complaining about missing disk_format field.

Steps to reproduce.

- Spin up an instance from an image.
- Create a snapshot from the instance.
- Go to the list of images and try to update the snapshots name.

** Affects: glance
 Importance: Undecided
 Status: New

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

Title:
  Snapshot created from volume doesn't have disk_format field

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  If an image doesn't have disk_format field then you can't change its
  name. Horizon will be complaining about missing disk_format field.

  Steps to reproduce.

  - Spin up an instance from an image.
  - Create a snapshot from the instance.
  - Go to the list of images and try to update the snapshots name.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp