[JBoss JIRA] (JBIDE-21698) Can't deploy Docker image to OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21698?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-21698 at 2/22/16 11:13 AM:
-----------------------------------------------------------------
I am stucked in the middle of the process. When I start building a docker image, in console everything looks ok, there is no error. All steps passed. But immediately after that there is an error dialog with following stack
{code}
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:653)
at java.util.ArrayList.get(ArrayList.java:429)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:810)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:750)
at org.eclipse.linuxtools.internal.docker.ui.jobs.BuildDockerImageJob.processMessage(BuildDockerImageJob.java:165)
at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:40)
at com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:840)
at com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:789)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.buildImage(DockerConnection.java:987)
at org.eclipse.linuxtools.internal.docker.ui.jobs.BuildDockerImageJob.run(BuildDockerImageJob.java:129)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
any hint?
was (Author: mlabuda):
I am stucked in the middle of the process. When I start building a docker image, in console everything looks ok, there is no error. All steps passed. But immediately after that there is an error dialog with following stack
{code}
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:653)
at java.util.ArrayList.get(ArrayList.java:429)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:810)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:750)
at org.eclipse.linuxtools.internal.docker.ui.jobs.BuildDockerImageJob.processMessage(BuildDockerImageJob.java:165)
at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:40)
at com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:840)
at com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:789)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.buildImage(DockerConnection.java:987)
at org.eclipse.linuxtools.internal.docker.ui.jobs.BuildDockerImageJob.run(BuildDockerImageJob.java:129)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code]
any hint?
> Can't deploy Docker image to OpenShift
> --------------------------------------
>
> Key: JBIDE-21698
> URL: https://issues.jboss.org/browse/JBIDE-21698
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Clone https://github.com/redhat-developer-tooling/openshift-vagrant/ (outside eclipse)
> Create / Run CDK Server adapter pointing at openshift-vagrant/cdk-v2/
> Clone https://github.com/burrsutter/cdk_helloworlds
> import swarm-helloworld as a maven project in the workspace
> Run maven build mvn clean compile package on the project.
> Right-click on swarm-helloworld/dockerfile > Run As > Docker Image Build
> Select Docker connection from CDK
> Use 172.30.80.211:5000/burr/swarm-helloworld as repo name
> The image deploys to the CDK docker connection/registry (See Docker Explorer)
> Right click on the deployed image > Deploy to OpenShift
> Select OpenShift Project (create a new one if necessary)
> =>Error Message : This docker image was not pulled in the selected Docker connection. Mapping ports will not be possible.
> The Finish Button stays disabled
> http://screencast.com/t/I2syMLXNcO8
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21698) Can't deploy Docker image to OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21698?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21698:
---------------------------------------
I am stucked in the middle of the process. When I start building a docker image, in console everything looks ok, there is no error. All steps passed. But immediately after that there is an error dialog with following stack
{code}
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:653)
at java.util.ArrayList.get(ArrayList.java:429)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:810)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:750)
at org.eclipse.linuxtools.internal.docker.ui.jobs.BuildDockerImageJob.processMessage(BuildDockerImageJob.java:165)
at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:40)
at com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:840)
at com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:789)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.buildImage(DockerConnection.java:987)
at org.eclipse.linuxtools.internal.docker.ui.jobs.BuildDockerImageJob.run(BuildDockerImageJob.java:129)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code]
any hint?
> Can't deploy Docker image to OpenShift
> --------------------------------------
>
> Key: JBIDE-21698
> URL: https://issues.jboss.org/browse/JBIDE-21698
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Clone https://github.com/redhat-developer-tooling/openshift-vagrant/ (outside eclipse)
> Create / Run CDK Server adapter pointing at openshift-vagrant/cdk-v2/
> Clone https://github.com/burrsutter/cdk_helloworlds
> import swarm-helloworld as a maven project in the workspace
> Run maven build mvn clean compile package on the project.
> Right-click on swarm-helloworld/dockerfile > Run As > Docker Image Build
> Select Docker connection from CDK
> Use 172.30.80.211:5000/burr/swarm-helloworld as repo name
> The image deploys to the CDK docker connection/registry (See Docker Explorer)
> Right click on the deployed image > Deploy to OpenShift
> Select OpenShift Project (create a new one if necessary)
> =>Error Message : This docker image was not pulled in the selected Docker connection. Mapping ports will not be possible.
> The Finish Button stays disabled
> http://screencast.com/t/I2syMLXNcO8
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21698) Can't deploy Docker image to OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21698?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21698:
----------------------------------
Description:
Clone https://github.com/redhat-developer-tooling/openshift-vagrant/ (outside eclipse)
Create / Run CDK Server adapter pointing at openshift-vagrant/cdk-v2/
Clone https://github.com/burrsutter/cdk_helloworlds
import swarm-helloworld as a maven project in the workspace
Run maven build mvn clean compile package on the project.
Right-click on swarm-helloworld/dockerfile > Run As > Docker Image Build
Select Docker connection from CDK
Use 172.30.80.211:5000/burr/swarm-helloworld as repo name
The image deploys to the CDK docker connection/registry (See Docker Explorer)
Right click on the deployed image > Deploy to OpenShift
Select OpenShift Project (create a new one if necessary)
=>Error Message : This docker image was not pulled in the selected Docker connection. Mapping ports will not be possible.
The Finish Button stays disabled
http://screencast.com/t/I2syMLXNcO8
was:
Clone https://github.com/redhat-developer-tooling/openshift-vagrant/ (outside eclipse)
Create / Run CDK Server adapter pointing at openshift-vagrant/cdk-v2/
Clone https://github.com/burrsutter/cdk_helloworlds
import swarm-helloworld as a maven project in the workspace
Right-click on swarm-helloworld/dockerfile > Run As > Docker Image Build
Select Docker connection from CDK
Use 172.30.80.211:5000/burr/swarm-helloworld as repo name
The image deploys to the CDK docker connection/registry (See Docker Explorer)
Right click on the deployed image > Deploy to OpenShift
Select OpenShift Project (create a new one if necessary)
=>Error Message : This docker image was not pulled in the selected Docker connection. Mapping ports will not be possible.
The Finish Button stays disabled
http://screencast.com/t/I2syMLXNcO8
> Can't deploy Docker image to OpenShift
> --------------------------------------
>
> Key: JBIDE-21698
> URL: https://issues.jboss.org/browse/JBIDE-21698
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Clone https://github.com/redhat-developer-tooling/openshift-vagrant/ (outside eclipse)
> Create / Run CDK Server adapter pointing at openshift-vagrant/cdk-v2/
> Clone https://github.com/burrsutter/cdk_helloworlds
> import swarm-helloworld as a maven project in the workspace
> Run maven build mvn clean compile package on the project.
> Right-click on swarm-helloworld/dockerfile > Run As > Docker Image Build
> Select Docker connection from CDK
> Use 172.30.80.211:5000/burr/swarm-helloworld as repo name
> The image deploys to the CDK docker connection/registry (See Docker Explorer)
> Right click on the deployed image > Deploy to OpenShift
> Select OpenShift Project (create a new one if necessary)
> =>Error Message : This docker image was not pulled in the selected Docker connection. Mapping ports will not be possible.
> The Finish Button stays disabled
> http://screencast.com/t/I2syMLXNcO8
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-20513) tricky to login to openshift when token expires
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20513?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-20513:
---------------------------------------
The expiration would be related to the value configured by the auth service; we can't control that. In regards to how 'oc' works, are you auth'ing against a system set-up to use basic auth? The auth flow in general needs to be refactored to conform what happens in the 'oc' client. I believe there is an open issue against the rest client to address.
> tricky to login to openshift when token expires
> -----------------------------------------------
>
> Key: JBIDE-20513
> URL: https://issues.jboss.org/browse/JBIDE-20513
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> I logged in with token.
> 24hrs later I start eclipse and expand the connection in explorer
> expecting to just login.
> Here is what happens instead:
> a) info message (not error) is logged to error log hiding the explorer view
> b) after some seconds (seems there is a timeout) a login dialog comes up saying I need to sign in (no clear info that auth failed or token missing etc.).
> cancel the dialog since I'm trying to figure out what happened.
> c) Now the explorer just shows "You must obtain API token by visiting ..." as child and I cannot see straightforward way to log in again.
> Turns out Refresh does trigger login again.
> meanwhile command line 'oc' seem to be fine at logging in with token older than 24 hrs...can't verify that though, but in any case:
> a) do a user really need to re-login every 24 hours ?
> b) the error handling/dialogs shown are not very informative
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21634) Explorer, Properties: Allow a user to scale their deployment
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21634?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21634:
---------------------------------------
I think we should and could do this one as the mechanics are fairly trivial. We could make it easier by adding a capability in the rest client (if it doesnt exist already) which would mean the tooling would just need to provide the UI bit. Right click context with an input box?
> Explorer, Properties: Allow a user to scale their deployment
> ------------------------------------------------------------
>
> Key: JBIDE-21634
> URL: https://issues.jboss.org/browse/JBIDE-21634
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
> Labels: explorer, openshift_v3, properties
> Fix For: 4.3.1.CR1
>
>
> The web and cli allows a user to scale their deployments, which is only possible now in Eclipse by editing the replicationcontroller. Add UI to facilitate scaling. Scaling should be allowed in some sort of context menu when selecting any of:
> 1. deployment (replication controller)
> 2. eclipse view of a deployment (server) -> walk back to the currrent deployment
> 3. pod -> walk back to the current deployment
> updating 'spec.replicas' causes a new pods to spin up
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21734) Deploying of a docker image from docker explorer has ambiguous connection
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21734?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21734:
----------------------------------
Labels: deploy_docker_wizard openshift_v3 (was: )
> Deploying of a docker image from docker explorer has ambiguous connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-21734
> URL: https://issues.jboss.org/browse/JBIDE-21734
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
> Attachments: ambiguous_connection.png
>
>
> When I am trying to deploy a docker image to OpenShift from Docker Explorer view, there is a combo box with listed existing OpenShift connections. If there are more than 1 connection to a specific server, it is not possible to know which one I am selecting (not without knowing its projects and even then they have to be different), because there is no username. The combo box with connections contains only list of server URLs. It could be in format e.g. "username - connection" like we have it on other places. See following screenshot
> !ambiguous_connection.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21734) Deploying of a docker image from docker explorer has ambiguous connection
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21734?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21734:
----------------------------------
Labels: docker openshift_v3 (was: deploy_docker_wizard openshift_v3)
> Deploying of a docker image from docker explorer has ambiguous connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-21734
> URL: https://issues.jboss.org/browse/JBIDE-21734
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
> Attachments: ambiguous_connection.png
>
>
> When I am trying to deploy a docker image to OpenShift from Docker Explorer view, there is a combo box with listed existing OpenShift connections. If there are more than 1 connection to a specific server, it is not possible to know which one I am selecting (not without knowing its projects and even then they have to be different), because there is no username. The combo box with connections contains only list of server URLs. It could be in format e.g. "username - connection" like we have it on other places. See following screenshot
> !ambiguous_connection.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21734) Deploying of a docker image from docker explorer has ambiguous connection
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21734?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21734:
----------------------------------
Description:
When I am trying to deploy a docker image to OpenShift from Docker Explorer view, there is a combo box with listed existing OpenShift connections. If there are more than 1 connection to a specific server, it is not possible to know which one I am selecting (not without knowing its projects and even then they have to be different), because there is no username. The combo box with connections contains only list of server URLs. It could be in format e.g. "username - connection" like we have it on other places. See following screenshot
!ambiguous_connection.png!
was:
When I am trying to deploy a docker image to OpenShift from Docker Explorer view, there is a combo box with listed existing OpenShift connections. If there are more than 1 connection to a specific server, it is not possible to know which one I am selecting (not without knowing its projects and even then they have to be different), because there is no username. The combo box with connections contains only list of server URLs. See following screenshot
!ambiguous_connection.png!
> Deploying of a docker image from docker explorer has ambiguous connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-21734
> URL: https://issues.jboss.org/browse/JBIDE-21734
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
> Attachments: ambiguous_connection.png
>
>
> When I am trying to deploy a docker image to OpenShift from Docker Explorer view, there is a combo box with listed existing OpenShift connections. If there are more than 1 connection to a specific server, it is not possible to know which one I am selecting (not without knowing its projects and even then they have to be different), because there is no username. The combo box with connections contains only list of server URLs. It could be in format e.g. "username - connection" like we have it on other places. See following screenshot
> !ambiguous_connection.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month