Description of problem: oc convert didn't create all files under directory after they have been converted Version-Release number of selected component (if applicable): oc v3.4.0.23+24b1a58 kubernetes v1.4.0+776c994 How reproducible: Always Steps to Reproduce: 1.Prepare 2 test files cat >> job-v1.yaml << EOF apiVersion: batch/v1 kind: Job metadata: name: pi spec: template: metadata: name: pi spec: containers: - name: pi image: perl command: ["perl", "-Mbignum=bpi", "-wle", "print bpi(2000)"] restartPolicy: Never EOF cat >> job-v2.json << EOF { "kind": "ScheduledJob", "apiVersion": "batch/v2alpha1", "metadata": { "name": "hello", "creationTimestamp": null }, "spec": { "schedule": "0/1 * * * ?", "concurrencyPolicy": "Allow", "suspend": false, "jobTemplate": { "metadata": { "creationTimestamp": null }, "spec": { "template": { "metadata": { "creationTimestamp": null }, "spec": { "containers": [ { "name": "hello", "image": "busybox", "args": [ "/bin/sh", "-c", "date; echo Hello from the Kubernetes cluster" ], "resources": {}, "terminationMessagePath": "/dev/termination-log", "imagePullPolicy": "Always" } ], "restartPolicy": "OnFailure", "terminationGracePeriodSeconds": 30, "dnsPolicy": "ClusterFirst", "securityContext": {} } } } } }, "status": {} } EOF 2.mkdir /tmp/test; cp job-v1.yaml job-v2.json /tmp/test;cd /tmp/test 3.oc convert -f . 4.oc convert -f . | oc create -f - Actual results: 3.All files are converted 4.Only one resource is created $ oc convert -f . | oc create -f - running in local mode... scheduledjob "hello" created Expected results: 4. Both job "pi" and scheduledjob "hello" should be created successfully Additional info:
Fixed in https://github.com/openshift/origin/pull/11874.
Checked with oc v3.4.0.27+dffa95c/kubernetes v1.4.0+776c994 with steps in "Steps to Reproduce", issue has been fixed I could verify when it's moved ON_QA
Move to VERIFIED since already checked in oc v3.4.0.27
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, 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-2017:0066