- **Comment**:
An adjustment is being made to IMM enhancement #1261.
This fix should hopefully remove this problem, that is get back to
the apparent behavior of PBE enable in OpenSAF 4.6 and earlier.
Note however that there is never a 100% guarantee that an attempted
CCB will succeed, even if it is correctly formed, i.e. contents is valid.
A CCB may get aborted due to resource reasons at any time. It should be
rare on normal systems that are not overloaded. But it will happen now
and then.
SMF could contemplate an approach of trying to redo CCBs that fail
at least once. This would make sense when/if the failure of a CCB would
otherwise derail the entire campaign, requiring rollback or even restore.
Replaying a CCB is in principle simple.
It consists of invoking saImmOmCcbAbort on ccb handle followed by
a jump back to where the CCB is being built. This is similar to a loop
for handling ERR_TRY_AGAIN, except here the logic is redoing an entire
ccb and not just a single operation or down-call.
---
** [tickets:#1398] smf: ccb fails after pbe enable**
**Status:** unassigned
**Milestone:** 4.5.2
**Created:** Wed Jul 01, 2015 02:07 PM UTC by Rafael
**Last Updated:** Thu Jul 02, 2015 07:09 AM UTC
**Owner:** nobody
During the final stages of an upgrade campaign PBE is enabled. PBE is not ready
until it attaches, so CCB commits will fail in that window. A possible solution
is to read IMMs noStdFlag and check that it is not <Empty> which would mean
that PBE is attached and ready.
IMM ticked related to this: #1261
Jun 29 10:36:35 SC-2-2 osafimmpbed: IN Admop for aborting CCBs result: 1, immsv
returned 1
Jun 29 10:36:35 SC-2-2 osafimmpbed: NO Update epoch 63 committing with
ccbId:100000185/4294967685
Jun 29 10:36:36 SC-2-2 osafsmfd[4726]: NO CAMP: Start campaign complete actions
(95)
Jun 29 10:36:36 SC-2-2 osafimmnd[4476]: NO Create of PERSISTENT runtime object
'smfRollbackElement=CampComplete,safSmfCampaign=ERIC-CMWUpgrade,safApp=safSmfService'
(safSmfCampaign).
Jun 29 10:36:36 SC-2-2 osafimmnd[4476]: NO Ccb 305 COMMITTED
(immcfg_SC-2-1_14718)
Jun 29 10:36:36 SC-2-2 osafimmnd[4476]: NO Ccb 306 COMMITTED
(immcfg_SC-2-1_14741)
Jun 29 10:36:36 SC-2-2 osafimmnd[4476]: NO Ccb 307 COMMITTED
(immcfg_SC-2-1_14764)
Jun 29 10:36:36 SC-2-2 osafimmnd[4476]: NO Ccb 308 COMMITTED
(immcfg_SC-2-1_14787)
Jun 29 10:36:37 SC-2-2 osafimmnd[4476]: NO Ccb 309 COMMITTED
(immcfg_SC-2-1_14810)
Jun 29 10:36:37 SC-2-2 osafimmnd[4476]: NO Ccb 310 COMMITTED
(immcfg_SC-2-1_14833)
Jun 29 10:36:37 SC-2-2 osafimmnd[4476]: NO Ccb 311 COMMITTED
(immcfg_SC-2-1_14856)
Jun 29 10:36:37 SC-2-2 osafimmnd[4476]: NO Ccb 312 COMMITTED
(immcfg_SC-2-1_14879)
Jun 29 10:36:37 SC-2-2 osafimmnd[4476]: NO Create of PERSISTENT runtime object
'smfRollbackElement=ccb_00000002,smfRollbackElement=CampComplete,safSmfCampaign=ERIC-CMWUpgrade,safApp=safSmfService'
(safSmfCampaign).
Jun 29 10:36:37 SC-2-2 osafimmnd[4476]: NO PBE-OI established on this SC.
Dumping incrementally to file imm.db
Jun 29 10:36:37 SC-2-2 osafimmnd[4476]: NO CCB 313 aborted by: immadm -o 202
safRdn=immManagement,safApp=safImmService
Jun 29 10:36:37 SC-2-2 osafimmnd[4476]: WA Timeout while waiting for
implementer, aborting ccb:313
Jun 29 10:36:37 SC-2-2 osafimmnd[4476]: NO Ccb 313 ABORTED (SMFSERVICE)
Jun 29 10:36:37 SC-2-2 osafimmnd[4476]: WA >>s_info->to_svc == 0<< reply
context destroyed before this reply could be made
Jun 29 10:36:37 SC-2-2 osafimmnd[4476]: WA Failed to send response to
agent/client over MDS
Jun 29 10:36:37 SC-2-2 osafimmnd[4476]: NO Ccb <313> not in correct state (12)
for Apply ignoring request
Jun 29 10:36:37 SC-2-2 osafimmnd[4476]: WA Spurious and redundant ccb-apply
request ignored ccbId:313
Jun 29 10:37:37 SC-2-2 osafsmfd[4726]: NO saImmOmCcbApply failed
rc=SA_AIS_ERR_FAILED_OPERATION (21)
Jun 29 10:37:37 SC-2-2 osafimmnd[4476]: WA ERR_BAD_HANDLE: Handle use is
blocked by pending reply on syncronous call
Jun 29 10:37:37 SC-2-2 osafimmnd[4476]: WA IMMND - Client Node Get Failed for
cli_hdl 158634617209359
Jun 29 10:37:37 SC-2-2 osafsmfd[4726]: ER SmfCampaignWrapup campCompleteAction
2 failed, rc=SA_AIS_ERR_FAILED_OPERATION (21)
Jun 29 10:37:37 SC-2-2 osafsmfd[4726]: ER Campaign wrapup executing campaign
complete actions failed
---
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.
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
