[CONTROLLER-1863] Bundles in error state after karaf restart by "shutdown -r" Created: 18/Sep/18 Updated: 02/May/23 |
|
| Status: | Open |
| Project: | controller |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Gobinath Suganthan | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pick-next, pt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
This JIRA had been raised in openflowplugin https://jira.opendaylight.org/browse/OPNFLWPLUG-1025 - (Karaf reboot with shutdown -r -f, bundles are entering to Failure state and SB communication are lost) The following errors were seen in the karaf logs "java.lang.IllegalAccessException: no such constructor:org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.inet.types.rev130715.IpAddress". Complete logs attached This seems to be related to https://jira.opendaylight.org/browse/CONTROLLER-1627 which was fixed in Boron. Similar exceptions like above were observed during the cluster restart scenario through quarantine then. The fix was to restart the jvm itself rather than the karaf. Ref https://git.opendaylight.org/gerrit/#/c/60485/ But I observed that the code block with fix doesn’t even get triggered while executing “shutdown -r”. Doesn’t the "shutdown -r" fall under quarantine restart ?
|
| Comments |
| Comment by Robert Varga [ 23/Apr/20 ] |
|
Is this still reproducible with Sodium or Magnesium? |
| Comment by Gobinath Suganthan [ 27/Apr/20 ] |
|
dheenab Could you please check this? |
| Comment by dheenadayalan b [ 30/Apr/20 ] |
|
rovarga, yes this reproducible in magnesium only[with similar error], however for sodium JVM crashed during restart. Respective logs have been attached |