February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23819) Preferences: Unable to determine oc 1.4.1 version

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23819?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23819: ------------------------------------- Summary: Preferences: Unable to determine oc 1.4.1 version (was: Unable to determine oc 1.4.1 version) > Preferences: Unable to determine oc 1.4.1 version > ------------------------------------------------- > > Key: JBIDE-23819 > URL: https://issues.jboss.org/browse/JBIDE-23819 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: Devstudio 10.3.0.AM2, oc client v1.4.1 downloaded from https://github.com/openshift/origin/releases/tag/v1.4.1 > Reporter: Radim Hopp > Assignee: Andre Dietisheim > Priority: Critical > Labels: oc_binary, openshift_v3, preferences > Fix For: 4.4.3.Final > > Attachments: binary-not-oc.png, oc-14-not-recognized.png > > > Selecting oc version 1.4.1 [1] in OpenShift 3 preferences dialog results in "Could not determine your OpenShift client version". > [1] - https://github.com/openshift/origin/releases/tag/v1.4.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23819) Preferences: Unable to determine oc 1.4.1 version

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23819?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23819: ------------------------------------- Labels: oc_binary openshift_v3 preferences (was: oc_binary openshift_v3) > Preferences: Unable to determine oc 1.4.1 version > ------------------------------------------------- > > Key: JBIDE-23819 > URL: https://issues.jboss.org/browse/JBIDE-23819 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: Devstudio 10.3.0.AM2, oc client v1.4.1 downloaded from https://github.com/openshift/origin/releases/tag/v1.4.1 > Reporter: Radim Hopp > Assignee: Andre Dietisheim > Priority: Critical > Labels: oc_binary, openshift_v3, preferences > Fix For: 4.4.3.Final > > Attachments: binary-not-oc.png, oc-14-not-recognized.png > > > Selecting oc version 1.4.1 [1] in OpenShift 3 preferences dialog results in "Could not determine your OpenShift client version". > [1] - https://github.com/openshift/origin/releases/tag/v1.4.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23819) Unable to determine oc 1.4.1 version

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23819?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23819: ------------------------------------- Summary: Unable to determine oc 1.4.1 version (was: Unable to determine oc 1.4.0 version) > Unable to determine oc 1.4.1 version > ------------------------------------ > > Key: JBIDE-23819 > URL: https://issues.jboss.org/browse/JBIDE-23819 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: Devstudio 10.3.0.AM2, oc client v1.4.1 downloaded from https://github.com/openshift/origin/releases/tag/v1.4.1 > Reporter: Radim Hopp > Assignee: Andre Dietisheim > Priority: Critical > Labels: oc_binary, openshift_v3 > Fix For: 4.4.3.Final > > Attachments: binary-not-oc.png, oc-14-not-recognized.png > > > Selecting oc version 1.4.1 [1] in OpenShift 3 preferences dialog results in "Could not determine your OpenShift client version". > [1] - https://github.com/openshift/origin/releases/tag/v1.4.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23817) Scaling: is not working with OpenShift 3.4 (CDK 2.4)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23817?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23817: ------------------------------------- Sprint: devex #127 February 2017 > Scaling: is not working with OpenShift 3.4 (CDK 2.4) > ---------------------------------------------------- > > Key: JBIDE-23817 > URL: https://issues.jboss.org/browse/JBIDE-23817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: CDK 2.4 > Devstudio 10.3.0.AM2 > Reporter: Radim Hopp > Priority: Critical > Labels: openshift_v3 > Fix For: 4.4.3.Final > > Attachments: Spectacle.yJ3971.png > > > Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now). > When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again. > This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23817) Scaling: is not working with OpenShift 3.4 (CDK 2.4)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23817?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23817: ------------------------------------------ [~rhopp] is scaling working in Web-UI or oc? > Scaling: is not working with OpenShift 3.4 (CDK 2.4) > ---------------------------------------------------- > > Key: JBIDE-23817 > URL: https://issues.jboss.org/browse/JBIDE-23817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: CDK 2.4 > Devstudio 10.3.0.AM2 > Reporter: Radim Hopp > Priority: Critical > Labels: openshift_v3 > Fix For: 4.4.3.Final > > Attachments: Spectacle.yJ3971.png > > > Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now). > When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again. > This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23817) Scaling: is not working with OpenShift 3.4 (CDK 2.4)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23817?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23817: ------------------------------------------ [~jeffmaury] [~bdshadow] this seems like a critical bug. Can anoyone of you look into it, please? > Scaling: is not working with OpenShift 3.4 (CDK 2.4) > ---------------------------------------------------- > > Key: JBIDE-23817 > URL: https://issues.jboss.org/browse/JBIDE-23817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: CDK 2.4 > Devstudio 10.3.0.AM2 > Reporter: Radim Hopp > Priority: Critical > Labels: openshift_v3 > Fix For: 4.4.3.Final > > Attachments: Spectacle.yJ3971.png > > > Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now). > When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again. > This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23817) Scaling: is not working with OpenShift 3.4 (CDK 2.4)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23817?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23817: ------------------------------------- Labels: openshift_v3 (was: ) > Scaling: is not working with OpenShift 3.4 (CDK 2.4) > ---------------------------------------------------- > > Key: JBIDE-23817 > URL: https://issues.jboss.org/browse/JBIDE-23817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: CDK 2.4 > Devstudio 10.3.0.AM2 > Reporter: Radim Hopp > Priority: Critical > Labels: openshift_v3 > Fix For: 4.4.3.Final > > Attachments: Spectacle.yJ3971.png > > > Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now). > When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again. > This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23817) Scaling is not working with OpenShift 3.4 (CDK 2.4)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23817?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23817: ------------------------------------- Fix Version/s: 4.4.3.Final > Scaling is not working with OpenShift 3.4 (CDK 2.4) > --------------------------------------------------- > > Key: JBIDE-23817 > URL: https://issues.jboss.org/browse/JBIDE-23817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: CDK 2.4 > Devstudio 10.3.0.AM2 > Reporter: Radim Hopp > Priority: Critical > Fix For: 4.4.3.Final > > Attachments: Spectacle.yJ3971.png > > > Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now). > When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again. > This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23817) Scaling: is not working with OpenShift 3.4 (CDK 2.4)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23817?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23817: ------------------------------------- Summary: Scaling: is not working with OpenShift 3.4 (CDK 2.4) (was: Scaling is not working with OpenShift 3.4 (CDK 2.4)) > Scaling: is not working with OpenShift 3.4 (CDK 2.4) > ---------------------------------------------------- > > Key: JBIDE-23817 > URL: https://issues.jboss.org/browse/JBIDE-23817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: CDK 2.4 > Devstudio 10.3.0.AM2 > Reporter: Radim Hopp > Priority: Critical > Fix For: 4.4.3.Final > > Attachments: Spectacle.yJ3971.png > > > Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now). > When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again. > This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23422: ------------------------------------------ [~ibuziuk] thx for the pointers. I found the launcher code for our nodejs plugin but was missing where the effective connection was implemented. >From what I was told by [~rcernich] the faced the same problem in Arquillian and they solved it by adding keep-alive pings that arquillian is sending to the server (preventing it from closing the connection after 1 minute). For us to be able to do such a thing we'd have to be able to customise the code (in chromium?) that is handling the connection. I bet that there's no such ability. Correct? > Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23422 > URL: https://issues.jboss.org/browse/JBIDE-23422 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.2.AM2 > Environment: windows 10 > Fedora 24 > Reporter: Ilya Buziuk > Assignee: Andre Dietisheim > Priority: Critical > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.4.3.Final > > > We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout. > The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)). > We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 February 2017