September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3890) Devstudio installation takes a long, long time

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3890?page=com.atlassian.jira.plugin.... ] Alexey Kazakov closed JBDS-3890. -------------------------------- Fix Version/s: 10.1.0.GA (was: 10.x) Resolution: Cannot Reproduce Bug Thanks for verification. Closing. > Devstudio installation takes a long, long time > ---------------------------------------------- > > Key: JBDS-3890 > URL: https://issues.jboss.org/browse/JBDS-3890 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.0.0.Alpha1 > Environment: Fedora 22 x64 > OpenJDK 1.8.0_91 > jboss-devstudio-10.0.0.Alpha1-v20160517-0518-B5370-installer-standalone.jar > Reporter: Jan Richter > Priority: Critical > Fix For: 10.1.0.GA > > Attachments: install.png, res.png > > > Some actual data here: > - Alpha1 (staged) build took 2:05 to install on my machine > - Alpha1 nightly (B5370) took 5:15 to install > Around the minute mark the installation just freezes in this state: > !install.png|thumbnail! > Meanwhile the trace says: > {noformat} > Committing the provisioning operation. > Operation completed in 275702 ms. > {noformat} > That is quite a long time it spent doing that operation. > Some jstack info can be found here: > http://pastebin.test.redhat.com/374700 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22626: ------------------------------------ You did not catch me. If you compare your 2 payloads, then the update as 2 containers whereas the original has only 1 > Updating deployed docker image on OpenShift does not work > --------------------------------------------------------- > > Key: JBIDE-22626 > URL: https://issues.jboss.org/browse/JBIDE-22626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.1.Final > > > In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok. > But if user deploys image with tag e.g. :0.8 to OpenShift, resources are created for this specific tag. When I am trying to Deploy to OS image with tag :0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag :0.8 and thus new deployment is not done. > Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it. > In order to add this version tag after semicolon, right-click on the image -> Add tag -> Re-type namespace/imagename + add ":0.8" e.g. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-22626: ------------------------------------------ [~jeffmaury] [~jcantrill], great thanks for your replies! [~jeffmaury] no, i'm not adding a new container. I'm calling DefaultClient.update() and as a proof the request is a PUT request: see my comment: {method=PUT, url=https://10.1.2.2:8443/oapi/v1/namespaces/sample-project/deploymentconfigs/aloha, tag=null} [~jcantrill] yes, _refresh_ is working exactly like this - returns the latest version of the resource to later be updated. And this is the thing i'm doing. Firstly i get DC from connection, see my example for servceaboce: _stubService_ method, where _findServiceFor(parameters.getProject().getName())_ exactly calls _connection.refresh()_ and then i set new parameters for them (e.g. from deploy wizard) and try to call _connection.update()_. And it works for Route, ImageStream(can see added new tag in web console), but doesn't work for DC. I'll try to update the line to which you provided the link. About the second container, yes, that's really strange. I'll try to work on it again to replicate. > Updating deployed docker image on OpenShift does not work > --------------------------------------------------------- > > Key: JBIDE-22626 > URL: https://issues.jboss.org/browse/JBIDE-22626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.1.Final > > > In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok. > But if user deploys image with tag e.g. :0.8 to OpenShift, resources are created for this specific tag. When I am trying to Deploy to OS image with tag :0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag :0.8 and thus new deployment is not done. > Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it. > In order to add this version tag after semicolon, right-click on the image -> Add tag -> Re-type namespace/imagename + add ":0.8" e.g. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23116) Docker New and Noteworthy for 4.4.1.Final

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23116?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-23116. --------------------------------- PR is merged. > Docker New and Noteworthy for 4.4.1.Final > ----------------------------------------- > > Key: JBIDE-23116 > URL: https://issues.jboss.org/browse/JBIDE-23116 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Jeff MAURY > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.1.Final > > > If no news for 4.4.1.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "page-include-previous: false" attribute to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-868) Create a test for a standalone devstudio-is installer

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-868: --------------------------------------- Summary: Create a test for a standalone devstudio-is installer Key: JBTIS-868 URL: https://issues.jboss.org/browse/JBTIS-868 Project: JBoss Tools Integration Stack Issue Type: Bug Components: QE Affects Versions: 4.3.1.Final Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky Priority: Critical Create a test for a standalone devstudio-is installer -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-867) Create test for updatable properties

by Matej Kralik (JIRA)

Matej Kralik created JBTIS-867: ---------------------------------- Summary: Create test for updatable properties Key: JBTIS-867 URL: https://issues.jboss.org/browse/JBTIS-867 Project: JBoss Tools Integration Stack Issue Type: Enhancement Components: QE, teiid Affects Versions: 4.3.1.Final Reporter: Matej Kralik Assignee: Matej Kralik Create the test for JBDVPL-350 (Add option in JDBC importer to set all "updatable" table properties to true/false) and test if VDB works correctly -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23145) Rename class variables in org.jboss.tools.hibernate.runtime.spi.ServiceLookup and cache the default service

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23145?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23145: ------------------------------ Sprint: devex #120 September 2016 > Rename class variables in org.jboss.tools.hibernate.runtime.spi.ServiceLookup and cache the default service > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23145 > URL: https://issues.jboss.org/browse/JBIDE-23145 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23145) Rename class variables in org.jboss.tools.hibernate.runtime.spi.ServiceLookup and cache the default service

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23145?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-23145: --------------------------------- Assignee: Koen Aers > Rename class variables in org.jboss.tools.hibernate.runtime.spi.ServiceLookup and cache the default service > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23145 > URL: https://issues.jboss.org/browse/JBIDE-23145 > Project: Tools (JBoss Tools) > Issue Type: Task > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23145) Rename class variables in org.jboss.tools.hibernate.runtime.spi.ServiceLookup and cache the default service

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23145?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23145: ------------------------------ Fix Version/s: 4.4.2.AM1 > Rename class variables in org.jboss.tools.hibernate.runtime.spi.ServiceLookup and cache the default service > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23145 > URL: https://issues.jboss.org/browse/JBIDE-23145 > Project: Tools (JBoss Tools) > Issue Type: Task > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22626: ------------------------------------ >From the payload that you showed, it seems you are adding a new container but it has the same name as the previous. Why don't you update the existing one ? > Updating deployed docker image on OpenShift does not work > --------------------------------------------------------- > > Key: JBIDE-22626 > URL: https://issues.jboss.org/browse/JBIDE-22626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.1.Final > > > In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok. > But if user deploys image with tag e.g. :0.8 to OpenShift, resources are created for this specific tag. When I am trying to Deploy to OS image with tag :0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag :0.8 and thus new deployment is not done. > Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it. > In order to add this version tag after semicolon, right-click on the image -> Add tag -> Re-type namespace/imagename + add ":0.8" e.g. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

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