[jbosstools-issues] [JBoss JIRA] (JBIDE-22914) OpenShift Deployment: Deploy latest does not work correctly

Marián Labuda (JIRA) issues at jboss.org
Tue Nov 8 05:51:00 EST 2016


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

Marián Labuda closed JBIDE-22914.
---------------------------------


Verified in DevStudio 10.2.0.AM3 build id AM3-v20161104-1659-B6372.

> OpenShift Deployment: Deploy latest does not work correctly
> -----------------------------------------------------------
>
>                 Key: JBIDE-22914
>                 URL: https://issues.jboss.org/browse/JBIDE-22914
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.1.AM3
>            Reporter: Marián Labuda
>            Assignee: Dmitrii Bocharov
>              Labels: openshift_v3
>             Fix For: 4.4.2.AM3
>
>
> When I have an application where no replication controller is yet and I want to deploy latest, I get following error:
> {code}
> Unable to perform a deployment for config hello-openshift
> com.openshift.restclient.NotFoundException: replicationcontrollers "hello-openshift-0" not found
> 	at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:105)
> 	at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:59)
> 	at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
> 	at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
> 	at okhttp3.RealCall.execute(RealCall.java:57)
> 	at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:200)
> 	at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:181)
> 	at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:269)
> 	at com.openshift.internal.restclient.capability.resources.DeployCapability.deploy(DeployCapability.java:59)
> 	at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1$1.visit(TriggerDeploymentHandler.java:90)
> 	at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1$1.visit(TriggerDeploymentHandler.java:1)
> 	at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91)
> 	at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1.doRun(TriggerDeploymentHandler.java:85)
> 	at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This is wrong, because it is trying to "deploy latest replication controller" instead of deploying latest deployment configuration (as it works e.g. from oc binary - deployment uses latest deployment configuration not replication controller which could be understood as instance of deployment configuration). Therefore if there is no replication controller and I click Deploy Latest in context menu of a service in OpenShift Explorer view or in context menu of a deployment configuration in properties view, I get the error.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)



More information about the jbosstools-issues mailing list