[JBoss JIRA] (JBIDE-22434) Properties not showing whole Docker image ID
by Josef Kopriva (JIRA)
Josef Kopriva created JBIDE-22434:
-------------------------------------
Summary: Properties not showing whole Docker image ID
Key: JBIDE-22434
URL: https://issues.jboss.org/browse/JBIDE-22434
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: docker
Affects Versions: 4.4.0.Alpha2
Environment: Version: 10.0.0.Alpha1
Build id: Alpha1-v20160525-0422-B5425
Build date: 20160525-0422
Reporter: Josef Kopriva
Attachments: Dockerfile, Docker_Image_ID.png
Image ID in properties tab is not complete, but Parent ID is complete.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22159) Docker image is empty after selecting it from Image search wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22159?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22159:
------------------------------------------
[~scabanovich] can you please estimate how much story points you'd need for this?
> Docker image is empty after selecting it from Image search wizard
> -----------------------------------------------------------------
>
> Key: JBIDE-22159
> URL: https://issues.jboss.org/browse/JBIDE-22159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha3
>
>
> As discovered in https://github.com/jbosstools/jbosstools-openshift/pull/1106#issuecomment..., provided you have a docker and an OpenShift connection:
> - In OpenShift Explorer, select the Deploy Image menu
> - select the docker connection
> - type a docker image name already pulled in the docker daemon
> - delete it and click the search... button
> - select the same docker image as previously typed
> - once the search wizard closes, the docker Image name field is still empty.
> See http://screencast.com/t/iTJX7SjB
> As per [~scabanovich]:
> {quote}
> it is possible that validator does not let empty string to model, so model remains with valid previous value. Then, when you select that same value in the dialog, model is notified, but it already has that value and it does not notify ui because it did not change
> {quote}
> and his fix proposal:
> {quote}
> before calling setImageName(newValue) check if it has the same value, then call setImageName(""); and only after this check and adjustment call setImageName(newValue).
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22433) Properties: Add Storage tab
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22433?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22433 at 5/25/16 6:43 AM:
-------------------------------------------------------------------
[~jcantrill] if I understand this right PVC (claimed storage) and PV (actual storage) are 2 different things, and this issue is about the fullfilled storage (not the claims). This terefore doesnt require https://issues.jboss.org/browse/OSJC-216, correct?
was (Author: adietish):
[~jcantrill] if I understand this right PVC (claimed storage) and PV (actual storage) are 2 different things, and this issue is about the fullfilled storage (not the claims). This terefore isnt related to https://issues.jboss.org/browse/OSJC-216, correct?
> Properties: Add Storage tab
> ---------------------------
>
> Key: JBIDE-22433
> URL: https://issues.jboss.org/browse/JBIDE-22433
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Fred Bricon
> Labels: openshift_v3, properties
> Fix For: 4.4.x
>
> Attachments: storage from web console.png
>
>
> We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties.
> Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22433) Properties: Add Storage tab
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22433?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22433:
------------------------------------------
[~jcantrill] if I understand this right PVC (claimed storage) and PV (actual storage) are 2 different things, and this issue is about the fullfilled storage (not the claims). This terefore isnt related to https://issues.jboss.org/browse/OSJC-216, correct?
> Properties: Add Storage tab
> ---------------------------
>
> Key: JBIDE-22433
> URL: https://issues.jboss.org/browse/JBIDE-22433
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Fred Bricon
> Labels: openshift_v3, properties
> Fix For: 4.4.x
>
> Attachments: storage from web console.png
>
>
> We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties.
> Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22433) Properties: Add Storage tab
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22433?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22433:
-------------------------------------
Labels: openshift_v3 properties (was: )
> Properties: Add Storage tab
> ---------------------------
>
> Key: JBIDE-22433
> URL: https://issues.jboss.org/browse/JBIDE-22433
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Fred Bricon
> Labels: openshift_v3, properties
> Fix For: 4.4.x
>
> Attachments: storage from web console.png
>
>
> We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties.
> Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22433) Properties: Add Storage tab to OpenShift properties
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22433?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22433:
-------------------------------------
Summary: Properties: Add Storage tab to OpenShift properties (was: Add Storage tab to OpenShift properties)
> Properties: Add Storage tab to OpenShift properties
> ---------------------------------------------------
>
> Key: JBIDE-22433
> URL: https://issues.jboss.org/browse/JBIDE-22433
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Fred Bricon
> Fix For: 4.4.x
>
> Attachments: storage from web console.png
>
>
> We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties.
> Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22433) Properties: Add Storage tab
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22433?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22433:
-------------------------------------
Summary: Properties: Add Storage tab (was: Properties: Add Storage tab to OpenShift properties)
> Properties: Add Storage tab
> ---------------------------
>
> Key: JBIDE-22433
> URL: https://issues.jboss.org/browse/JBIDE-22433
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Fred Bricon
> Fix For: 4.4.x
>
> Attachments: storage from web console.png
>
>
> We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties.
> Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22371) Allow users easily manage environment variables of OpenShift application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22371?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22371:
------------------------------------------
[~scabanovich] can you please estimate how many story-points you'd need for this?
> Allow users easily manage environment variables of OpenShift application
> ------------------------------------------------------------------------
>
> Key: JBIDE-22371
> URL: https://issues.jboss.org/browse/JBIDE-22371
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha3
>
>
> At the moment to add a new environment variable/edit an existing one. Environment variables are located at deployment configuration. At the moment it requires to open Properties view, select a deployment config, open context menu Edit... and find in json where the spot with env. vars is located and add more key:value pair or edit existing ones. It would be nice if we would have some dialog/wizard to easily manage variables.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22423) Edit resources: 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:
-------------------------------------
Summary: Edit resources: Cannot edit build config resource (was: Cannot edit build config resource)
> 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
> Labels: openshift_v3, resource_editor
> 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
[JBoss JIRA] (JBIDE-22423) Edit resources: 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:
-------------------------------------
Labels: openshift_v3 resource_editor (was: openshift_v3)
> 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
> Labels: openshift_v3, resource_editor
> 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