May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-152) Restore dialog when building Docker image if connection does not exist anymore [EBZ#484485]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-152?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon resolved ERT-152. ------------------------------- Resolution: Done > Restore dialog when building Docker image if connection does not exist anymore [EBZ#484485] > ------------------------------------------------------------------------------------------- > > Key: ERT-152 > URL: https://issues.jboss.org/browse/ERT-152 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 4.2.1, Docker, bzira > Fix For: Neon.1 (4.6) > > > Otherwise, the tooling fails with the following error: "No Docker connection named 'xyz' exists." and the only workaround is to remove the associated launch configuration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3913) EAP 7 shell scripts have changes since EAP 6.4; need to update devstudio installer accordingly

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3913?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3913: ------------------------------------- I tried this in devstudio-10.0.0.Alpha3-v20160531-1024-B5476-installer-eap.jar . After installation, EAP 7 was set up automatically and it then started correctly. > EAP 7 shell scripts have changes since EAP 6.4; need to update devstudio installer accordingly > ---------------------------------------------------------------------------------------------- > > Key: JBDS-3913 > URL: https://issues.jboss.org/browse/JBDS-3913 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: installer > Environment: http://www.qa.jboss.com/binaries/RHDS/10.0/snapshots/builds/devstudio.pro... > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.Alpha3 > > Attachments: 1.png, 2.png > > > See attached screenshots -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Martin Malina commented on ERT-204: ----------------------------------- I tried this today and it still doesn't work. The search button does find my docker machine and I can select it. It then correctly fills in the name and IP, but it does not check the authentication checkbox and so there is no cert path configured and it doesn't work. > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22195) Docker-machine look-up does not work

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22195?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22195: --------------------------------------- I reopened ERT-204 > Docker-machine look-up does not work > ------------------------------------ > > Key: JBIDE-22195 > URL: https://issues.jboss.org/browse/JBIDE-22195 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha2 > > > The {{Search...}} dialog for Docker Machines in the New Connection wizard in the Docker tooling does not work: a warning message appears in the Error Log view, saying : > {quote} > The 'docker-machine' command could not be located in /usr/bin:/bin:/usr/sbin:/sbin > {quote} > even though the preferences show that the {{docker-machine}} command is located in {{/usr/local/bin}}. > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=493328 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22195) Docker-machine look-up does not work

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22195?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22195: --------------------------------------- I just tried this on Windows with latest docker tooling from http://download.eclipse.org/linuxtools/updates-docker-nightly/ and it works half way. The search button does find my docker machine and I can select it. It then correctly fills in the name and IP, but it does not check the authentication checkbox and so there is no cert path configured and it doesn't work. > Docker-machine look-up does not work > ------------------------------------ > > Key: JBIDE-22195 > URL: https://issues.jboss.org/browse/JBIDE-22195 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha2 > > > The {{Search...}} dialog for Docker Machines in the New Connection wizard in the Docker tooling does not work: a warning message appears in the Error Log view, saying : > {quote} > The 'docker-machine' command could not be located in /usr/bin:/bin:/usr/sbin:/sbin > {quote} > even though the preferences show that the {{docker-machine}} command is located in {{/usr/local/bin}}. > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=493328 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22463) Update CDK code after API change in Docker tooling

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22463?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22463: -------------------------------- Fix Version/s: 4.4.0.Alpha3 Story Points: 1 Sprint: devex #115 May 2016 > Update CDK code after API change in Docker tooling > -------------------------------------------------- > > Key: JBIDE-22463 > URL: https://issues.jboss.org/browse/JBIDE-22463 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha3 > > > The APi to create a connection changed in the latest version of Docker tooling. This impacts the {{CDKDockerUtility}} class in the {{org.jboss.tools.openshift.cdk.server}} bundle. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3788) Folder selection dialog should consume focus when opened

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3788?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3788. ----------------------------- Verified in B159. > Folder selection dialog should consume focus when opened > -------------------------------------------------------- > > Key: JBDS-3788 > URL: https://issues.jboss.org/browse/JBDS-3788 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha2 > > > This is an extension of JBDS-3696. Hitting Browse opens a folder selection dialog. At this point nothing stops me from switching back to the main window and clicking whatever UI element I want. > The trouble is that while these elements do not seem to respond when the browse dialog is shown, all the actions get queued up and execute once the dialog closes. > But wait - it gets better! I can open the dialog and then click a sequence of buttons (like 'continue', 'back' - many times) and it always lands on a different page in the end. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22423) Edit resources: Cannot edit build config resource

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22423?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22423. --------------------------------- Verified in devstudio with build id: Alpha3-v20160531-0503-B5474. > Edit resources: Cannot edit build config resource > ------------------------------------------------- > > Key: JBIDE-22423 > URL: https://issues.jboss.org/browse/JBIDE-22423 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Labels: openshift_v3, resource_editor > Fix For: 4.4.0.Alpha3 > > Attachments: error-saving-buildconfig.png > > > When I am trying to edit build config resource, I get an error. See stack trace below. Problem causes key value pair "from" : {} in image change trigger. I don't know why it is added here, but output from oc binary (oc get bc eap-app -o json) does not show this key value in json (it's the only difference). > See stack trace of the error > {code} > Could not update "[eapapp] Build Config : eap-app.json" for project "eapapp" : BuildConfig "eap-app" is invalid: triggers[2].imageChange.from.kind: invalid value '', Details: only an ImageStreamTag type of reference is allowed in an ImageChange trigger. > com.openshift.restclient.OpenShiftException: Could not update resource eap-app: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "BuildConfig \"eap-app\" is invalid: triggers[2].imageChange.from.kind: invalid value '', Details: only an ImageStreamTag type of reference is allowed in an ImageChange trigger.", > "reason": "Invalid", > "details": { > "name": "eap-app", > "kind": "BuildConfig", > "causes": [ > { > "reason": "FieldValueInvalid", > "message": "invalid value '', Details: only an ImageStreamTag type of reference is allowed in an ImageChange trigger.", > "field": "triggers[2].imageChange.from.kind" > } > ] > }, > "code": 422 > } > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:488) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:254) > at org.jboss.tools.openshift.internal.ui.property.OpenShiftResourceDocumentProvider$2.run(OpenShiftResourceDocumentProvider.java:131) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: com.openshift.internal.restclient.http.HttpClientException: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "BuildConfig \"eap-app\" is invalid: triggers[2].imageChange.from.kind: invalid value '', Details: only an ImageStreamTag type of reference is allowed in an ImageChange trigger.", > "reason": "Invalid", > "details": { > "name": "eap-app", > "kind": "BuildConfig", > "causes": [ > { > "reason": "FieldValueInvalid", > "message": "invalid value '', Details: only an ImageStreamTag type of reference is allowed in an ImageChange trigger.", > "field": "triggers[2].imageChange.from.kind" > } > ] > }, > "code": 422 > } > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:278) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:243) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.put(UrlConnectionHttpClient.java:165) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:250) > ... 2 more > Caused by: java.io.IOException: Server returned HTTP response code: 422 for URL: https://10.1.2.2:8443/oapi/v1/namespaces/eapapp/buildconfigs/eap-app > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1840) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:239) > ... 4 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22420) Application Wizard: Finish button is still enabled upon selection of a builder image if a template was selected before

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22420?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22420. --------------------------------- Verified in devstudio with build id: Alpha3-v20160531-0503-B5474. > Application Wizard: Finish button is still enabled upon selection of a builder image if a template was selected before > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22420 > URL: https://issues.jboss.org/browse/JBIDE-22420 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > If I select a template in New OpenShift Application wizard, the Finish button is enabled and it is possible to skip all wizard pages and have created an application. If I select a builder image in the wizard, Finish is disabled (although on the next wizard page it gets enabled even I do not set any other value manually). But having selecting a template at first in the wizard and then selecting a build image, Finish button is still enabled. Click on the button cause NPE with following stack trace: > {code}Unable to create resources to deploy image null > java.lang.IllegalArgumentException: newValue is null > at org.jboss.dmr.ModelNode.set(ModelNode.java:499) > at com.openshift.internal.restclient.model.Service.setSelector(Service.java:115) > at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.stubService(DeployImageJob.java:254) > at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.generateResources(DeployImageJob.java:150) > at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.doRun(DeployImageJob.java:99) > 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 message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3874) Rename default install folder to match the new branding

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3874?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3874. ----------------------------- As per the last build, we got developer-studio folder => verfied. > Rename default install folder to match the new branding > ------------------------------------------------------- > > Key: JBDS-3874 > URL: https://issues.jboss.org/browse/JBDS-3874 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.0.0.Alpha2 > > > Since we are no longer calling devstudio anything begining with 'j' (i.e. jboss devstudio, jbds, etc.) it would be nice to rename the default installation folder from 'jbdevstudio' to something more consistent with the new branding, like 'devstudio'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016