The resource spec contents of spec PP and RB fields are always different.

[CharlesQQ]

What happened:
When create pp and workload, pp sets the .spec.suspension.dispatching=true, and then .spec.suspension.dispatching=false , rb is always .spec.suspension.dispatching=true.

As shown in the code below, when the update event starts to be processed, if the creation event has not been completed, that is, rb has not been created, then resourceBindings will not be found, and the result is that the update content of pp will not be synchronized to rb.

karmada/pkg/detector/detector.go

Lines 1169 to 1191 in cf5def1

	func (d *ResourceDetector) HandlePropagationPolicyCreationOrUpdate(policy *policyv1alpha1.PropagationPolicy) error {
	// If the Policy's ResourceSelectors change, causing certain resources to no longer match the Policy, the label claimed
	// on relevant resource template will be removed (which gives the resource template a change to match another policy).
	policyID := policy.Labels[policyv1alpha1.PropagationPolicyPermanentIDLabel]
	err := d.cleanPPUnmatchedRBs(policyID, policy.Namespace, policy.Name, policy.Spec.ResourceSelectors)
	if err != nil {
	return err
	}
	// When updating fields other than ResourceSelector, should first find the corresponding ResourceBinding
	// and add the bound object to the processor's queue for reconciliation to make sure that
	// PropagationPolicy's updates can be synchronized to ResourceBinding.
	resourceBindings, err := d.listPPDerivedRBs(policyID, policy.Namespace, policy.Name)
	if err != nil {
	return err
	}
	for _, rb := range resourceBindings.Items {
	resourceKey, err := helper.ConstructClusterWideKey(rb.Spec.Resource)
	if err != nil {
	return err
	}
	d.Processor.Add(keys.ClusterWideKeyWithConfig{ClusterWideKey: resourceKey, ResourceChangeByKarmada: true})
	}

What you expected to happen:
The relevant fields in the spec of the PP and RB fields must ultimately be the same.

How to reproduce it (as minimally and precisely as possible):

create pp and resource template, set pp field .spec.suspension.dispatching=true, and then set .spec.suspension.dispatching=false, check check rb field .spec.suspension.dispatching.

Anything else we need to know?:

Environment:

• Karmada version:
  v1.12
• kubectl-karmada or karmadactl version (the result of kubectl-karmada version or karmadactl version):
• Others: