Watch HFC/HFS spec changes to trigger BMH reconciliation

When a user clears firmware specs to abort a failed servicing operation,
the BMH controller may be in exponential backoff due to the servicing
error. Without a watch, the BMH won't notice the spec change until the
next backoff-delayed reconciliation, which can take a long time.

Add watches on HostFirmwareSettings and HostFirmwareComponents with
GenerationChangedPredicate, mapping events back to the BMH with the
same name/namespace. This ensures the BMH controller reconciles
promptly when specs are modified, enabling the fast-path abort to
trigger without delay.

Assisted-By: Claude Opus 4.6

Author: jacob-anders

internal/controller/metal3.io/baremetalhost_controller.go

@@ -46,6 +46,7 @@ import (
 	"sigs.k8s.io/controller-runtime/pkg/controller"
 	"sigs.k8s.io/controller-runtime/pkg/controller/controllerutil"
 	"sigs.k8s.io/controller-runtime/pkg/event"
+	"sigs.k8s.io/controller-runtime/pkg/handler"
 	"sigs.k8s.io/controller-runtime/pkg/predicate"
 )
 
@@ -2510,6 +2511,22 @@ func (r *BareMetalHostReconciler) SetupWithManager(mgr ctrl.Manager, preprovImgE
 		controller.Owns(&metal3api.PreprovisioningImage{})
 	}
 
+	// Watch HFC/HFS for spec changes (generation bumps) so that the BMH
+	// controller reconciles promptly when a user clears firmware specs,
+	// rather than waiting for error-state exponential backoff to expire.
+	firmwareEventHandler := handler.EnqueueRequestsFromMapFunc(
+		func(_ context.Context, obj client.Object) []ctrl.Request {
+			return []ctrl.Request{{NamespacedName: client.ObjectKey{
+				Name:      obj.GetName(),
+				Namespace: obj.GetNamespace(),
+			}}}
+		},
+	)
+	controller.Watches(&metal3api.HostFirmwareSettings{}, firmwareEventHandler,
+		builder.WithPredicates(predicate.GenerationChangedPredicate{}))
+	controller.Watches(&metal3api.HostFirmwareComponents{}, firmwareEventHandler,
+		builder.WithPredicates(predicate.GenerationChangedPredicate{}))
+
 	return controller.Complete(r)
 }