8000 BatchV1API_createNamespacedJob does not return the failing reason. · Issue #189 · kubernetes-client/c · GitHub
[go: up one dir, main page]

Skip to content
BatchV1API_createNamespacedJob does not return the failing reason. #189
@shayan-eftekhari

Description

@shayan-eftekhari

Hi,

I'm using the BatchV1API_createNamespacedJob API to create a Job.

If for any reason the process fails (e.g. if a job with the same name already exists), the API still returns a v1_job_t* with a kind equal to "Status" instead of "Job" but there is no way to understand the reason.

I digged into its implementation and I found this:

cJSON *BatchV1APIlocalVarJSON = cJSON_Parse(apiClient->dataReceived);

The BatchV1APIlocalVarJSON local variable holds the actual reason, so I'm wondering if there is a way to report it back.

This might be also true on other APIs but I have not examined them yet.

Would you please let me know if there is a way to access the failure reason through the API, or if there is not, do you have a plan to make it possible? I'm wondering if it is possible to extend v1_job_status_t struct to hold such information.

Thank you in advance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0