This is tracking the upstream effort needed to deliver the solution to the bug described below.

 Problem Description: Clearly explain the issue.

Users can configure "requested tunnel keys" for logical router ports.  ovn-northd tries to honor those when creating Southbound port bindings.  However, if users request a tunnel key for a DGP (distributed gateway port), ovn-northd tries to use the same tunnel key for both the port binding corresponding to the NB logical router port and also for the port binding corresponding to the implicit chassis redirect port (cr-<LRP>).

 Impact Assessment: Describe the severity and impact (e.g., network down,availability of a workaround, etc.).

May affect network traffic based on the order in which ovn-northd processes the LRP/cr-LRP port bindings.

 Software Versions: Specify the exact versions in use (e.g.,openvswitch3.1-3.1.0-147.el8fdp).

Any supported OVN (at least >= ovn24.03-24.03.7-8.el9fdp).

  Issue Type: Indicate whether this is a new issue or a regression (if a regression, state the last known working version).

Day-1 bug.

 Reproducibility: Confirm if the issue can be reproduced consistently. If not, describe how often it occurs.

Consistently reproducible.

 Reproduction Steps: Provide detailed steps or scripts to replicate the issue.

In an OVN sandbox create a router with a DGP and a requested tunnel key for it:

ovn-nbctl lr-add lr -- lrp-add lr lrp 00:00:00:00:00:01 10.0.0.1/24 \
    -- set logical_router_port lrp options:requested-tnl-key=42
    -- lrp-set-gateway-chassis lrp chassis-0 10

 Expected Behavior: Describe what should happen under normal circumstances.

ovn-northd should assign tunnel key 42 to the port binding corresponding to "lrp". And allocate a different ID to the port binding corresponding to "cr-lrp". It should also not complain about the non-existent requested-tnl-key duplicated config.
 

 Observed Behavior: Explain what actually happens.

In the ovn-northd logs:

northd|WARN|Logical router port lrp requests same tunnel key 42 as another LSP or LRP

 Troubleshooting Actions: Outline the steps taken to diagnose or resolve the issue so far.

 Logs: If you collected logs please provide them (e.g. sos report, /var/log/openvswitch/* , testpmd console)