Joel , you get a cookie for getting this right !!!
yup , all I had to do is a "ls" and I am ok
thanks to all!!!
On Wed, Jun 6, 2018 at 5:07 PM, Graham Dumpleton
wrote:
> Also ensure you have the correct oc command line client version
> corresponding to the oc cluster. When they are divergent
Also ensure you have the correct oc command line client version corresponding
to the oc cluster. When they are divergent you can get subtle problems.
Graham
> On 7 Jun 2018, at 7:05 am, Brian Keyes wrote:
>
> if I ssh into one of the worker nodes and "oc login" I can start the debug
>
if I ssh into one of the worker nodes and "oc login" I can start the debug
container and get a command prompt , so it may be some kind of proxy or
something here at my work site
On Wed, Jun 6, 2018 at 4:52 PM, Brian Keyes wrote:
> no I dont think so , but I am running the CLI on my local
What operating system is your local machine? Ok windows I’ve noticed the oc
binary doesn’t doesn’t do terminal emulation properly. So it looks like
it’s hanging but it’s actually working. Try typing “ls” and see if the
command has actually worked, but you’re just not setting the command
prompt.
On
no I dont think so , but I am running the CLI on my local machine , I will
ssh into one of the nodes and try
thanks
On Wed, Jun 6, 2018 at 4:49 PM, Aleksandar Lazic
wrote:
> On 06/06/2018 13:04, Brian Keyes wrote:
>
>> If I do a "debug in terminal" in the console I always get a command
On 06/06/2018 13:04, Brian Keyes wrote:
If I do a "debug in terminal" in the console I always get a command prompt
if i goto the command line and do a "oc debug i get this message
Debugging with pod/lster-1-2rqg9-debug, original command:
container-entrypoint /tmp/scripts/run
Waiting for pod
If I do a "debug in terminal" in the console I always get a command prompt
if i goto the command line and do a "oc debug i get this message
Debugging with pod/lster-1-2rqg9-debug, original command:
container-entrypoint /tmp/scripts/run
Waiting for pod to start ...
Pod IP: 10.252.4.18
If you
