[jbosstools-issues] [JBoss JIRA] (JBIDE-26691) OpenShift Tooling: Cannot create server adapter for app running on CRC

[André Dietisheim (Jira)]

    [ https://issues.jboss.org/browse/JBIDE-26691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751587#comment-13751587 ] 

André Dietisheim edited comment on JBIDE-26691 at 6/25/19 11:22 AM:
--------------------------------------------------------------------

[~jkopriva], [~jeffmaury] the following usually happens if syncing is tried too early, when no rsync nor tar is available yet:
{code}
OpenShiftBinaryCapability process exited: WARNING: cannot use rsync: rsync not available in container
WARNING: cannot use tar: tar not available in container
error: No available strategies to copy.
{code}
* Is the error also happening if you re-try after waiting a bit?
* If the error is persistent, then this would mean that the image is lacking rsync and tar. Is it? If you log into it, are there rsync or tar binaries present?
* if rsync is present in the container, then we could face a problem with the port forwarding. Is the port-forwarding for the pod "Started"?


was (Author: adietish):
[~jkopriva], [~jeffmaury] the following usually happens if syncing is tried too early, when no rsync nor tar is available yet:
{code}
OpenShiftBinaryCapability process exited: WARNING: cannot use rsync: rsync not available in container
WARNING: cannot use tar: tar not available in container
error: No available strategies to copy.
{code}
Is the error also happening if you re-try after waiting a bit?
On the other hand, if the error is persistent, then this would mean that the image is lacking rsync and tar. Is it? If you log into it, are there rsync or tar binaries present?

> OpenShift Tooling: Cannot create server adapter for app running on CRC
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-26691
>                 URL: https://issues.jboss.org/browse/JBIDE-26691
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.12.0.Final
>         Environment: MacOS 10.14.5 (18F203) CSB, JDK11, CRC 0.87.0-alpha-4.1.0+3a5033a
>            Reporter: Josef Kopriva
>            Assignee: André Dietisheim
>            Priority: Critical
>             Fix For: 4.12.0.Final
>
>
> {code:java}
> eclipse.buildId=12.12.0.GA-v20190623-2343-B4589
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB
> Framework arguments:  -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> org.jboss.tools.openshift.core
> Error
> Tue Jun 25 07:30:16 CEST 2019
> Could not sync folder /Users/jkopriva/workspace_4589/.metadata/.plugins/org.jboss.ide.eclipse.as.core/123 at eap-app/deploy to all pods.
> {code}
> {code:java}
> eclipse.buildId=12.12.0.GA-v20190623-2343-B4589
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB
> Framework arguments:  -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> org.jboss.tools.openshift.core
> Error
> Tue Jun 25 07:30:16 CEST 2019
> OpenShiftBinaryCapability process exited: WARNING: cannot use rsync: rsync not available in container
> WARNING: cannot use tar: tar not available in container
> error: No available strategies to copy.
> {code}



--
This message was sent by Atlassian Jira
(v7.12.1#712002)