Menu

#687 CSI CSI dependency failed in multiple sponsor for single dependent case.

4.4.2
fixed
Praveen
None
defect
amf
d
4.4
major
2015-03-16
2013-12-20
manu
No

Changeset : 4733

CSI5 is dependent on CSI1,CSI2,CSI3 and CSI4 in the configuration.

when we perform the UNLOCk-IN UNLOCK operation on SU.
All csi are assigned accept CSI4. As per the configuration CSI5 is dependent on CSI4 . But CSI5 also got assigned with out assignment of CSI4.

safCSIComp=safComp=AmfDemo5\,safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo,safCsi=AmfDemo_CSI2,safSi=AmfDemo,safApp=AmfDemo
saAmfCSICompHAState=ACTIVE(1)
saAmfCSICompHAReadinessState=READY_FOR_ASSIGNMENT(1)
safCSIComp=safComp=AmfDemo3\,safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo,safCsi=AmfDemo_CSI1,safSi=AmfDemo,safApp=AmfDemo
saAmfCSICompHAState=ACTIVE(1)
saAmfCSICompHAReadinessState=READY_FOR_ASSIGNMENT(1)
safCSIComp=safComp=AmfDemo1\,safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo,safCsi=AmfDemo_CSI5,safSi=AmfDemo,safApp=AmfDemo
saAmfCSICompHAState=ACTIVE(1)
saAmfCSICompHAReadinessState=READY_FOR_ASSIGNMENT(1)
safCSIComp=safComp=AmfDemo2\,safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo,safCsi=AmfDemo_CSI3,safSi=AmfDemo,safApp=AmfDemo
saAmfCSICompHAState=ACTIVE(1)
saAmfCSICompHAReadinessState=READY_FOR_ASSIGNMENT(1)

4 Attachments

Related

Tickets: #687

Discussion

  • Praveen

    Praveen - 2013-12-26

    This problem is reproducible on 4.3 GA release changeset also:
    4.3.GA 4241:b4b4dedbc6ac
    Attached 687.tgz contains traces and configuration after reproducing on 4.3 GA changeset with simple AMF demo based configuration.

     
  • Anders Widell

    Anders Widell - 2014-01-09
    • Milestone: 4.4.FC --> 4.4.RC1
     
  • Nagendra Kumar

    Nagendra Kumar - 2014-01-15

    Note:
    This is an invalid configuration. compcstype is not configured, but corresponding csi is sponsor of some other csis. If sponsor csi is not supposed to be assigned(because of missing compcstype configuration), csi-csi dep shouldn't be configured for those csis, at least csi shouldn't be made as sponsor.

     
  • Nagendra Kumar

    Nagendra Kumar - 2014-02-03
    • Version: 4.4 --> 4.2.5
     
  • Nagendra Kumar

    Nagendra Kumar - 2014-02-03
    • Version: 4.2.5 --> 4.4
    • Milestone: 4.4.RC1 --> 4.2.5
     
  • Praveen

    Praveen - 2014-02-17
    • Milestone: 4.2.5 --> 4.3.3
     
  • Anders Widell

    Anders Widell - 2014-10-07
    • Milestone: 4.3.3 --> 4.4.2
     
  • Praveen

    Praveen - 2015-01-13
    • status: unassigned --> accepted
    • assigned_to: Praveen
     
  • Praveen

    Praveen - 2015-01-29

    Simple configuration (687.xml) to reproduce the problem.
    Steps:
    1) immcfg -f 687.xml
    2) amf-adm unlock-in safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
    3) amf-adm unlock safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1

     
  • Praveen

    Praveen - 2015-01-29
    • status: accepted --> review
    • Part: - --> d
     
  • Praveen

    Praveen - 2015-03-13

    changeset: 6346:3d2bc823d687
    parent: 6344:97ccb50cd7d7
    user: praveen.malviya@oracle.com
    date: Fri Mar 13 09:44:48 2015 +0530
    summary: amfd: do not assign dependent csi if any sponsor csi is unassigned [#687]

    changeset: 6345:85ccd1a19dac
    branch: opensaf-4.5.x
    parent: 6343:4bd0893394bf
    user: praveen.malviya@oracle.com
    date: Fri Mar 13 09:44:08 2015 +0530
    summary: amfd: do not assign dependent csi if any sponsor csi is unassigned [#687]

    For 4.4. I will push it later after rebasing it.

     

    Related

    Tickets: #687

  • Praveen

    Praveen - 2015-03-16
    • status: review --> fixed
     
  • Praveen

    Praveen - 2015-03-16

    changeset: 6358:f46cf39fcaed
    branch: opensaf-4.4.x
    tag: tip
    user: praveen.malviya@oracle.com
    date: Mon Mar 16 11:35:13 2015 +0530
    summary: amfd: do not assign dependent csi if any sponsor csi is unassigned [#687]

     

    Related

    Tickets: #687


Log in to post a comment.