The ccb was aborted at init procerdure. But currently there is no restry for this.
From syslog
2019-07-17T06:02:14.975+02:00 node2-vc111 osafsmfd[9118]: NO PROC: Start upgrade procedure safSmfProc=proc1
2019-07-17T06:02:14.990+02:00 node2-vc111 osafsmfd[9118]: NO PROC: Start procedure init actions
...
2019-07-17T06:02:21.548+02:00 node2-vc111 osafimmnd[8947]: WA Aborting ccbId 210 to start sync
...
2019-07-17T06:02:23.311+02:00 node2-vc111 osafsmfd[9118]: NO AdminOwnerSet: SetAdminOwner() Fail, SAAISERRNOTEXIST (12)
2019-07-17T06:02:23.311+02:00 node2-vc111 osafsmfd[9118]: NO AddCreates: AdminOwnerSet() Fail
2019-07-17T06:02:23.311+02:00 node2-vc111 osafsmfd[9118]: NO DoModelModification: AddCreates() Fail
2019-07-17T06:02:23.312+02:00 node2-vc111 osafsmfd[9118]: NO doImmOperations: DoModelModification() Fail, SAAISERRNOTEXIST (12) in 'saImmOmAdminOwnerSet'
2019-07-17T06:02:23.320+02:00 node2-vc111 osafsmfd[9118]: NO Init action 3 failed, rc=SAAISERRNOTEXIST (12)
2019-07-17T06:02:23.322+02:00 node2-vc111 osafsmfd[9118]: NO CAMP: Procedure safSmfProc=proc1 returned FAILED
Diff:
Diff:
commit 2d85d5d9264c6a7d1c6601b900fb810facbee3ac (HEAD -> develop, origin/develop)
Author: thang.d.nguyen thang.d.nguyen@dektech.com.au
Date: Mon Aug 12 15:16:47 2019 +0700