February 2016 - jbosstools-issues

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21666?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21666: ------------------------------------- Fix Version/s: 4.4.x > Properties view: 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 > Fix For: 4.4.x > > > 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

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21666?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21666: ------------------------------------- Priority: Major (was: Critical) > Properties view: 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 > Labels: openshift_v3 > Fix For: 4.4.x > > > 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

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21666?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21666: ------------------------------------- Labels: openshift_v3 properties (was: openshift_v3) > Properties view: 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 > Labels: openshift_v3, properties > Fix For: 4.4.x > > > 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

[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: ------------------------------------------ [~jcantrill] IEditorPart offers #isDirty. But then how to get from OpenShiftResourceDocumentProvider to the editor? I dont know. On the other hand OpenShiftResourceDocumentProvider#canSaveDocument(getInput()) should report the same dirty state as far as I can read API and impl. > 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 > Assignee: Jeff Cantrill > 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-21666) Set correct OpenShift resource name for Repplication controller in properties view

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21666?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21666: --------------------------------------- Yeah, I am aware this is not final solution of properties view and I agree with you. > 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

[JBoss JIRA] (JBIDE-21683) Property sheet cells are editable

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21683?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21683: --------------------------------------- Ok, I can accept it as a temporarily solution. > Property sheet cells are editable > --------------------------------- > > Key: JBIDE-21683 > URL: https://issues.jboss.org/browse/JBIDE-21683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.x > Environment: Boss Openshift UI Plugin Version: 3.1.0.CR1-v20160202-0335-B166 > Reporter: Steve Speicher > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > Attachments: Screen Shot 2016-02-06 at 9.03.05 AM.png > > > When I bring up the property sheet, values are editable but I can't really edit them. It would be good if users were disallowed from changing values (like the property name field is restricted) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21698) Can't deploy Docker image to OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21698?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21698: ----------------------------------- Assignee: Jeff Cantrill > Can't deploy Docker image to OpenShift > -------------------------------------- > > Key: JBIDE-21698 > URL: https://issues.jboss.org/browse/JBIDE-21698 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.1.CR1 > > > Clone https://github.com/redhat-developer-tooling/openshift-vagrant/ (outside eclipse) > Create / Run CDK Server adapter pointing at openshift-vagrant/cdk-v2/ > Clone https://github.com/burrsutter/cdk_helloworlds > import swarm-helloworld as a maven project in the workspace > Right-click on swarm-helloworld/dockerfile > Run As > Docker Image Build > Select Docker connection from CDK > Use 172.30.80.211:5000/burr/swarm-helloworld as repo name > The image deploys to the CDK docker connection/registry (See Docker Explorer) > Right click on the deployed image > Deploy to OpenShift > Select OpenShift Project (create a new one if necessary) > =>Error Message : This docker image was not pulled in the selected Docker connection. Mapping ports will not be possible. > The Finish Button stays disabled > http://screencast.com/t/I2syMLXNcO8 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21698) Can't deploy Docker image to OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21698?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21698: -------------------------------- Fix Version/s: 4.3.1.CR1 > Can't deploy Docker image to OpenShift > -------------------------------------- > > Key: JBIDE-21698 > URL: https://issues.jboss.org/browse/JBIDE-21698 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.1.CR1 > > > Clone https://github.com/redhat-developer-tooling/openshift-vagrant/ (outside eclipse) > Create / Run CDK Server adapter pointing at openshift-vagrant/cdk-v2/ > Clone https://github.com/burrsutter/cdk_helloworlds > import swarm-helloworld as a maven project in the workspace > Right-click on swarm-helloworld/dockerfile > Run As > Docker Image Build > Select Docker connection from CDK > Use 172.30.80.211:5000/burr/swarm-helloworld as repo name > The image deploys to the CDK docker connection/registry (See Docker Explorer) > Right click on the deployed image > Deploy to OpenShift > Select OpenShift Project (create a new one if necessary) > =>Error Message : This docker image was not pulled in the selected Docker connection. Mapping ports will not be possible. > The Finish Button stays disabled > http://screencast.com/t/I2syMLXNcO8 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21698) Can't deploy Docker image to OpenShift

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21698: ----------------------------------- Summary: Can't deploy Docker image to OpenShift Key: JBIDE-21698 URL: https://issues.jboss.org/browse/JBIDE-21698 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Fred Bricon Priority: Blocker Clone https://github.com/redhat-developer-tooling/openshift-vagrant/ (outside eclipse) Create / Run CDK Server adapter pointing at openshift-vagrant/cdk-v2/ Clone https://github.com/burrsutter/cdk_helloworlds import swarm-helloworld as a maven project in the workspace Right-click on swarm-helloworld/dockerfile > Run As > Docker Image Build Select Docker connection from CDK Use 172.30.80.211:5000/burr/swarm-helloworld as repo name The image deploys to the CDK docker connection/registry (See Docker Explorer) Right click on the deployed image > Deploy to OpenShift Select OpenShift Project (create a new one if necessary) =>Error Message : This docker image was not pulled in the selected Docker connection. Mapping ports will not be possible. The Finish Button stays disabled http://screencast.com/t/I2syMLXNcO8 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18316) Errors in project after import WildFly quickstarts (bundled jboss-ejb3-2_0.xsd)

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18316?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-18316: ------------------------------------- If entry "http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd" is removed from xsi:schemaLocation from original version of the file validation returns no errors and code assist looks working. Fixed file jboss-ejb3.xml should looks like this: {code:xml} <?xml version="1.1" encoding="UTF-8"?> <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:c="urn:clustering:1.0" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd" version="3.1" impl-version="2.0"> <assembly-descriptor> </assembly-descriptor> </jboss:ejb-jar> {code} Reason for this issue is that jboss-ejb3.xml sets schema location for "http://java.sun.com/xml/ns/javaee" namespace explicitly to http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd but has defined also namespace "http://www.jboss.com/xml/ns/javaee" which resolves to jboss-ejb3-2_0.xsd file from XML catalog. jboss-ejb3-2_0.xsd imports namespace "http://java.sun.com/xml/ns/javaee" which in XML catalog point to jboss-ejb3-spec-2_0.xsd file but this is the same namespace with defined schema location in jboss-ejb3.xml and resolved to http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd file (stored in XML catalog) instead to jboss-ejb3-spec-2_0.xsd file. I don't know if this is an Eclipse bug or expected scenario. Once schema location definition for "http://java.sun.com/xml/ns/javaee" namespace is removed from file jboss-ejb3.xml validation does not complain anymore. That is also reason why when jboss-ejb3-2_0.xsd is opened in JBDS there are no validation errors. jboss-ejb3-2_0.xsd has errors only in context of jboss-ejb3.xml validation > Errors in project after import WildFly quickstarts (bundled jboss-ejb3-2_0.xsd) > ------------------------------------------------------------------------------- > > Key: JBIDE-18316 > URL: https://issues.jboss.org/browse/JBIDE-18316 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.x > > > After importing all modules from https://github.com/wildfly/quickstart into JBDS 8.0.0.CR1b, a few projects have errors because of XML validation, such as: > {code} > Referenced file contains errors (jar:file:/Users/xcoulon/DevToolz/ide/jbossdevstudio800CR1b/studio/plugins/org.jboss.tools.as.catalog_3.0.0.CR1-v20140905-1648-B75.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > {code} -- 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