February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21665) Scaling OS3 application does not work properly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21665?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21665: ------------------------------------------ {quote} (08:22:36 PM) adietisheim: jcantril: if resource is stale but not dirty I would replace it straight away (08:22:52 PM) adietisheim: jcantril: if stale and dirty I would ask the user if we can replace (08:23:06 PM) adietisheim: jcantril: makes sense? (08:23:07 PM) jcantril: adietisheim, and they will not be able to save (08:23:22 PM) adietisheim: jcantril: yes if they decide not to let us refresh it (08:23:23 PM) jcantril: adietisheim, that seems reasonable to me {quote} [~fbricon] acceptable to you? > Scaling OS3 application does not work properly > ---------------------------------------------- > > Key: JBIDE-21665 > URL: https://issues.jboss.org/browse/JBIDE-21665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > Attachments: edit_error.png > > > When I am trying to scale application via tooling, first attempt to set replicas amount works but every consecutive attempt to edit same resource fails. See following screenshot of the error followed by stack trace > !edit_error.png! > {code} > com.openshift.restclient.OpenShiftException: Could not update resource eap-app-1: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "replicationControllers \"eap-app-1\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "eap-app-1", > "kind": "replicationControllers" > }, > "code": 409 > } > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:480) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:247) > at org.jboss.tools.openshift.internal.ui.property.OpenShiftResourceDocumentProvider$2.run(OpenShiftResourceDocumentProvider.java:92) > 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": "replicationControllers \"eap-app-1\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "eap-app-1", > "kind": "replicationControllers" > }, > "code": 409 > } > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:226) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:191) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.put(UrlConnectionHttpClient.java:119) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:243) > ... 2 more > Caused by: java.io.IOException: Server returned HTTP response code: 409 for URL: https://10.1.2.2:8443/api/v1/namespaces/project01/replicationcontrollers/... > 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:187) > ... 4 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21665) Scaling OS3 application does not work properly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21665?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21665 at 2/15/16 2:25 PM: ------------------------------------------------------------------- {quote} (08:22:36 PM) adietisheim: jcantril: if resource is stale but not dirty I would replace it straight away (08:22:52 PM) adietisheim: jcantril: if stale and dirty I would ask the user if we can replace (08:23:06 PM) adietisheim: jcantril: makes sense? (08:23:07 PM) jcantril: adietisheim, and they will not be able to save (08:23:22 PM) adietisheim: jcantril: yes if they decide not to let us refresh it (08:23:23 PM) jcantril: adietisheim, that seems reasonable to me {quote} [~fbricon][~maxandersen] acceptable to you? was (Author: adietish): {quote} (08:22:36 PM) adietisheim: jcantril: if resource is stale but not dirty I would replace it straight away (08:22:52 PM) adietisheim: jcantril: if stale and dirty I would ask the user if we can replace (08:23:06 PM) adietisheim: jcantril: makes sense? (08:23:07 PM) jcantril: adietisheim, and they will not be able to save (08:23:22 PM) adietisheim: jcantril: yes if they decide not to let us refresh it (08:23:23 PM) jcantril: adietisheim, that seems reasonable to me {quote} [~fbricon] acceptable to you? > Scaling OS3 application does not work properly > ---------------------------------------------- > > Key: JBIDE-21665 > URL: https://issues.jboss.org/browse/JBIDE-21665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > Attachments: edit_error.png > > > When I am trying to scale application via tooling, first attempt to set replicas amount works but every consecutive attempt to edit same resource fails. See following screenshot of the error followed by stack trace > !edit_error.png! > {code} > com.openshift.restclient.OpenShiftException: Could not update resource eap-app-1: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "replicationControllers \"eap-app-1\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "eap-app-1", > "kind": "replicationControllers" > }, > "code": 409 > } > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:480) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:247) > at org.jboss.tools.openshift.internal.ui.property.OpenShiftResourceDocumentProvider$2.run(OpenShiftResourceDocumentProvider.java:92) > 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": "replicationControllers \"eap-app-1\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "eap-app-1", > "kind": "replicationControllers" > }, > "code": 409 > } > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:226) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:191) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.put(UrlConnectionHttpClient.java:119) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:243) > ... 2 more > Caused by: java.io.IOException: Server returned HTTP response code: 409 for URL: https://10.1.2.2:8443/api/v1/namespaces/project01/replicationcontrollers/... > 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:187) > ... 4 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21690) Include updated wildfly10 schema in catalog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21690?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21690: -------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.x) > Include updated wildfly10 schema in catalog > ------------------------------------------- > > Key: JBIDE-21690 > URL: https://issues.jboss.org/browse/JBIDE-21690 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Rob Stryker > Fix For: 4.3.1.CR1 > > > Wildfly 10 final has many updated schema which should be added. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21690) Include updated wildfly10 schema in catalog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21690?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-21690: ----------------------------------- Assignee: Rob Stryker > Include updated wildfly10 schema in catalog > ------------------------------------------- > > Key: JBIDE-21690 > URL: https://issues.jboss.org/browse/JBIDE-21690 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > Wildfly 10 final has many updated schema which should be added. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21690) Include updated wildfly10 schema in catalog

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-21690: ----------------------------------- Summary: Include updated wildfly10 schema in catalog Key: JBIDE-21690 URL: https://issues.jboss.org/browse/JBIDE-21690 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server Affects Versions: 4.3.1.Beta2 Reporter: Rob Stryker Wildfly 10 final has many updated schema which should be added. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21665) Scaling OS3 application does not work properly

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21665?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21665: --------------------------------------- [~adietish] The issue here is the open editor of the resource does not get updated with the new content, but it looks like the tabs are receiving the update callback as I would expect. Is there an established pattern of updating open editors that needs to be followed? Might @fbricon know? > Scaling OS3 application does not work properly > ---------------------------------------------- > > Key: JBIDE-21665 > URL: https://issues.jboss.org/browse/JBIDE-21665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > Attachments: edit_error.png > > > When I am trying to scale application via tooling, first attempt to set replicas amount works but every consecutive attempt to edit same resource fails. See following screenshot of the error followed by stack trace > !edit_error.png! > {code} > com.openshift.restclient.OpenShiftException: Could not update resource eap-app-1: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "replicationControllers \"eap-app-1\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "eap-app-1", > "kind": "replicationControllers" > }, > "code": 409 > } > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:480) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:247) > at org.jboss.tools.openshift.internal.ui.property.OpenShiftResourceDocumentProvider$2.run(OpenShiftResourceDocumentProvider.java:92) > 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": "replicationControllers \"eap-app-1\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "eap-app-1", > "kind": "replicationControllers" > }, > "code": 409 > } > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:226) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:191) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.put(UrlConnectionHttpClient.java:119) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:243) > ... 2 more > Caused by: java.io.IOException: Server returned HTTP response code: 409 for URL: https://10.1.2.2:8443/api/v1/namespaces/project01/replicationcontrollers/... > 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:187) > ... 4 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21685) wildfly-helloworld-ws indicates arquillian xsd is incorrect

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21685?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21685: ------------------------------------- To be clear, I think the prefix should be xs:, not xsd:, but I'm sure you'd know better than me. > wildfly-helloworld-ws indicates arquillian xsd is incorrect > ----------------------------------------------------------- > > Key: JBIDE-21685 > URL: https://issues.jboss.org/browse/JBIDE-21685 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Affects Versions: 4.3.1.Beta2 > Reporter: Rob Stryker > Fix For: 4.3.x > > > The following error is presented on the wildfly quickstarts 10.x branch for the wildfly-helloworld-ws project: > Multiple annotations found at this line: > - schema_reference.4: Failed to read schema document 'http://jboss.org/schema/arquillian/arquillian_1_0.xsd', because 1) could not > find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. > - cvc-elt.1: Cannot find the declaration of element 'arquillian'. > After viewing the xsd at http://jboss.org/schema/arquillian/arquillian_1_0.xsd, it's shown that the root element is `schema` rather than `xsd:schema` -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21685) wildfly-helloworld-ws indicates arquillian xsd is incorrect

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21685?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21685: ------------------------------------- [~aslak] https://github.com/wildfly/quickstart/tree/10.x/helloworld-ws > wildfly-helloworld-ws indicates arquillian xsd is incorrect > ----------------------------------------------------------- > > Key: JBIDE-21685 > URL: https://issues.jboss.org/browse/JBIDE-21685 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Affects Versions: 4.3.1.Beta2 > Reporter: Rob Stryker > Fix For: 4.3.x > > > The following error is presented on the wildfly quickstarts 10.x branch for the wildfly-helloworld-ws project: > Multiple annotations found at this line: > - schema_reference.4: Failed to read schema document 'http://jboss.org/schema/arquillian/arquillian_1_0.xsd', because 1) could not > find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. > - cvc-elt.1: Cannot find the declaration of element 'arquillian'. > After viewing the xsd at http://jboss.org/schema/arquillian/arquillian_1_0.xsd, it's shown that the root element is `schema` rather than `xsd:schema` -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21689) 82 updated schema unavailable on jboss.org

by Rob Stryker (JIRA)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21666) Set correct OpenShift resource name for Repplication controller in properties view

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21666?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21666: --------------------------------------- [~mlabuda] That's not quite how it is laid out in the web ui. The web has 'Deployments' which is actually a 'Deployment Config' and allows you to navigate to a list of deployments which are modified replication controllers. This is the same construct as 'builds' which are buildconfigs that allow you to navigate to builds. One difference is in the web ui, you are unable to see the resources referenced above for a 'service' (a.ka. application); you can only see this break down on the project level. If anything, we should enhance what is available on the 'details' tab for an 'application' such that it mostly mirrors what you can do in the web ui (e.g. scaling, latest build, latest deployment). We have JBIDE-21479 which starts to address this. Additionally, we could remove build and deployment configs and make the tabs more like what is offered in the web ui. That would be my preference. The current tab implementations were never meant to be the final solution, just the first step at making the transition to the new view. I think one challenge we have is not packing too much into the tab views now. > Set correct OpenShift resource name for Repplication controller in properties view > ---------------------------------------------------------------------------------- > > Key: JBIDE-21666 > URL: https://issues.jboss.org/browse/JBIDE-21666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > > At the moment we have following OpenShift resources listed for a project in Properties view: > * Builds > * Build Configs > * Deployment Configs > * Pods > * Deployments > * Image Streams > * Routes > * Services > What is misleading is having "Deployment Configs" and "Deployments". We are trying to copy web-UI, as far as I know. But in the web-UI under Deployments are placed "Deployment Configs". We, under "Deployments" in properties view, have "Replication Controllers". So its misleading for me. I think we should rename our Deployment Configs to Deployment and our Deployments to Replication Controllers, which are missing in web-ui because the most significant functionality accessible via Replication Controllers is editable in web-ui through overview page (e.g spinner for amount of pods). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016