Account is locked out and cannot have password updated.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
We are seeing this in tempest testing. In some tempest runs the test to change the user password fails because the account is locked out. Example traceback can be found at http://
2017-07-20 01:14:10.769485 | tempest.
2017-07-20 01:14:10.769531 | -------
2017-07-20 01:14:10.769545 |
2017-07-20 01:14:10.769562 | Captured traceback:
2017-07-20 01:14:10.769580 | ~~~~~~~~~~~~~~~~~~~
2017-07-20 01:14:10.769602 | Traceback (most recent call last):
2017-07-20 01:14:10.769639 | File "tempest/
2017-07-20 01:14:10.769672 | self._update_
2017-07-20 01:14:10.769707 | File "tempest/
2017-07-20 01:14:10.769732 | original_
2017-07-20 01:14:10.769769 | File "tempest/
2017-07-20 01:14:10.769801 | resp, _ = self.post(
2017-07-20 01:14:10.769831 | File "tempest/
2017-07-20 01:14:10.769864 | return self.request(
2017-07-20 01:14:10.769895 | File "tempest/
2017-07-20 01:14:10.769919 | self._error_
2017-07-20 01:14:10.769951 | File "tempest/
2017-07-20 01:14:10.769979 | raise exceptions.
2017-07-20 01:14:10.770005 | tempest.
2017-07-20 01:14:10.770054 | Details: {u'code': 401, u'title': u'Unauthorized', u'message': u'The account is locked for user: b99de038ad484b1
2017-07-20 01:14:10.770068 |
2017-07-20 01:14:10.770081 |
2017-07-20 01:14:10.770099 | Captured pythonlogging:
2017-07-20 01:14:10.770118 | ~~~~~~~
2017-07-20 01:14:10.770193 | 2017-07-20 00:54:16,576 23533 INFO [tempest.
2017-07-20 01:14:10.770284 | 2017-07-20 00:54:16,576 23533 DEBUG [tempest.
2017-07-20 01:14:10.770331 | Body: {"user": {"password": "M8*qsS56SFEo%s4", "original_
2017-07-20 01:14:10.770475 | Response - Headers: {u'content-type': 'application/json', u'date': 'Thu, 20 Jul 2017 00:54:16 GMT', u'vary': 'X-Auth-Token', u'server': 'Apache/2.4.18 (Ubuntu)', u'connection': 'close', u'x-openstack-
2017-07-20 01:14:10.770528 | Body: {"error": {"message": "The account is locked for user: b99de038ad484b1
2017-07-20 01:14:10.770599 | 2017-07-20 00:54:16,614 23533 INFO [tempest.
2017-07-20 01:14:10.770669 | 2017-07-20 00:54:16,614 23533 DEBUG [tempest.
2017-07-20 01:14:10.770709 | Body: {"user": {"password": "H1!w*#WDyqGDBod", "original_
2017-07-20 01:14:10.770857 | Response - Headers: {u'content-type': 'application/json', u'date': 'Thu, 20 Jul 2017 00:54:16 GMT', u'vary': 'X-Auth-Token', u'server': 'Apache/2.4.18 (Ubuntu)', u'connection': 'close', u'x-openstack-
2017-07-20 01:14:10.770914 | Body: {"error": {"message": "The account is locked for user: b99de038ad484b1
2017-07-20 01:14:10.770929 |
2017-07-20 01:14:10.770942 |
2017-07-20 01:14:10.770960 | Captured traceback-1:
2017-07-20 01:14:10.770978 | ~~~~~~~
2017-07-20 01:14:10.771001 | Traceback (most recent call last):
2017-07-20 01:14:10.771034 | File "tempest/
2017-07-20 01:14:10.771062 | original_
2017-07-20 01:14:10.771096 | File "tempest/
2017-07-20 01:14:10.771120 | original_
2017-07-20 01:14:10.771157 | File "tempest/
2017-07-20 01:14:10.771188 | resp, _ = self.post(
2017-07-20 01:14:10.771218 | File "tempest/
2017-07-20 01:14:10.771251 | return self.request(
2017-07-20 01:14:10.771282 | File "tempest/
2017-07-20 01:14:10.771306 | self._error_
2017-07-20 01:14:10.771346 | File "tempest/
2017-07-20 01:14:10.789250 | raise exceptions.
2017-07-20 01:14:10.789306 | tempest.
2017-07-20 01:14:10.789359 | Details: {u'code': 401, u'title': u'Unauthorized', u'message': u'The account is locked for user: b99de038ad484b1
I'm not sure if this is a keystone issue or a tempest test bug so going to file it against both then start tracking it with elastic-recheck.
Changed in keystone: | |
status: | New → Invalid |
no longer affects: | tempest |
Is this issue still poping up?