schema service should not stop if Authentication fails with keystone
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
High
|
Sachin Bansal | |||
Trunk |
Fix Committed
|
High
|
Sachin Bansal |
Bug Description
R2.20 Build 71
In HA environments , it can so happen that the keystone auth may not be passing as soon those services come up.
For ex: mysql may not be ready.
When schema tries to start in this scenario, supervisor tries restarting it 5 times and gives up.
Below exception seems to be an unhandled exception which is causing schema to fail
The above is a description of an error in a Python program. Here is
the original traceback:
Traceback (most recent call last):
File "/usr/bin/
load_
File "/usr/lib/
main()
File "/usr/lib/
args)
File "/usr/lib/
self.
File "/usr/lib/
func(*args, **kwargs)
File "/usr/lib/
func(*args, **kwargs)
File "/usr/lib/
args.
File "/usr/lib/
retry_
File "/usr/lib/
self._headers = self._authentic
File "/usr/lib/
raise RuntimeError(
RuntimeError: Authentication Failure
Review in progress for https:/ /review. opencontrail. org/13051
Submitter: Sachin Bansal (<email address hidden>)