- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -1,7 +1,6 @@
There is a case SU is stuck in TERMINATING presence state. The senario is as
below
PI SU contains 2 NPI components. Before comp 1 reach the max restart to
escalate from comp restart to Su restart. It just receive the instantiate CLI
command.
-The SU will move from INSTANTIATED to TERMINATING. In this phase comp 2 was
cleaned up and uninstantiated successfully. Then comp 1 is instantiated. And
amfnd do nothing in this situation.
-In this case, need to run SU fsm with instantiate event.
+The SU will move from INSTANTIATED to TERMINATING. In this phase comp 2 was
cleaned up and uninstantiated successfully. Then comp 1 is instantiated. At
this time comp 1 already terminated.
+So it must ignore INSTANTIATED in this case. The component will be recovered
due to component register timeout later.
-Another case amfnd send callback parameters to component . The amf client down
and the callback will be failed. In this case, we also need to process error
recover for the component.
~~~~
- **Comment**:
commit 2c515e6367d26fd74ffc7800cd6570fbfc49bc6a (HEAD -> develop,
origin/develop, ticket-3160)
Author: thang.d.nguyen <[email protected]>
Date: Tue Mar 3 18:11:14 2020 +0700
amfnd: reset component register once it is terminated [#3160]
Reset component register once it is terminated to avoid
process instantiate event in late.
---
** [tickets:#3160] amf: SU is stuck in TERMINATING presence state **
**Status:** review
**Milestone:** 5.20.05
**Created:** Thu Feb 27, 2020 01:02 AM UTC by Thang Duc Nguyen
**Last Updated:** Thu Feb 27, 2020 07:44 AM UTC
**Owner:** Thang Duc Nguyen
There is a case SU is stuck in TERMINATING presence state. The senario is as
below
PI SU contains 2 NPI components. Before comp 1 reach the max restart to
escalate from comp restart to Su restart. It just receive the instantiate CLI
command.
The SU will move from INSTANTIATED to TERMINATING. In this phase comp 2 was
cleaned up and uninstantiated successfully. Then comp 1 is instantiated. At
this time comp 1 already terminated.
So it must ignore INSTANTIATED in this case. The component will be recovered
due to component register timeout later.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list._______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
