images produces from Dockerfile have an old version of oc

[elmiko]

while experimenting with creating my own must-gather image i tried to make a build from the Dockerfile located in the root of the project. although it built properly, when running it i see an error in that the --dest-dir option is not available. upon further inspection it appears that the oc binary included in the registry.svc.ci.openshift.org/openshift/origin-v4.0:cli image does no support the inspect command, thus the gather scripts will fail.

a snippet of error output:

[must-gather      ] OUT namespace/openshift-must-gather-gc2vz created                                                                                                                          
[must-gather      ] OUT clusterrolebinding.rbac.authorization.k8s.io/must-gather-4hkdz created                                                                                                 
[must-gather      ] OUT pod for plug-in image quay.io/fnord/must-gather created                                                                                                         
[must-gather-2qqfs] POD 2021-05-04T00:32:02.896350743Z Error: unknown flag: --dest-dir  

how to reproduce

1. create a must gather image using the default dockerfile, eg podman build -t quay.io/fnord/must-gather
2. upload image
3. run a must gather against a cluster using oc must-gather --image quay.io/fnord/must-gather

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions 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/test-infra repository.