Current Behavior

nodeA:

PeerID: 12D3KooWCrBnK6RP6bAws2voZzUjhJhwNksvfSDprhjkjm7pv57r
version: 2.2.0-rc.1+commit.7c8fb964
config from the node logs:

"protocol": {
      "outgoing_ticket_winning_prob": 1,
      "heartbeat": {
        "timeout": 15
      },
      "ticket_aggregation": {
        "timeout": 15
      }
    },

nodeB:

PeerID: 12D3KooWNTT31hFWSfUEmXgRa22hPcGXWdbyZmPTNBoMZ4GYMbNK
version: 2.1.5
config from the node logs: It doesn't show what is a winning prob.

Win tickets probability on both nodes: 1
Network: rotsee
Also tested with Singapore-latest tag (2.2.0-rc.1+commit.58bf759e), same issue.

Sending a 1-hop message to myself using the path nodeA -> nodeB -> nodeA:

• NodeB does not receive any ticket.
• NodeA successfully receives the message.

Using the alternate path nodeB -> nodeA -> nodeB:

• NodeA does not receive any ticket.
• NodeB successfully receives the message.

Expected Behavior

Sending a 1-hop message to myself using the path nodeA -> nodeB -> nodeA:

• NodeB should receive ticket.
• NodeA successfully receives the message.

Using the alternate path nodeB -> nodeA -> nodeB:

• NodeA should receive ticket.
• NodeB successfully receives the message.

Steps to Reproduce

1. Run one node 2.2 and another node 2.1.5
2. Try to send 1-hop message via 2.1.5

Were you able to reproduce the bug using the above steps consistently each time? YES

Logs

NodeA: https://drive.google.com/file/d/1EFUO2mNkkpSLo88fvQPovXIioC922KcF/view?usp=sharing
NodeA_config: https://drive.google.com/file/d/1vV6vvfZxPDLrCz0NGnssg5Eq3ehRPUCJ/view?usp=sharing
NodeB: https://drive.google.com/file/d/1Q2JuZ28hQQAapQVpws_x_B6xfa04PZh8/view?usp=sharing
NodeB_config: https://drive.google.com/file/d/1fcnl3zgJMBFxRYOdEh4eE7yhjVpo8rMT/view?usp=sharing