controller-0 is added to the generated baremetal-info.yml, and should instead be excluded. I can't think of a reason why controller-0 should be managed as a BareMetalHost for metal3. Is there one?

Also, if you do create a BMH for controller-0, the default state is powered off. So once you create the BMH for it, it gets powered off, which then breaks power control for the other BMH's since controller-0 is running the sushy pods. This is difficult to debug and understand why that happens.