Skip to content

The backoffLimit of the CronJob is left out when using the "Start Job" menu item #15575

@asoltesz

Description

@asoltesz

The Openshift Console has a very useful function for the CronJob called "Start Job" appearing in the context menu.
This creates a Job instance from the CronJob by using its jobTemplate.

We are using this to start ad-hoc Jobs from CronJobs that are either suspended or scheduled to run very infrequently by default (and we need a Job execution before the next scheduled one).

Unfortunately, the Openshift UI function creates an imperfect Job since it leaves out the "backoffLimit" attribute which is an important part of the jobTemplate (it may leave out other fields as well).

When I wait and get a Job execution from the CronJob by its normal schedule, the "backoffLimit" is correctly copied into the Job and it behaves accordingly. When I create the Job via the "Create Job" context menu item, the "backoffLimit" is not copied onto the Job and the default "6" value appears on it.

This is a problem for all of those jobs where the execution should not be re-attempted which - I assume - most cases since the batch execution problems usually do not resolve themselves.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions