As a services engineer, I need tool which finds whether keystone SSL issue exists
There is a known and quite common keystone SSL issue, which can be identified based on logs. Example of faulty log:
{noformat}
<188>Aug 8 00:50:58 node-18 keystone-
<187>Aug 8 00:50:58 node-18 keystone-
140507666065224
140507666065224
unable to load certificate
<187>Aug 8 00:50:58 node-18 keystone-
Traceback (most recent call last):
File "/usr/lib/
result = method(context, **params)
File "/usr/lib/
return f(self, context, *args, **kwargs)
File "/usr/lib/
CONF.
File "/usr/lib/
raise subprocess.
CalledProcessError: Command 'openssl' returned non-zero exit status 3
<190>Aug 8 00:50:58 node-18 keystone-
<188>Aug 8 00:53:58 node-18 keystone-
<187>Aug 8 00:53:58 node-18 keystone-
139865734448968
139865734448968
unable to load certificate
{noformat}
The tool should return human-readable result, or be part of a more complex log analysis tool.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Oleksandr Kyrylchuk
- Direction:
- Needs approval
- Assignee:
- Oleksandr Kyrylchuk
- Definition:
- New
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Oleksandr Kyrylchuk
- Completed by
- Oleksandr Kyrylchuk