Before I install Rancher v2.7.3 I have:

release=fleet ns=cattle-fleet-system chart=fleet-102.0.0+up0.6.0

release=fleet-agent-local ns=cattle-fleet-system chart=fleet-agent-local-v0.0.0+s-a308b0cf342cdf1dd6d8e7dde0226eba0bdb8c0cc97d0b2f4c36c86fd11e9

release=fleet-crd ns=cattle-fleet-system chart=fleet-crd-102.0.0+up0.6.0

And then after I install Rancher v2.7.3, this chart has been added by Rancher:

release=fleet-agent-local ns=cattle-fleet-local-system chart=fleet-agent-local-v0.0.0+s-4e4bca490df31d6a3cdca28ee3989d47b6c4ebfb4f9c97ad0b1299a2194e4

The bundles are showing errors like:

ErrApplied(1) [Cluster fleet-local/local: another operation (install/upgrade/rollback) is in progress]

Modified(1) [Cluster fleet-local/local]; priorityclass.scheduling.k8s.io cluster-low missing; priorityclass.scheduling.k8s.io cluster-medium missing; priorityclass.scheduling.k8s.io deployment-machinery missing; priorityclass.scheduling.k8s.io develop missing

It's as if the two agents are fighting over the bundles. The different hash code on the Rancher-supplied fleet-agent leads me to believe it is a different version perhaps.