[JBoss JIRA] (JBIDE-22467) Include Docker tooling 2.0.0.RC3
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-22467:
-------------------------------------
Summary: Include Docker tooling 2.0.0.RC3
Key: JBIDE-22467
URL: https://issues.jboss.org/browse/JBIDE-22467
Project: Tools (JBoss Tools)
Issue Type: Task
Components: target-platform
Affects Versions: 4.4.0.Alpha2
Reporter: Xavier Coulon
Include the Docker tooling 2.0.0.RC3 once it is available (link to update site will be posted here).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[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)
7 years, 11 months
[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)
7 years, 11 months
[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)
7 years, 11 months