Can you please update the ticket with the change sets?
---
** [tickets:#2916] amfd: SU remains OUT_OF_SERVICE when unlock SU during
cluster start up**
**Status:** fixed
**Milestone:** 5.18.08
**Created:** Tue Aug 21, 2018 11:09 PM UTC by Minh Hon Chau
**Last Updated:** Thu Aug 23, 2018 10:16 PM UTC
**Owner:** Minh Hon Chau
The problem happens in NWay Active SUs, all SUs have the assignment, except SU
in the SC-1.
Scenario: It is single step upgrade, after cluter reboot, SMF will issue unlock
command during cluster startup.
During cluster starting up, SC-2 has already joined cluster and before the SC-1
(standby) joins the cluster, issue unlock the SUs in SC-1 and SC-2. Only SU in
SC-2 becomes IN_SERVICE.
3001 2018-08-16T02:52:00.986+0200 SC-2 safApp=safAmfService NO: "Admin
op "UNLOCK" initiated for 'safSu=SC-1,safSg=NWA,safApp=QWE-ABC-Amfproxy',
invocation: 425201762315"
3002 2018-08-16T02:52:00.987+0200 SC-2 safApp=safAmfService NO:
"safSu=SC-1,safSg=NWA,safApp=QWE-ABC-Amfproxy AdmState LOCKED => UNLOCKED"
3003 2018-08-16T02:52:00.988+0200 SC-2 safApp=safAmfService NO: "Admin
op done for invocation: 425201762315, result 1"
3004 2018-08-16T02:52:00.990+0200 SC-2 safApp=safAmfService NO: "Admin
op "UNLOCK" initiated for 'safSu=SC-2,safSg=NWA,safApp=QWE-ABC-Amfproxy',
invocation: 429496729612"
3005 2018-08-16T02:52:00.990+0200 SC-2 safApp=safAmfService NO:
"safSu=SC-2,safSg=NWA,safApp=QWE-ABC-Amfproxy AdmState LOCKED => UNLOCKED"
3006 2018-08-16T02:52:00.991+0200 SC-2 safApp=safAmfService NO:
"safSu=SC-2,safSg=NWA,safApp=QWE-ABC-Amfproxy ReadinessState OUT_OF_SERVICE =>
IN_SERVICE"
When "cluster init timeout" amfd will start assignment of all SUs
3069 2018-08-16T02:52:10.058+0200 SC-2 safApp=safAmfService NO: "Cluster
startup timeout, assigning SIs to SUs"
so we can see the other SUs were being assigned
3080 2018-08-16T02:52:10.129+0200 SC-2 safApp=safAmfService NO:
"safSi=ABC.main-NWA-1,safApp=QWE-ABC-Amfproxy assigned to
safSu=SC-2,safSg=NWA,safApp=QWE-ABC-Amfproxy HA State 'ACTIVE'"
3311 2018-08-16T02:53:55.745+0200 SC-2 safApp=safAmfService NO:
"safSu=PL-4,safSg=NWA,safApp=QWE-ABC-Amfproxy PresenceState INSTANTIATING =>
INSTANTIATED"
3312 2018-08-16T02:53:55.745+0200 SC-2 safApp=safAmfService NO:
"safSu=PL-4,safSg=NWA,safApp=QWE-ABC-Amfproxy ReadinessState OUT_OF_SERVICE =>
IN_SERVICE"
3313 2018-08-16T02:53:55.750+0200 SC-2 safApp=safAmfService NO:
"safSi=ABC.main-NWA-1,safApp=QWE-ABC-Amfproxy assigned to
safSu=PL-4,safSg=NWA,safApp=QWE-ABC-Amfproxy HA State 'ACTIVE'"
3360 2018-08-16T02:54:06.555+0200 SC-2 safApp=safAmfService NO:
"safSu=PL-3,safSg=NWA,safApp=QWE-ABC-Amfproxy PresenceState INSTANTIATING =>
INSTANTIATED"
3361 2018-08-16T02:54:06.555+0200 SC-2 safApp=safAmfService NO:
"safSu=PL-3,safSg=NWA,safApp=QWE-ABC-Amfproxy ReadinessState OUT_OF_SERVICE =>
IN_SERVICE"
3362 2018-08-16T02:54:06.560+0200 SC-2 safApp=safAmfService NO:
"safSi=ABC.main-NWA-1,safApp=QWE-ABC-Amfproxy assigned to
safSu=PL-3,safSg=NWA,safApp=QWE-ABC-Amfproxy HA State 'ACTIVE'"
The only SU in SC-1 is not assigned, because it is still OUT_OF_SERVICE
The unlock command does not get the SU IN_SERVICE, because node SC-1 is still
DISABLED.
---
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.------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
