config_object_error log should not assume a request context always present
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
New
|
Undecided
|
Unassigned |
Bug Description
If there is a db entry that is not in correct state, following traceback is observed on startup of api-server
The above is a description of an error in a Python program. Here is
the original traceback:
Traceback (most recent call last):
File "/usr/lib/
result = fn(obj_type, uuid_list)
File "/usr/lib/
obj_uuid, None, obj_type, 'dbe_resync:
File "/usr/lib/
id, fq_name_str, obj_type, operation, err_str)
File "/usr/lib/
self.
File "/usr/lib/
apiConfig.url = get_request().url
File "/usr/lib/
return gevent.
AttributeError: 'greenlet.greenlet' object has no attribute 'api_context'