Menu

#1802 amf upgrade fails

never
invalid
None
defect
amf
nd
5.0 GA
major
2016-09-20
2016-05-02
No

When running an SMF upgrade of AMF the following happens:

SC-2-1 osafsmfd[4296]: NO STEP: Online installation of new software
(this step is succesful)
SC-2-1 osafsmfd[4296]: NO STEP: Lock deactivation units
SC-2-1 osafamfd[4120]: NO Node is locked, no SI unassigned alarm will be sent
SC-2-1 osafsmfd[4296]: NO STEP: Terminate deactivation units
SC-2-1 osafamfd[4120]: WA avd_msg_sanity_chk: invalid msg id 219, msg type 8, from 2020f should be 218
... (this repeats a number of times)

osafsmfd[4296]: NO Fail to invoke admin operation, rc=SA_AIS_ERR_TIMEOUT (5). dn=[safAmfNode=SC-2,safAmfCluster=myAmfCluster], opId=[3]
osafsmfd[4296]: NO Failed to call admin operation 3 on safAmfNode=SC-2,safAmfCluster=myAmfCluster

Is AMF handling a upgrade properly? Seems that the msg id is missmatched here.

Related

Tickets: #1802

Discussion

  • Gary Lee

    Gary Lee - 2016-05-03

    Sounds like we have a problem of snd_msg_id being updated & messages sent (potentially out of order) from multiple threads.

     

    Last edit: Gary Lee 2016-05-03
  • Gary Lee

    Gary Lee - 2016-05-03

    Rafael says the problem goes away if #517 changes are reverted

     
    • Praveen

      Praveen - 2016-05-03

      What is the upgrade path being followed?
      Also please share the traces from AMFD and AMFND and details about no.
      of nodes.

      Thanks,
      Praveen

      On 03-May-16 11:00 AM, Gary Lee wrote:

      Rafael says the problem goes away if #517 changes are reverted


      [tickets:#1802] https://sourceforge.net/p/opensaf/tickets/1802/ amf
      upgrade fails

      Status: unassigned
      Milestone: 5.0.GA
      Created: Mon May 02, 2016 05:44 PM UTC by Rafael
      Last Updated: Tue May 03, 2016 05:29 AM UTC
      Owner: nobody

      When running an SMF upgrade of AMF the following happens:

      SC-2-1 osafsmfd[4296]: NO STEP: Online installation of new software
      (this step is succesful)
      SC-2-1 osafsmfd[4296]: NO STEP: Lock deactivation units
      SC-2-1 osafamfd[4120]: NO Node is locked, no SI unassigned alarm will be
      sent
      SC-2-1 osafsmfd[4296]: NO STEP: Terminate deactivation units
      SC-2-1 osafamfd[4120]: WA avd_msg_sanity_chk: invalid msg id 219, msg
      type 8, from 2020f should be 218
      ... (this repeats a number of times)

      osafsmfd[4296]: NO Fail to invoke admin operation, rc=SA_AIS_ERR_TIMEOUT
      (5). dn=[safAmfNode=SC-2,safAmfCluster=myAmfCluster], opId=[3]
      osafsmfd[4296]: NO Failed to call admin operation 3 on
      safAmfNode=SC-2,safAmfCluster=myAmfCluster

      Is AMF handling a upgrade properly? Seems that the msg id is missmatched
      here.


      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.


      Find and fix application performance issues faster with Applications Manager
      Applications Manager provides deep performance insights into multiple tiers of
      your business applications. It resolves application problems quickly and
      reduces your MTTR. Get your free trial!
      https://ad.doubleclick.net/ddm/clk/302982198;130105516;z


      Opensaf-tickets mailing list
      Opensaf-tickets@lists.sourceforge.net
      https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

       

      Related

      Tickets: #1802

  • Praveen

    Praveen - 2016-05-03
    • status: unassigned --> needinfo
     
  • Praveen

    Praveen - 2016-05-03

    Hi,

    What is the upgrade path being followed along with specific changeset and tag?
    Also please share the syslog, traces from AMFD and AMFND and details about no.
    of nodes. Also steps to reproduce.

    Thanks,
    Praveen

     
  • Nagendra Kumar

    Nagendra Kumar - 2016-05-03
    • status: needinfo --> accepted
    • assigned_to: Nagendra Kumar
     
  • Rafael Odzakow

    Rafael Odzakow - 2016-05-03

    Maybe someone else can help you with the trace and logs. I am not able to reproduce it on my system. It seems this also shows in a failover case of the active SC without doing any SMF upgrade.

     
  • Nagendra Kumar

    Nagendra Kumar - 2016-05-03

    Please find the attached patch 1802.patch and test and share the results.

    Thanks
    -Nagu

     
  • Nagendra Kumar

    Nagendra Kumar - 2016-05-03
    • status: accepted --> review
     
  • Nagendra Kumar

    Nagendra Kumar - 2016-05-03

    Updated the patch, please find it(1802_mod.patch) attached.

     
  • Nagendra Kumar

    Nagendra Kumar - 2016-05-03

    Please perform your testing with 1802_mod.patch and share the results.

     
  • Nagendra Kumar

    Nagendra Kumar - 2016-05-03

    @Rafael: Can you please get 1802_mod.patch tested, so that we can push it before 5.0 GA?

    Thanks
    -Nagu

     
  • Mathi Naickan

    Mathi Naickan - 2016-05-04
    • status: review --> needinfo
    • Milestone: 5.0.GA --> 5.0.1
     
  • Mathi Naickan

    Mathi Naickan - 2016-05-04

    This ticket needs to be updated with additional information of how to reproduce, traces etc.
    Please update with the relevant information.

     
  • Nagendra Kumar

    Nagendra Kumar - 2016-06-07
    • status: needinfo --> invalid
    • Part: - --> nd
    • Version: --> 5.0 GA
     
  • Nagendra Kumar

    Nagendra Kumar - 2016-06-07

    The latest patch floated avoids this issue.

     
  • Anders Widell

    Anders Widell - 2016-09-20
    • Milestone: 5.0.1 --> never
     

Log in to post a comment.