Redundant Managing Node test fails - Zynq EmacPS, Windows(NDIS, Link-to-application)

[powerlink-team-kalycito]

Bug Description: Stack version : v2.7.0-rc1 SHA : c733b294ba07a7813120fe6e4aeac2b46a82d18f Test case : Redundant Managing Node Test Managing Node : Xilinx-z702(Emacps), NDIS, Link-to-Application(Windows) Controlled Node: Linux Edrv

Bug Summary: Link-to-application - RMN acting as AMN, when unplug and plugged back AMN stays in PreOp2 state. (Expected Behavior - AMN should reach CsOperational state) Zynq EmacPS, NDIS - When running with RMN configuration enabled, the AMN reaches operational state but does not detect CNs.

Steps to Reproduce: (Zynq EmacPS, NDIS)

• Build the stack and driver with RMN configuration enabled.
• Change node ID of the MN in the application and build the same with the RMN configuration enabled.
• Run the application with RMN cdc.

(Link-to-application)

• Build the stack and driver with RMN configuration enabled.
• Change node ID of the MN in the application and build the same with the RMN configuration enabled.
• Run the application with RMN cdc.
• Unplug and plug back the AMN.

[powerlink-team-kalycito]

• Pull request (#370) for Zynq Emacps is provided.
• For Windows NDIS, it is concluded as not a bug because for any node to act as RMN it must run both as MN and CN, but Windows NDIS design does not have implementation for CN.
• For Link to application, the bug is not seen if the node is terminated by Ctrl+c instead unplugging from the network.

This bug can be closed, if the pull request #370 is merged.

[powerlink-team-kalycito]

Pull request #374 resolves this issue. Hence this bug can be closed.

[powerlink-team-kalycito]

Pull request for this issue (#374) is integrated in the stack. This bug shall be closed now.