- **status**: review --> fixed
- **Comment**:

commit e71ccceccae17aa9876ab9108b62a4fc36c99140 (HEAD -> develop, 
origin/develop, ticket-3354)
Author: thang.d.nguyen <[email protected]>
Date:   Mon Jun 24 21:36:17 2024 +0700

    smf: fix one step upgrade failed [#3354]

    In large cluster or system under high load, during one step
    upgrade, SMF orders AMF to lock node group(NG). There are
    many request to IMM to update attribute and it causes the
    timeout respond from IMM to AMF. SMF receives timeout then
    retry lock again and again while the first lock still on
    going. When the first lock is successful and the request
    lock again from SMF will receive NO_OP error from AMF.

    In this case, NO_OP should be considered as a success.




---

**[tickets:#3354] smf: upgrades failed in one step during lock node group**

**Status:** fixed
**Milestone:** 5.24.09
**Created:** Tue Jun 25, 2024 12:56 AM UTC by Thang Duc Nguyen
**Last Updated:** Thu Jun 27, 2024 11:27 AM UTC
**Owner:** Thang Duc Nguyen


This ticket is to enhance to old one #3262. In #3262, it covers the TIMEOUT 
error from IMM. In this ticket it covers the NO_OP error from AMFD as 
implementer.
Errors in syslog
~~~

2024-06-23T16:29:00.966+02:00 SC-1 osafamfd[741]: NO 
'safAmfNodeGroup=smfLockAdmNg1,safAmfCluster=myAmfCluster' is already 
undergoing admin operation
2024-06-23T16:29:02.676+02:00 SC-1 osafamfd[741]: WA ERR_INVALID_PARAM: Illegal 
SaInvocationT value provided in saImmOiAdminOperationResult
2024-06-23T16:29:02.676+02:00 SC-1 osafamfd[741]: ER 
saImmOiAdminOperationResult failed with 7 for admin op invocation: 
52591874539524, result 1
...
2024-06-23T16:29:04.570+02:00 SC-1 osafsmfd[1873]: NO nodeGroupAdminOperation: 
SaAmfAdminOperationId 2 Fail SA_AIS_ERR_NO_OP (28)
2024-06-23T16:29:04.572+02:00 SC-1 osafsmfd[1873]: NO adminOperationNodeGroup: 
setNodeGroupAdminState() Fail SA_AIS_ERR_NO_OP (28)
2024-06-23T16:29:04.599+02:00 SC-1 osafsmfd[1873]: NO changeAdminState: 
changeNodeGroupAdminState() Fail SA_AIS_ERR_NO_OP (28)
2024-06-23T16:29:04.599+02:00 SC-1 osafsmfd[1873]: NO lock setAdminState() Fail
2024-06-23T16:29:04.600+02:00 SC-1 osafsmfd[1873]: ER Failed to Lock 
deactivation units in step=safSmfStep=0001
2024-06-23T16:29:04.600+02:00 SC-1 osafsmfd[1873]: ER Step execution failed, 
Try undoing the step
2024-06-23T16:29:04.606+02:00 SC-1 osafsmfd[1873]: NO 
SmfStepStateUndoing::execute start undoing step.
2024-06-23T16:29:04.607+02:00 SC-1 osafsmfd[1873]: ER Rollback of cluster 
reboot activate step is not implemented
2024-06-23T16:29:04.607+02:00 SC-1 osafsmfd[1873]: ER Step undoing failed
~~~


---

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

Reply via email to