The resources "xMachineTemplate-cp" are not pivoted because ownerReference is not set

When a management cluster is installed, the metal3MachineTemplate-cp resource is recreated via the re-instantiation of the cluster helmRelease. This is not the case for the metal3MachineTemplate-md resource, which was pivoted.
By inspecting the two resources on the bootstrap-cluster, we can see that metal3MachineTemplate-cp has no ownerReference (required to pivot resources). \

ownerReferences:
    - apiVersion: cluster.x-k8s.io/v1beta1
      kind: Cluster
      name: mgmt-1528686993-rke2-capm3-virt
      uid: 06605586-d66c-44f5-92df-9caf51134e3b

This behavior seems related to the RKE2 bootstrap provider. Since it works properly with KubeAdm.

I don't know what are the impacts for now, apart from the fact that the resource is not pivoted.

We can legitimately create an issue on the upstream side (https://github.com/rancher/cluster-api-provider-rke2)

(The behavior seems to be the same whatever the infraprovider (tested with capm3 and capo).)