Hi @mohan-hasoln,
I can not reproduce the issue.
Could you attached syslog and AMF trace on the ticket ?
B.R/Thang
---
** [tickets:#3329] amfd: saAmfSUPresenceState is INSTANTIATED after LOCK-IN
command**
**Status:** review
**Milestone:** 5.23.03
**Created:** Thu Dec 15, 2022 05:29 PM UTC by Mohan Kanakam
**Last Updated:** Fri Dec 16, 2022 01:55 PM UTC
**Owner:** Mohan Kanakam
Steps to reproduce:
1) Start opensaf on one node
2) Upload the 2n redundancy configuration of amf demo in sample directory with
saAmfSGAutoRepair and SUFailover are enabled.
3) Perform unlock-in and unlock operations.
3) Add the saAmfComponentErrorReport() in amf_csi_remove_callback.
4) Add the sleep of 5 seconds in start() function of instantiation script.
4)Perform lock operation, and waited till "Presence State UNINSTANTIATED =>
UNINSTANTIATED" in syslog and perform lock-in operation immediately.
This will cause the below inconsistent state that is admin state is locked-in
and presence state is instantiated:
safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
saAmfSUAdminState=LOCKED-INSTANTIATION(3)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets