Menu

#874 SG unstable while doing Si-Swap.

never
not-reproducible
Praveen
None
defect
amf
-
4.3.2
major
2014-05-13
2014-04-24
manu
No

changeset : 5024 (4.3.2)
model : 2n
configuration : 1App,1SG,2SUs with 4comps each, 4SIs with 1 CSI each
si-si deps configured as SI1 sponsor for SI2,3,4
SU1 is active, SU2 is standby.
SU1 is mapped to pl-3 and SU2 to pl-4
saAmfSGAutoRepair=1(True)
SuFailover=1(True)

Test:
1. perform SI swap
2. sponsor SI timesout the new standby assignment
3. Again perform SI swap. This fails

Snippet:-

pr 24 18:22:03 SLES_NEW1 osafimmnd[18992]: NO Implementer connected: 19 (MsgQueueService131855) <0, 2030f>
Apr 24 18:22:40 SLES_NEW1 osafamfd[19047]: ER safSi=SI1,safApp=test2nApp SWAP failed - SG not stable (1)
Apr 24 18:22:41 SLES_NEW1 osafamfd[19047]: ER safSi=SI1,safApp=test2nApp SWAP failed - SG not stable (1)
Apr 24 18:22:42 SLES_NEW1 osafamfd[19047]: ER safSi=SI1,safApp=test2nApp SWAP failed - SG not stable (1)
Apr 24 18:22:43 SLES_NEW1 osafamfd[19047]: ER safSi=SI1,safApp=test2nApp SWAP failed - SG not stable (1)
Apr 24 18:22:44 SLES_NEW1 osafamfd[19047]: ER safSi=SI1,safApp=test2nApp SWAP failed - SG not stable (1)
Apr

1 Attachments

Discussion

  • Praveen

    Praveen - 2014-05-05

    Please share AMF traces if possible.

     
  • Praveen

    Praveen - 2014-05-06

    This issue is not reproducible.Please find the attached traces.It works fine.

     
  • Praveen

    Praveen - 2014-05-13
    • status: unassigned --> accepted
    • assigned_to: Praveen
    • Version: --> 4.3.2
     
  • Praveen

    Praveen - 2014-05-13

    With the steps given, this issue is not reproducible in 4.3 branch also.
    Attach is log and configuration and traces after successful verification.
    Please reopen the ticket if issue is observed again.

     
  • Praveen

    Praveen - 2014-05-13
    • status: accepted --> not-reproducible
    • Milestone: future --> never
     

Log in to post a comment.