[jbosstools-issues] [JBoss JIRA] (JBIDE-23822) Server adapter: is not working with oc v1.4.x

[ https://issues.jboss.org/browse/JBIDE-23822?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23822 at 2/7/17 3:47 PM: ------------------------------------------------------------------ [~hardy.ferentschik] for me there's no X.4.X oc binary (neither 1.4.x nor 3.4.x) that works doing rsync with cdk/minishift Alpha2. At the same time login works, which I cant explain. We are using oc specifying user and token in the very same cmd. We do this so that we dont meddle with login states. To get the token you can simply do {code}oc whoami -t{code} Here are the steps (using ocp 3.4.x) to reproduce it in all details - you'd get the very same with all oc/ocp >= 1.4/3.4 while it works using those in version <=1.3.x/4.3.x: {code} adietish@Andres-MBP $ /Users/adietish/Downloads/oc\ binaries/ocp-3.4.0.39/oc login Authentication required for https://192.168.99.100:8443 (openshift) Username: developer Password: Login successful. You have one project on this server: "gargoyle" Using project "gargoyle". adietish@Andres-MBP $ /Users/adietish/Downloads/oc\ binaries/ocp-3.3.17/oc whoami -t lYmVXxFjLrZu5jf7WpGNAOx9KAAjp3_46AT70JOf1JQ adietish@Andres-MBP $ Users/adietish/Downloads/oc\ binaries/ocp-3.4.0.39/oc rsync --user=developer --token=lYmVXxFjLrZu5jf7WpGNAOx9KAAjp3_46AT70JOf1JQ --server=https://192.168.99.100:8443 --insecure-skip-tls-verify=true --exclude='.git' nodejs-mongodb-example-1-i31y4:/opt/app-root/src/ -n gargoyle/Users/adietish/Documents/jboss-workspaces/jbosstools-github/runtime-openshift2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/gigu@mongodb/deploy/ error: auth info "developer" does not exist {code} was (Author: adietish): [~hardy.ferentschik] for me there's no X.4.X oc binary (neither 1.4.x nor 3.4.x) that works doing rsync with cdk/minishift Alpha2. At the same time login works, which I cant explain. We are using oc specifying user and token in the very same cmd. We do this so that we dont meddle with login states. To get the token you can simply do {code}oc whoami -t{code} Here are the steps (using ocp 3.4.x) to reproduce it in all details - you'd get the very same with all oc/ocp >= 1.4/3.4 while it works using those in version <=1.3.x/4.3.x: {code} adietish@Andres-MBP $ /Users/adietish/Downloads/oc\ binaries/ocp-3.4.0.39/oc login Authentication required for https://192.168.99.100:8443 (openshift) Username: developer Password: Login successful. You have one project on this server: "gargoyle" Using project "gargoyle". adietish@Andres-MBP $ /Users/adietish/Downloads/oc\ binaries/ocp-3.3.17/oc whoami -t lYmVXxFjLrZu5jf7WpGNAOx9KAAjp3_46AT70JOf1JQ adietish@Andres-MBP $ /Users/adietish/Downloads/oc\ binaries/ocp-3.4.0.39/oc rsync --user=system --token=lYmVXxFjLrZu5jf7WpGNAOx9KAAjp3_46AT70JOf1JQ --server=https://192.168.99.100:8443 --insecure-skip-tls-verify=true --exclude='.git' nodejs-mongodb-example-1-i31y4:/opt/app-root/src/ -n gigu /Users/adietish/Documents/jboss-workspaces/jbosstools-github/runtime-openshift2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/gigu@mongodb/deploy/ error: auth info "system" does not exist {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)