Bug 1834643
Summary: | `oc create cronjob` help show incorrect example | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | zhou ying <yinzhou> |
Component: | oc | Assignee: | Maciej Szulik <maszulik> |
Status: | CLOSED ERRATA | QA Contact: | RamaKasturi <knarra> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 4.5 | CC: | aos-bugs, jokerman, knarra, mfojtik |
Target Milestone: | --- | ||
Target Release: | 4.6.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-10-27 15:58:59 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
zhou ying
2020-05-12 06:39:07 UTC
I've opened https://github.com/kubernetes/kubernetes/pull/91013 and we'll get the fix in the next release. Upstream PRs merged. This is waiting for k8s bump. Waiting for next k8s bump. K8s was bumped in https://github.com/openshift/oc/pull/491 Verified with the version below and i do see right examples in "oc create cronjob -h" [ramakasturinarra@dhcp35-60 ~]$ oc version -o yaml clientVersion: buildDate: "2020-08-21T02:37:08Z" compiler: gc gitCommit: ea0d54068621ec0f95973068729f739f3dacfef7 gitTreeState: clean gitVersion: 4.6.0-202008210209.p0-ea0d540 goVersion: go1.14.4 major: "" minor: "" platform: linux/amd64 openshiftVersion: 4.6.0-0.nightly-2020-08-23-214712 serverVersion: buildDate: "2020-08-20T16:46:57Z" compiler: gc gitCommit: 3e083ac29409923906267ebcc5f8e0aa13072c72 gitTreeState: dirty gitVersion: v1.19.0-rc.2+3e083ac-dirty goVersion: go1.14.4 major: "1" minor: 19+ platform: linux/amd64 [ramakasturinarra@dhcp35-60 ~]$ oc create cronjob -h Create a cronjob with the specified name. Aliases: cronjob, cj Usage: oc create cronjob NAME --image=image --schedule='0/5 * * * ?' -- [COMMAND] [args...] [flags] Examples: # Create a cronjob oc create cronjob my-job --image=busybox --schedule="*/1 * * * *" # Create a cronjob with command oc create cronjob my-job --image=busybox --schedule="*/1 * * * *" -- date Options: --allow-missing-template-keys=true: If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. --dry-run='none': Must be "none", "server", or "client". If client strategy, only print the object that would be sent, without sending it. If server strategy, submit server-side request without persisting the resource. --field-manager='kubectl-create': Name of the manager used to track field ownership. --image='': Image name to run. -o, --output='': Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file. --restart='': job's restart policy. supported values: OnFailure, Never --save-config=false: If true, the configuration of current object will be saved in its annotation. Otherwise, the annotation will be unchanged. This flag is useful when you want to perform kubectl apply on this object in the future. --schedule='': A schedule in the Cron format the job should be run with. --template='': Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview]. --validate=false: If true, use a schema to validate the input before sending it Use "oc options" for a list of global command-line options (applies to all commands). Also running the above examples work fine. [ramakasturinarra@dhcp35-60 ~]$ oc create cronjob my-job --image=busybox --schedule="*/1 * * * *" cronjob.batch/my-job created [ramakasturinarra@dhcp35-60 ~]$ oc create cronjob my-job1 --image=busybox --schedule="*/1 * * * *" -- date cronjob.batch/my-job1 created [ramakasturinarra@dhcp35-60 ~]$ oc get cronjob NAME SCHEDULE SUSPEND ACTIVE LAST SCHEDULE AGE my-job */1 * * * * False 0 <none> 20s my-job1 */1 * * * * False 0 <none> 6s Based on the above moving it to verified state. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196 |