January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22816 at 1/4/17 10:11 AM: ------------------------------------------------------------------- [~jeffmaury] I cannot reproduce this. Can you please provide steps? was (Author: adietish): [~jeffmaury] I cannot reproduce this, but then I'm maybe missing something. Can you please provide steps or confirm this? > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.4.3.AM1 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22816 at 1/4/17 10:11 AM: ------------------------------------------------------------------- [~jeffmaury] I still cannot reproduce this. Can you please provide steps? was (Author: adietish): [~jeffmaury] I cannot reproduce this. Can you please provide steps? > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.4.3.AM1 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22816: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.4.3.AM1 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22816: ------------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.4.3.AM1 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21462) Project wizard: cancel button stops the job but wont cleanup resources

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21462?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21462: ------------------------------------- Issue Type: Enhancement (was: Bug) > Project wizard: cancel button stops the job but wont cleanup resources > ---------------------------------------------------------------------- > > Key: JBIDE-21462 > URL: https://issues.jboss.org/browse/JBIDE-21462 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149 > OS: Fedora 17 & MAC OS 10 > Reporter: Xia Zhao > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.3.AM1 > > > In project wizard, hitting the cancel button stops the job but wont cleanup the project (-resources) that were created. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21462) Project wizard: cancel button stops the job but wont cleanup resources

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21462?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21462: ------------------------------------- Description: In project wizard, hitting the cancel button stops the job but wont cleanup the project (-resources) that were created. Steps to Reproduce: 0. Install latest version of Jboss Developer Studio from https://devstudio.redhat.com/9.0/stable/updates/ 1. Login openshift with Jboss Developer Studio 2. Go to context menu New->Project 3. Enter project name "xiazhaotest", click on the Finish button 4. Click on the red cancel button while JBT is creating project, the wizard jumped back to the page on step3, but project "xiazhaotest" is in fact created Actual Result: Cancel button did not work in create project wizard of Jboss Developer Studio project "xiazhaotest" is in fact created Expected Result: Cancel button should work in create project wizard of Jboss Developer Studio project "xiazhaotest" should not be created was:In project wizard, hitting the cancel button stops the job but wont cleanup the project (-resources) that were created. > Project wizard: cancel button stops the job but wont cleanup resources > ---------------------------------------------------------------------- > > Key: JBIDE-21462 > URL: https://issues.jboss.org/browse/JBIDE-21462 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149 > OS: Fedora 17 & MAC OS 10 > Reporter: Xia Zhao > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.3.AM1 > > > In project wizard, hitting the cancel button stops the job but wont cleanup the project (-resources) that were created. > Steps to Reproduce: > 0. Install latest version of Jboss Developer Studio from https://devstudio.redhat.com/9.0/stable/updates/ > 1. Login openshift with Jboss Developer Studio > 2. Go to context menu New->Project > 3. Enter project name "xiazhaotest", click on the Finish button > 4. Click on the red cancel button while JBT is creating project, the wizard jumped back to the page on step3, but project "xiazhaotest" is in fact created > Actual Result: > Cancel button did not work in create project wizard of Jboss Developer Studio > project "xiazhaotest" is in fact created > Expected Result: > Cancel button should work in create project wizard of Jboss Developer Studio > project "xiazhaotest" should not be created -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23463: ------------------------------------------ PR was merged into opeshift-restclient-java/master. resolving. > Properties: Build pod has state of exit code 0 instead of correct status completed > ---------------------------------------------------------------------------------- > > Key: JBIDE-23463 > URL: https://issues.jboss.org/browse/JBIDE-23463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: build-pod-completed.png, exit-code-0.png > > > When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests. > steps: > # EXEC: create an application via a s2i template > # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view" > # EXEC: in Properties: select "Pods" tab. > # ASSERT: a build pod is appearing > # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods > Result: > The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise) > !exit-code-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23463: ------------------------------------- Attachment: build-pod-completed.png > Properties: Build pod has state of exit code 0 instead of correct status completed > ---------------------------------------------------------------------------------- > > Key: JBIDE-23463 > URL: https://issues.jboss.org/browse/JBIDE-23463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: build-pod-completed.png, exit-code-0.png > > > When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests. > steps: > # EXEC: create an application via a s2i template > # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view" > # EXEC: in Properties: select "Pods" tab. > # ASSERT: a build pod is appearing > # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods > Result: > The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise) > !exit-code-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23463: ------------------------------------------ [~scabanovich] works as expected, the build pod status is now "Completed". Thanks! !build-pod-completed.png! > Properties: Build pod has state of exit code 0 instead of correct status completed > ---------------------------------------------------------------------------------- > > Key: JBIDE-23463 > URL: https://issues.jboss.org/browse/JBIDE-23463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: exit-code-0.png > > > When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests. > steps: > # EXEC: create an application via a s2i template > # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view" > # EXEC: in Properties: select "Pods" tab. > # ASSERT: a build pod is appearing > # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods > Result: > The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise) > !exit-code-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4230) JBDS running on Fedora 25 with Wayland makes GUI rendering awful and return "No more handles" every time

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4230?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4230 at 1/4/17 8:42 AM: ---------------------------------------------------------- Latest snapshot build (devstudio-10.3.0.AM1-v20170103-1259-B6826-installer-standalone.jar) contains a new executable: {code}devstudio-wayland{code} [~rimolive] Can you try that and see if it works for you? Get latest installer from https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.product_maste... was (Author: nickboldt): Latest snapshot build (devstudio-10.3.0.AM1-v20170103-1259-B6826-installer-standalone.jar) contains a new executable: {code}devstudio-wayland{code} [~rimolive] Can you try that and see if it works for you? > JBDS running on Fedora 25 with Wayland makes GUI rendering awful and return "No more handles" every time > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-4230 > URL: https://issues.jboss.org/browse/JBDS-4230 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.2.0.GA > Environment: Fedora 25 with Wayland > Reporter: Ricardo Martinelli Oliveira > Assignee: Nick Boldt > Priority: Critical > Fix For: 10.3.0.AM1 > > > Workaround: Add GDK_BACKEND=x11 in devstudio.ini file to force use x11 to run JBDS. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2017