[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-204:
---------------------------------------
Summary: 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
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
[JBoss JIRA] (JBIDE-22423) 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 updated JBIDE-22423:
----------------------------------
Steps to Reproduce:
ASSERT: Have an application based on eap 6.4 template.
EXEC: Select build config in Properties view.
EXEC: Select context menu item Edit... and change build config and try to save.
RESULT: Error pops up.
EXPECTED RESULT: Build config is changed and saved successfully.
Workaround Description: Delete key:value pair "from" : {} in build config in image change trigger
Workaround: Workaround Exists
> 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
>
> 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
[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars
by Thomas Mäder (JIRA)
Thomas Mäder created JBDS-3903:
----------------------------------
Summary: Platform Installer does not Setup Docker Env-Vars
Key: JBDS-3903
URL: https://issues.jboss.org/browse/JBDS-3903
Project: Red Hat Developer Studio (DevStudio)
Issue Type: Feature Request
Components: platform-installer
Affects Versions: 10.0.0.Alpha1
Environment: Windows
Reporter: Thomas Mäder
I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection.
Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection.
As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22423) Cannot edit build config resource
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22423:
-------------------------------------
Summary: Cannot edit build config resource
Key: JBIDE-22423
URL: https://issues.jboss.org/browse/JBIDE-22423
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.0.Alpha2
Reporter: Marián Labuda
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
[JBoss JIRA] (JBIDE-22423) 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 updated JBIDE-22423:
----------------------------------
Issue Type: Bug (was: Enhancement)
> 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
>
> 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
[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21828:
---------------------------------------
I'm pretty certain at the moment one is unable to refresh a service because
of the caching implementation.
--
--
Jeff Cantrill
Senior Software Engineer, Red Hat Engineering
OpenShift Integration Services
Red Hat, Inc.
*Office*: 703-748-4420 | 866-546-8970 ext. 8162420
jcantril(a)redhat.com
http://www.redhat.com
> 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: Jeff Cantrill
> 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