Menu

#464 Verify duplicate TIPC node_id before configuring TIPC

4.7.FC
fixed
None
enhancement
base
-
major
2015-09-18
2013-06-18
No

Currently, there is no direct way to detect if there is already another node running with the same TIPC node_id.
If we could query say the TIPC routing table before doing stuff that within nid_tipc, then we could fail the opensaf startup when duplicate slot_id is configured.

This can fix known issues like http://devel.opensaf.org/ticket/2802

Related

Wiki: NEWS-4.7.0

Discussion

  • Mathi Naickan

    Mathi Naickan - 2013-06-18
     
  • Mathi Naickan

    Mathi Naickan - 2014-05-19

    This ticket can also see if there are any cleanups required in nid_tipc script.

     
  • Mathi Naickan

    Mathi Naickan - 2014-05-19
    • Type: defect --> enhancement
    • Component: osaf --> mds
    • Milestone: future --> 4.5.FC
     
  • Mathi Naickan

    Mathi Naickan - 2014-07-21
    • Milestone: 4.5.FC --> 4.6.FC
     
  • A V Mahesh (AVM)

    • Milestone: 4.6.FC --> future
     
  • A V Mahesh (AVM)

    • status: unassigned --> review
    • assigned_to: A V Mahesh (AVM)
    • Component: mds --> base
    • Milestone: future --> 4.7.FC
     
  • A V Mahesh (AVM)

    • status: review --> fixed
     
  • A V Mahesh (AVM)

    changeset: 6844:ff30714b16bb
    tag: tip
    user: A V Mahesh mahesh.valla@oracle.com
    date: Fri Sep 18 11:00:14 2015 +0530
    summary: opensaf: prevented cluster re-start on misconfigured slot_id [#464/#414]

     

Log in to post a comment.