I think this is because we have some internal types in some helpers. We need to clear cruft to get consistent behavior.
PR fixing the problem: https://github.com/openshift/origin/pull/22494
Could you tell what's the odd behaviors of oc "in some paths"? I checked PR code, it involves build/bc/dc of /apps/apis/apps. But not sure what's the oddity, thus no idea how to verify the bug. Thanks!
Tested with versions: oc version Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.0", GitCommit:"ac50235ff", GitTreeState:"", BuildDate:"2019-04-11T04:55:38Z", GoVersion:"", Compiler:"", Platform:""} Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+f174899", GitCommit:"f174899", GitTreeState:"clean", BuildDate:"2019-04-10T17:18:27Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"} Per discussion with Maciej, checked below commands with BC/DC: oc new-app centos/ruby-25-centos7~https://github.com/sclorg/ruby-ex.git oc status oc status --suggest oc logs bc/ruby-ex oc logs dc/ruby-ex oc rollout latest dc/ruby-ex oc logs dc/ruby-ex oc logs -f dc/ruby-ex oc attach dc/ruby-ex oc autoscale dc/ruby-ex --max=4; oc get hpa oc expose dc/ruby-ex --name=ruby-ex-svc oc rollout history dc/ruby-ex oc rollback dc/ruby-ex All work well. Thus moving to VERIFIED.
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-2019:0758