Upstream, we've been trying to get the bug OSPRH-15801 fixed in ironic where Nova can hand Ironic bad metadata. Ultimately these sorts of issues are important to have a fix for in general because our customer base heavily relies upon spine/leaf network configurations, and these are cases where it becomes even easier to fall into situations where bad metadata is generated.

Ultimately, upstream reviewers have asked for more to be followed up on:

• Some syntax nitpicking on the upstream change, see: https://review.opendev.org/c/openstack/ironic/+/946677
• Some additional logging, see: https://review.opendev.org/c/openstack/ironic/+/946677
• An outstanding request to attempt to shorten the value used for the "id" value.
  • This relates to bug https://bugs.launchpad.net/ironic/+bug/2112655 upstream as well.
  • This is rooted in use of vlans on tenant workloads which the schema supports. We don't really see it used widely
• Vlan support needs to be added overall, since it seems, at least based on the schema and the data, its a valid case we could get sent. It is likely just a missing case we're not really aware of, but to add it was sort of beyond the original bugs sizing.

Ultimately, the classes of issues do sort of mean we're unlikely to pre-emptively/pro-actively try and backport fixes in to the product, but to have fixes for them will at least save us a substantial amount of time should a customer encounter these sorts of issues down the road.