[jbosstools-issues] [JBoss JIRA] (JBIDE-26699) Server adapter: should error if port forwarding fails

[André Dietisheim (Jira)]

     [ https://issues.jboss.org/browse/JBIDE-26699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

André Dietisheim updated JBIDE-26699:
-------------------------------------
    Description: 
steps:
# ASSERT: have a crc cluster installed where you didnt approve the certificates: https://github.com/code-ready/crc/issues/218#issuecomment-501099558
# ASSERT: have an app (with a pod) running
# EXEC: create a server adapter for it and start it
# ASSERT: syncing fails
{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}
{code}
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}
# EXEC: check if the port forwarding for the pod (of your app) is "Started"

*Result*:
The port forwarding for your pod is "Stopped". If you try to start it it'll fail with the error
{code}
OpenShiftBinaryCapability process exited: error: error upgrading connection: error dialing backend: remote error: tls: internal error
{code}

*Expected result*:
Starting the server adapter should fail and notify that the port forwarding failed. Currently only the next step where syncing is attempted fails.

  was:
steps:
# ASSERT: have a crc cluster installed where you didnt approve the certificates: https://github.com/code-ready/crc/issues/218#issuecomment-501099558
# ASSERT: have an app (with a pod) running
# EXEC: create a server adapter for it and start it
# ASSERT: syncing fails
{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}
{code}
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}
# EXEC: check if the port forwarding for the pod (of your app) is "Started"

Result:
The port forwarding for your pod is "Stopped". If you try to start it it'll fail with the error
{code}
OpenShiftBinaryCapability process exited: error: error upgrading connection: error dialing backend: remote error: tls: internal error
{code}

Expected result:
Starting the server adapter should fail and notify that the port forwarding failed. Currently only the next step where syncing is attempted fails.



> Server adapter: should error if port forwarding fails
> -----------------------------------------------------
>
>                 Key: JBIDE-26699
>                 URL: https://issues.jboss.org/browse/JBIDE-26699
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.12.0.AM1
>            Reporter: André Dietisheim
>            Priority: Major
>              Labels: port_forwarding, server_adapter
>
> steps:
> # ASSERT: have a crc cluster installed where you didnt approve the certificates: https://github.com/code-ready/crc/issues/218#issuecomment-501099558
> # ASSERT: have an app (with a pod) running
> # EXEC: create a server adapter for it and start it
> # ASSERT: syncing fails
> {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}
> {code}
> 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}
> # EXEC: check if the port forwarding for the pod (of your app) is "Started"
> *Result*:
> The port forwarding for your pod is "Stopped". If you try to start it it'll fail with the error
> {code}
> OpenShiftBinaryCapability process exited: error: error upgrading connection: error dialing backend: remote error: tls: internal error
> {code}
> *Expected result*:
> Starting the server adapter should fail and notify that the port forwarding failed. Currently only the next step where syncing is attempted fails.



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