November 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4168) Updated the "Setting up CDK software components" for adding Vagrant box

by Budh Ram Gurung (JIRA)

[ https://issues.jboss.org/browse/JBDS-4168?page=com.atlassian.jira.plugin.... ] Budh Ram Gurung updated JBDS-4168: ---------------------------------- Description: We have updated our Vagrantfiles so that user can use any customized box name. This can be easily done with adding an environment variable like `BOX`. The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. was: We have updated our Vagrantfiles so that user can use any customized box name. The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. > Updated the "Setting up CDK software components" for adding Vagrant box > ----------------------------------------------------------------------- > > Key: JBDS-4168 > URL: https://issues.jboss.org/browse/JBDS-4168 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: cdk > Reporter: Budh Ram Gurung > > We have updated our Vagrantfiles so that user can use any customized box name. > This can be easily done with adding an environment variable like `BOX`. > The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4168) Updated the "Setting up CDK software components" for adding Vagrant box

by Budh Ram Gurung (JIRA)

[ https://issues.jboss.org/browse/JBDS-4168?page=com.atlassian.jira.plugin.... ] Budh Ram Gurung updated JBDS-4168: ---------------------------------- Description: We have updated our Vagrantfiles so that user can use any customized box name. This can be easily done with adding an environment variable like *BOX*. The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. was: We have updated our Vagrantfiles so that user can use any customized box name. This can be easily done with adding an environment variable like **BOX**. The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. > Updated the "Setting up CDK software components" for adding Vagrant box > ----------------------------------------------------------------------- > > Key: JBDS-4168 > URL: https://issues.jboss.org/browse/JBDS-4168 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: cdk > Reporter: Budh Ram Gurung > > We have updated our Vagrantfiles so that user can use any customized box name. > This can be easily done with adding an environment variable like *BOX*. > The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4168) Updated the "Setting up CDK software components" for adding Vagrant box

by Budh Ram Gurung (JIRA)

Budh Ram Gurung created JBDS-4168: ------------------------------------- Summary: Updated the "Setting up CDK software components" for adding Vagrant box Key: JBDS-4168 URL: https://issues.jboss.org/browse/JBDS-4168 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: cdk Reporter: Budh Ram Gurung We have updated our Vagrantfiles so that user can use any customized box name. The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23360) Select Route: Remember selected route in ambiguous routing does not work

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23360?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23360. --------------------------------- Verified in DevStudio 10.2.0.AM3 build id AM3-v20161104-1659-B6372. > Select Route: Remember selected route in ambiguous routing does not work > ------------------------------------------------------------------------ > > Key: JBIDE-23360 > URL: https://issues.jboss.org/browse/JBIDE-23360 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, select_route > Fix For: 4.4.2.AM3 > > > When selecting Show In - Web Browser on a project with more services, routing is ambiguous. There is shown a shell "Select Route" with a checkbox "Remember selected route". This checkbox does not work. If I check it and then click OK button, I get the same prompt again next time I select Show In - Web Browser context menu item. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23371) Deploy image wizard: "Services and Routing Settings" page needs to explain to user what the settings result in.

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23371?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23371: ---------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.2.AM3) > Deploy image wizard: "Services and Routing Settings" page needs to explain to user what the settings result in. > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23371 > URL: https://issues.jboss.org/browse/JBIDE-23371 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.Final > > Attachments: services-and-routing-page.png > > > steps to reproduce: > # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu > # EXEC: get to the "Services & Routing Settings" page > Result: > !services-and-routing-page.png! > The page allows to add/remove/edit ports and to configure a route. It's not obvious to the user what these settings are for and what they result in being created (a single service and route are created). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23357) Deploy Docker Wizard: Image is not revalidated if going back to Deploy an Image wizard page

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23357?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23357. --------------------------------- Verified in DevStudio 10.2.0.AM3 build id AM3-v20161104-1659-B6372. > Deploy Docker Wizard: Image is not revalidated if going back to Deploy an Image wizard page > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23357 > URL: https://issues.jboss.org/browse/JBIDE-23357 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > When I fill in valid image into the wizard and hit next, there is a check on existence of such image and its metadata are fetched. Problem is when I go back to the Deploy an Image wizard page and put there invalid image name. Finish button is still enabled and it allows user to use non-existing (made-up) image to deploy. It results in wrong deployment. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23029. --------------------------------- Nothing to verify. Closing. > Integration tests: Tests should be able to run individually > ----------------------------------------------------------- > > Key: JBIDE-23029 > URL: https://issues.jboss.org/browse/JBIDE-23029 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.2.AM3 > > > We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need). > This is even more true since running the whole suite is a lengthy task. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22914?page=com.atlassian.jira.plugi... ] 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)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23061) Integration tests: have warning when scaling to 0 asserted

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23061?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23061. --------------------------------- Test exists in IT repo, closing. > Integration tests: have warning when scaling to 0 asserted > ---------------------------------------------------------- > > Key: JBIDE-23061 > URL: https://issues.jboss.org/browse/JBIDE-23061 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, scaling_pods_wizard > Fix For: 4.4.2.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23355) Deploy Docker Wizard: No docker connection is preselected in the wizard even it is selected in docker explorer

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23355?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23355. --------------------------------- Verified in DevStudio 10.2.0.AM3 build id AM3-v20161104-1659-B6372. > Deploy Docker Wizard: No docker connection is preselected in the wizard even it is selected in docker explorer > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23355 > URL: https://issues.jboss.org/browse/JBIDE-23355 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > When opening Deploy Image to OpenShift wizard from context menu of a project and I have a docker connection selected in Docker explorer, the combo box with docker connection in the wizard is empty. The Docker Connection: combo should have filled currently selected docker connection in docker explorer. > steps to reproduce: > # ASSERT: have a docker connection and an openshift connection with at least 1 project > # EXEC: in Docker explorer: select a docker connection > # EXEC: in OpenShift explorer: pick "Deploy Docker Image..." in the context menu of a project > Result: > Deploy Docker Image wizard pops up, Docker connection is not preselected, while it could (and we do this in many wizards), since we selected a docker connection in Docker explorer > !empty-docker-connection.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2016