May 2016 - jbosstools-issues - Jboss List Archives

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22423?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22423: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 > 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 > Labels: openshift_v3 > Fix For: 4.4.0.Alpha3 > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22412) Enhance JobChainBuilder with conditions for starting the next job

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22412?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22412: ------------------------------------- Story Points: 2 (was: 1) > Enhance JobChainBuilder with conditions for starting the next job > ----------------------------------------------------------------- > > Key: JBIDE-22412 > URL: https://issues.jboss.org/browse/JBIDE-22412 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha3 > > > For example, if the chain of jobs is loading content of a wizard or an editor, and user may close it before jobs are completed, there is no need to schedule the next job in the chain when the previous job is done. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 just tried this today with Eclipse Neon RC1 on Windows 10 with docker tools nightly (http://download.eclipse.org/linuxtools/update-neon-docker-rc2) and I'm still seeing exactly the same as I reported earlier: https://issues.jboss.org/browse/JBIDE-22195?focusedCommentId=13193943&pag... {quote} when I first open the New Docker Connection wizard (with a docker machine already running), I get this popup: You need to set the preferences for Docker Machine. OK Cancel I click ok, Docker Machine preference page opens. But it shows a warning: docker-machine could not be located in the directory. The directory is set correctly to C:\Program Files\Docker Toolbox. Once I click to edit the path, the warning disappears. But I still can't press OK. When I click Cancel, I'm back in the new connection wizard and get a popup: No connections were found. If I click again the Search button, I get the popup again: "You need to set the preferences for Docker Machine." And from here I can go in circles. {quote} > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ] Thomas Mäder edited comment on JBIDE-21828 at 5/25/16 5:55 AM: --------------------------------------------------------------- [~jcantrill], what was the "delete project issue" you tried to fix by doing async notifications? was (Author: tmader): [~jcantrill] Jeff, what was the "delete project issue" you tried to fix by doing async notifications? > OpenShift Explorer view flickers when refreshing a service > ---------------------------------------------------------- > > Key: JBIDE-21828 > URL: https://issues.jboss.org/browse/JBIDE-21828 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Thomas Mäder > Fix For: 4.4.0.Alpha3 > > Attachments: Screenshot 2016-03-08 10.32.39.png > > > When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls. > Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod. > Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services. > Custom/added logs in the console: > {code} > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-21828: -------------------------------------- [~jcantrill] Jeff, what was the "delete project issue" you tried to fix by doing async notifications? > OpenShift Explorer view flickers when refreshing a service > ---------------------------------------------------------- > > Key: JBIDE-21828 > URL: https://issues.jboss.org/browse/JBIDE-21828 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Thomas Mäder > Fix For: 4.4.0.Alpha3 > > Attachments: Screenshot 2016-03-08 10.32.39.png > > > When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls. > Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod. > Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services. > Custom/added logs in the console: > {code} > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22383) Application Wizard: Selected project combo box is empty

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22383?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22383: ------------------------------------------ merged to master > Application Wizard: Selected project combo box is empty > ------------------------------------------------------- > > Key: JBIDE-22383 > URL: https://issues.jboss.org/browse/JBIDE-22383 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > Having a connection with several projects and a different than the first one project selected in OpenShift Explorer view, opening of a New OpenShift Application wizard via shell menu File - New - OpenShift Application leaves combo box for a project empty. If the first project is preselect in OpenShift Explorer view, its ok. Issues is only with selected project different than the first one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22383) Application Wizard: Selected project combo box is empty

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22383?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-22383. -------------------------------------- Resolution: Done > Application Wizard: Selected project combo box is empty > ------------------------------------------------------- > > Key: JBIDE-22383 > URL: https://issues.jboss.org/browse/JBIDE-22383 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > Having a connection with several projects and a different than the first one project selected in OpenShift Explorer view, opening of a New OpenShift Application wizard via shell menu File - New - OpenShift Application leaves combo box for a project empty. If the first project is preselect in OpenShift Explorer view, its ok. Issues is only with selected project different than the first one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-155) Expose DockerContainerConfig#labels() in API [EBZ#485936]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-155?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon resolved ERT-155. ------------------------------- Resolution: Done Patch applied upstream. > Expose DockerContainerConfig#labels() in API [EBZ#485936] > --------------------------------------------------------- > > Key: ERT-155 > URL: https://issues.jboss.org/browse/ERT-155 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira > > This method is implemented in DockerContainerConfig but not exposed in the API (it was implemented for Linux Tools 4.2.1 which did not allow for API changes) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-155) Expose DockerContainerConfig#labels() in API [EBZ#485936]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-155?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-155: ------------------------------ Fix Version/s: Neon (4.6) RC2 > Expose DockerContainerConfig#labels() in API [EBZ#485936] > --------------------------------------------------------- > > Key: ERT-155 > URL: https://issues.jboss.org/browse/ERT-155 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira > Fix For: Neon (4.6) RC2 > > > This method is implemented in DockerContainerConfig but not exposed in the API (it was implemented for Linux Tools 4.2.1 which did not allow for API changes) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-155) Expose DockerContainerConfig#labels() in API [EBZ#485936]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-155?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon reassigned ERT-155: --------------------------------- Assignee: Jeff Johnston > Expose DockerContainerConfig#labels() in API [EBZ#485936] > --------------------------------------------------------- > > Key: ERT-155 > URL: https://issues.jboss.org/browse/ERT-155 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira > > This method is implemented in DockerContainerConfig but not exposed in the API (it was implemented for Linux Tools 4.2.1 which did not allow for API changes) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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