If unexpected exceptions are seen while launching SVMs, not enough info is collected in the logs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
New
|
Medium
|
Rudra Rugge | ||
R2.20 |
Won't Fix
|
Medium
|
Rudra Rugge | ||
Trunk |
Won't Fix
|
Medium
|
Rudra Rugge |
Bug Description
R2.20 Build 74 Ubuntu 14.04
In one of the manual tests, the compute and glance endpoints were configured incorrectly in keystone.
Service instances would not launch because of this.
But the logs in contrail-
08/10/2015 04:17:12 PM [nodec2:
08/10/2015 04:17:12 PM [nodec2:
08/10/2015 04:17:24 PM [nodec2:
08/10/2015 04:17:24 PM [nodec2:
08/10/2015 04:17:55 PM [nodec2:
08/10/2015 04:17:55 PM [nodec2:
08/10/2015 04:18:25 PM [nodec2:
In /usr/lib/
except Exception as e:
return None
Below was the exception detail which was missing (was got only after manually adding a 'raise e' stmt
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/
self.
File "/usr/lib/
vm_uuid = self._create_
File "/usr/lib/
name=si.flavor)
File "/usr/lib/
proj_name, False, **kwargs)
File "/usr/lib/
raise e
EndpointNotFound
Marking this as won't fix as this has not been seen in the latest releases. Please reopen if you see the issue again.