Note. I am filling exception in order to get hot fix approved for a patch in 16.2 networking-ovn branch. Current plan is to include this fix in upcoming 16.2.8 release (GA May 7)

*Have you evaluated this as a potential release Blocker?
Yes, not that urgent. We just want hot fix until 16.2.8 is relesed

*What is the business rationale for this exception? Is there a specific customer that needs this RFE?
Part of RHOS-PRIO 505. Customer ADP

*Are there any security concerns?
No

*Business Impact
From RHOS-PRIO 505

This is affecting most of the instances the customer is creating

*Probability of occurrence?
Customer states that some instances have this issue but it is painful

*Severity of consequences. What % of our Top 50 customers have hit this issue, or will hit the issue
What other functions, teams, or DFGs are impacted by this feature?
What is the estimated time to have the upstream work complete and approved?

The issue is in OVN(and resolved in later OVN releases). The patch in neutron metadata agent is a workaround since there are no plans to bump OVN on 16.2 release(very old). This workaround patch went into downstream only since there is no upstram branch.
patch was already merged into 16.2-trunk-patches

*Is there potential doc impact? If yes, has your doc team point of contact agreed that docs have the capacity to complete the required work?
No

• Are there new packages needed that are not packaged in OSP or RHEL? Does it require newer versions of existing dependencies (dependency bumps)?
  No

• What is the support level? Tech Preview or fully supported
  Fully supported

• How invasive is the code? From very invasive, a core change to very isolated, no risk to other components?
  Not very invasive, we just added more logic into the existing code to compensate for slowness in OVN.

• What is the impact to deployment/updates/upgrades/FFU; what are the test plans in these areas?
  None