Skip to content

requeue logic for pending NAD#445

Open
posikoya wants to merge 1 commit into
openstack-k8s-operators:mainfrom
posikoya:posikoya/refator-reconcile-err
Open

requeue logic for pending NAD#445
posikoya wants to merge 1 commit into
openstack-k8s-operators:mainfrom
posikoya:posikoya/refator-reconcile-err

Conversation

@posikoya
Copy link
Copy Markdown

@posikoya posikoya commented May 6, 2026

The operator currently returns a misleading reconcile error when Pod interfaces are not yet ready with assigned IPs. This change introduces a requeue mechanism to allow time for NetworkAttachmentDefinitions (NAD) to be fully provisioned.

The operator currently returns a misleading reconcile error when Pod interfaces are not yet ready with assigned IPs.
This change introduces a requeue mechanism to allow time for NetworkAttachmentDefinitions (NAD) to be fully provisioned.
@openshift-ci openshift-ci Bot requested review from kstrenkova and stuggi May 6, 2026 12:58
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 6, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: posikoya
Once this PR has been reviewed and has the lgtm label, please assign kstrenkova for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 6, 2026

Hi @posikoya. Thanks for your PR.

I'm waiting for a openstack-k8s-operators member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@centosinfra-prod-github-app
Copy link
Copy Markdown

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/rdoproject.org/buildset/d991970e3dd54427957f8a896ea9c0bf

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 44m 52s
podified-multinode-edpm-deployment-crc-test-operator FAILURE in 2h 27m 18s

@posikoya posikoya marked this pull request as ready for review May 11, 2026 08:53
@openshift-ci openshift-ci Bot requested a review from dprince May 11, 2026 08:53
@kstrenkova
Copy link
Copy Markdown
Contributor

/ok-to-test

err.Error()))

return ctrl.Result{}, err
return ctrl.Result{RequeueAfter: time.Second * 10}, nil
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do think it is a good idea to re-queue, but I am concerned what will happen if the NAD is actually faulty. It seems it will re-queue forever without printing any error in the logs. How would you prevent this?

}

return ctrl.Result{}, nil
return ctrl.Result{}, err
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Returning an error here might mean that when the if networkReady conditions is true, the whole function will return an error, which is not something we want :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants