yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #80337
[Bug 1847727] Re: CI: failing on CRITICAL may be still too strong
Chris Dent correctly suggested that the message comes from keystone. Is
it possible to lower the severity of this particular event?
(Originally reported to Placement because only it has been found to log
this message.)
** Also affects: keystone
Importance: Undecided
Status: New
--
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/1847727
Title:
CI: failing on CRITICAL may be still too strong
Status in OpenStack Identity (keystone):
New
Status in kolla-ansible:
Triaged
Bug description:
Temporary unavailability of keystone makes placement-api cry:
/var/log/kolla/placement/placement-api.log
2019-10-10 21:12:50.615 21 CRITICAL keystonemiddleware.auth_token [req-c1a6e19a-cfdd-4b13-8943-dde5619d7711 900cc8bc95494bd282da6d8904014168 64d1bb7662d448e68696dd0cccc855dc - default default] Unable to validate token: Failed to fetch token data from identity server: ServiceError: Failed to fetch token data from identity server
2019-10-10 21:14:45.753 21 CRITICAL keystonemiddleware.auth_token [req-c1a2b9a0-75d7-4870-a4d9-fdb46dee6042 900cc8bc95494bd282da6d8904014168 64d1bb7662d448e68696dd0cccc855dc - default default] Unable to validate token: Failed to fetch token data from identity server: ServiceError: Failed to fetch token data from identity server
Cycle: Train
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1847727/+subscriptions