Menu

#2582 amfnd: handle TIMEOUT in amf_saImmOmAccessorGet_o2

5.18.02
fixed
Gary Lee
None
defect
amf
nd
major
False
2018-02-02
2017-09-13
Gary Lee
No

Sometimes IMM returns TIMEOUT to AMFND when calling immutil_saImmOmAccessorGet_o2().

Aug 20 07:08:46 PL-4 osafamfnd[7326]: ER amf_saImmOmAccessorGet_o2 FAILED for 'safComp=ABC,safSu=PL-4,safSg=NoRed-ABC,safApp=ABC'
Aug 20 07:08:46 PL-4 osafamfnd[7326]: NO Component CLC fsm exited with error for comp:safComp=ABC,safSu=PL-4,safSg=NoRed-ABC,safApp=ABC

Related

Wiki: ChangeLog-5.18.02

Discussion

  • Anders Widell

    Anders Widell - 2017-11-03
    • Milestone: 5.17.11 --> 5.18.01
     
  • Gary Lee

    Gary Lee - 2017-12-18
    • status: accepted --> review
     
  • Gary Lee

    Gary Lee - 2018-01-09

    commit 51e30cbf5f891f2479013bf9ce4289a27c47aa17
    Author: Gary Lee gary.lee@dektech.com.au
    Date: Tue Jan 9 14:52:18 2018 +1100

    amfnd: do not retrieve runtime attributes [#2582]
    
    amf_saImmOmAccessorGet_o2() would sometimes return TIMEOUT if
    AMFD is updating a runtime object and IMM PBE is slow, leaving
    a component in UN-INSTANTIATED state.
    
    To fix this, we should only retrieve configuration attributes thus
    IMM will not have to read from AMFD at all. This also reduces
    load on AMFD.
    
     
  • Gary Lee

    Gary Lee - 2018-01-09
    • status: review --> fixed
     

Log in to post a comment.