-
Bug
-
Resolution: Done
-
Lowest
-
None
-
None
-
None
I've been running the ODL Clustering CSIT job from stable/oxygen and analyzing failures, as part of the clustering stabilization effort.
During one of these runs, the cluster fails to go to sync status after ODL is restarted (Tell based False). I looked at the node that failed to sync, and see that karaf took just a little over 7 minutes to start up for this test case.
Here are the relevant karaf logs:
Jun 29, 2018 3:43:47 PM org.apache.karaf.main.Main launch
INFO: Installing and starting initial bundles
Jun 29, 2018 3:43:47 PM org.apache.karaf.main.Main launch
INFO: All initial bundles installed and set to start
Jun 29, 2018 3:43:47 PM org.apache.karaf.main.lock.SimpleFileLock lock
INFO: Trying to lock /tmp/karaf-0.8.3-SNAPSHOT/lock
Jun 29, 2018 3:43:47 PM org.apache.karaf.main.lock.SimpleFileLock lock
INFO: Lock acquired
Jun 29, 2018 3:43:47 PM org.apache.karaf.main.Main$KarafLockCallback lockAquired
INFO: Lock acquired. Setting startlevel to 100
Jun 29, 2018 3:50:48 PM org.apache.karaf.main.Main launch
INFO: Installing and starting initial bundles
Jun 29, 2018 3:50:49 PM org.apache.karaf.main.Main launch
INFO: All initial bundles installed and set to start
Jun 29, 2018 3:50:49 PM org.apache.karaf.main.lock.SimpleFileLock lock
INFO: Trying to lock /tmp/karaf-0.8.3-SNAPSHOT/lock
Jun 29, 2018 3:50:49 PM org.apache.karaf.main.lock.SimpleFileLock lock
INFO: Lock acquired
Jun 29, 2018 3:50:49 PM org.apache.karaf.main.Main$KarafLockCallback lockAquired
INFO: Lock acquired. Setting startlevel to 100
I'll also attach the (annotated) karaf log.
- relates to
-
NETVIRT-1315 Troubleshooting Controller CSIT
- In Progress
-
NETVIRT-1386 Better permanent solution for QosAlertGenerator which shall not modify the logging configuration at runtime
- Resolved
1.
|
get jstack working in csit | Verified | Jamo Luhrsen |