Fix in https://github.com/openshift/origin/pull/22498

Verified with latest oc , this not fixed:
Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.0", GitCommit:"eee567b9d", GitTreeState:"", BuildDate:"2019-04-14T17:00:04Z", GoVersion:"", Compiler:"", Platform:""}

C:\Users\oppenshift\Downloads> oc plugin list
The following compatible plugins are available:

C:\Program Files\Microsoft Windows Performance Toolkit\oc-far-foo.exe
C:\Users\oppenshift\AppData\Local\Microsoft\WindowsApps\oc-xxia.cmd
C:\Users\oppenshift\AppData\Local\Microsoft\WindowsApps\oc-xxiatest.bat
C:\Users\oppenshift\AppData\Local\Microsoft\WindowsApps\oc-xxiaxshell.exe

error: unable to read directory "" in your PATH: open : The system cannot find the file specified.

C:\Users\oppenshift\Downloads>oc xxia
not supported by windows

*** Bug 1699705 has been marked as a duplicate of this bug. ***

> error: unable to read directory "" in your PATH: open : The system cannot find the file specified.

This looks like an error in the configuration. Not a plugin problem per se.


> C:\Users\oppenshift\Downloads>oc xxia
> not supported by windows

Similarly, the fact that windows cannot execute a specific binary is not a problem for oc.
Plugin mechanism is working as expected.

Based on the above I'm moving this back to QA.

When I use the `path` command :

C:\Users\oppenshift>path
PATH=C:\Program Files (x86)\NetSarang\Xshell 6\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft Windows Performance Toolkit\;C:\WINDOWS\System32\OpenSSH\;C:\Users\oppenshift\AppData\Local\Microsoft\WindowsApps;


Seems no configuration error ?

It looks like the error reading directory is different on windows, I've fixed it in https://github.com/openshift/origin/pull/22590
I'm moving this back to POST and will move to qa once the PR merges.

Confirmed with latest oc client, no error info:
C:\Users\oppenshift>oc version
Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.0", GitCommit:"74c534b60", GitTreeState:"", BuildDate:"2019-04-21T21:13:18Z", GoVersion:"", Compiler:"", Platform:""}
Unable to connect to the server: dial tcp: lookup api.qe-xxia-0417-2.qe.devcluster.openshift.com: no such host

C:\Users\oppenshift>oc plugin list
The following compatible plugins are available:

C:\Program Files\Microsoft Windows Performance Toolkit\oc-far-foo.exe
C:\Users\oppenshift\AppData\Local\Microsoft\WindowsApps\oc-xxia.cmd
C:\Users\oppenshift\AppData\Local\Microsoft\WindowsApps\oc-xxiatest.bat
C:\Users\oppenshift\AppData\Local\Microsoft\WindowsApps\oc-xxiaxshell.exe
Unable read directory "" from your PATH: open : The system cannot find the file specified.. Skipping...

Hi Maciej:

    I've two questions about this issue:
    1) when I set PATH without the space , also see the info, I want to know why ? 

  C:\Users\oppenshift>path
PATH=C:\WINDOWS\System32\OpenSSH\;C:\Users\oppenshift\AppData\Local\Microsoft\WindowsApps;

C:\Users\oppenshift>oc plugin list
The following compatible plugins are available:

C:\Users\oppenshift\AppData\Local\Microsoft\WindowsApps\oc-xxia.cmd
C:\Users\oppenshift\AppData\Local\Microsoft\WindowsApps\oc-xxiatest.bat
C:\Users\oppenshift\AppData\Local\Microsoft\WindowsApps\oc-xxiaxshell.exe
Unable read directory "" from your PATH: open : The system cannot find the file specified.. Skipping...


    2)I want to double confirm for windows cannot execute a specific binary:   "not supported by windows", is this by design ?

Yes the error is expected, in https://github.com/openshift/origin/pull/22590 we've decided to always show 
the information about problems but continue processing. This replaced previous error string matching 
solution which was working only on linux.

> 2)I want to double confirm for windows cannot execute a specific binary:   "not supported by windows", is this by design ?

Yes, that's an operating system limitation, we can't address that. I'm guessing this is version specific, and we don't want 
to go that granular with allowed extensions.

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