Skip to content

Commit

Permalink
Requeue in NnfAccess after NnfNodeBlockStorage conflict (#425)
Browse files Browse the repository at this point in the history
The NnfNodeBlockStorage resource is not owned by the NnfAccess, so the NnfAccess won't
be requeued after the client cache updates.

Signed-off-by: Matt Richerson <[email protected]>
  • Loading branch information
matthew-richerson authored Dec 5, 2024
1 parent 595b723 commit 123b12e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion internal/controller/nnf_access_controller.go
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,7 @@ func (r *NnfAccessReconciler) mount(ctx context.Context, access *nnfv1alpha4.Nnf
err = r.addBlockStorageAccess(ctx, access, storageMapping)
if err != nil {
if apierrors.IsConflict(err) {
return &ctrl.Result{}, nil
return &ctrl.Result{RequeueAfter: time.Second * 2}, nil
}

return nil, dwsv1alpha2.NewResourceError("unable to add endpoints to NnfNodeStorage").WithError(err)
Expand Down

0 comments on commit 123b12e

Please sign in to comment.