fix: log correct error from Prepare Data Plugins#2512
Conversation
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi @varad-ahirwadkar. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
|
||
| // Prepare per request data by running PrepareData plugins. | ||
| if d.runPrepareDataPlugins(ctx, reqCtx.SchedulingRequest, snapshotOfCandidatePods) != nil { | ||
| prepErr := d.runPrepareDataPlugins(ctx, reqCtx.SchedulingRequest, snapshotOfCandidatePods) |
There was a problem hiding this comment.
can you reuse err instead of introducing a new var?
|
/ok-to-test |
Signed-off-by: Varad <varad.ahirwadkar1@ibm.com>
7649b89 to
d0fc625
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nirrozenbaum, varad-ahirwadkar The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Varad <varad.ahirwadkar1@ibm.com>
Signed-off-by: Varad <varad.ahirwadkar1@ibm.com>
…api-inference-extension#2512) Signed-off-by: Varad <varad.ahirwadkar1@ibm.com>
What type of PR is this?
/kind bug
What this PR does / why we need it:
HandleRequest()ignored the error returned byrunPrepareDataPluginsand logged a staleerrvariable, causing misleading logs.Capture and log the actual returned error to improve observability.
Which issue(s) this PR fixes:
Fixes #2508
Does this PR introduce a user-facing change?:
NONE