September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4032) [cdk installer] weird errors during startup

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4032?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4032: -------------------------------- Fix Version/s: 10.2.0.AM1 > [cdk installer] weird errors during startup > ------------------------------------------- > > Key: JBDS-4032 > URL: https://issues.jboss.org/browse/JBDS-4032 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Rob Stryker > Fix For: 10.2.0.AM1 > > > After a previously-working environment, I installed build http://cdk-builds.usersys.redhat.com/builds/nightly/devsuite/2016-08-24_0... > Once I did that, I get teh following environment: > Administrator@LBDZ-20120704HU MINGW64 /c/DevelopmentSuite4/cdk/components/rhel/rhel-ose > $ vagrant -v > Vagrant 1.8.1 > Administrator@LBDZ-20120704HU MINGW64 /c/DevelopmentSuite4/cdk/components/rhel/rhel-ose > $ vagrant plugin list > landrush (1.1.2) > vagrant-registration (1.2.2) > - Version Constraint: 1.2.2 > vagrant-service-manager (1.1.0) > - Version Constraint: 1.1.0 > vagrant-share (1.1.5, system) > vagrant-sshfs (1.1.0) > - Version Constraint: 1.1.0 > Vagrant up had following log: https://paste.fedoraproject.org/418594/77989147/ > That log indicated I should read another log. The 2nd log is: https://paste.fedoraproject.org/418595/26780201/ > Removing the box and re-adding it did not seem to help. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-412) Need to improve as-you-type formatting for JSON editor [EBZ#501011]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-412: --------------------------------------- Summary: Need to improve as-you-type formatting for JSON editor [EBZ#501011] Key: ERT-412 URL: https://issues.jboss.org/browse/ERT-412 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Friendly Jira Robot Need to improve as-you-type formatting in JSON editor for curly braces: 1. "dependencies" : {|} 2. "dependencies" : { | } | - represents cursor position 1 - represents state before hitting Enter 2 - represents state after hitting Enter -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4032) [cdk installer] weird errors during startup

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4032?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4032: ------------------------------------- What was installed in previously working environment? I assume you had DevSuite 1.0.0.GA based install: * Vagrant 1.7.4; * CDK 2.1; * Cygwin 2.5.2. * Virtualbox 5.0.8 Then uninstalled vagrant, virtual box and used devsuite installer. Is that correct scenario? > [cdk installer] weird errors during startup > ------------------------------------------- > > Key: JBDS-4032 > URL: https://issues.jboss.org/browse/JBDS-4032 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Rob Stryker > Fix For: 10.2.0.AM1 > > > After a previously-working environment, I installed build http://cdk-builds.usersys.redhat.com/builds/nightly/devsuite/2016-08-24_0... > Once I did that, I get teh following environment: > Administrator@LBDZ-20120704HU MINGW64 /c/DevelopmentSuite4/cdk/components/rhel/rhel-ose > $ vagrant -v > Vagrant 1.8.1 > Administrator@LBDZ-20120704HU MINGW64 /c/DevelopmentSuite4/cdk/components/rhel/rhel-ose > $ vagrant plugin list > landrush (1.1.2) > vagrant-registration (1.2.2) > - Version Constraint: 1.2.2 > vagrant-service-manager (1.1.0) > - Version Constraint: 1.1.0 > vagrant-share (1.1.5, system) > vagrant-sshfs (1.1.0) > - Version Constraint: 1.1.0 > Vagrant up had following log: https://paste.fedoraproject.org/418594/77989147/ > That log indicated I should read another log. The 2nd log is: https://paste.fedoraproject.org/418595/26780201/ > Removing the box and re-adding it did not seem to help. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23141) Multi delete certificates should be possible

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23141?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23141: ------------------------------- Labels: openshift openshift_v3 (was: ) > Multi delete certificates should be possible > -------------------------------------------- > > Key: JBIDE-23141 > URL: https://issues.jboss.org/browse/JBIDE-23141 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > > It should be possible to delete several certificates in a single UI action -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23141) Multi delete certificates should be possible

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-23141: ---------------------------------- Summary: Multi delete certificates should be possible Key: JBIDE-23141 URL: https://issues.jboss.org/browse/JBIDE-23141 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.1.Final Reporter: Jeff MAURY Fix For: 4.4.2.AM2 It should be possible to delete several certificates in a single UI action -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23015) Creating a route should have a default port

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23015: ----------------------------------- Sprint: devex #119 August 2016, devex #120 September 2016 (was: devex #119 August 2016) > Creating a route should have a default port > ------------------------------------------- > > Key: JBIDE-23015 > URL: https://issues.jboss.org/browse/JBIDE-23015 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff MAURY > Fix For: 4.4.2.AM1 > > > When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail. > There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others. > The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation) > To reproduce: > - git clone https://github.com/redhat-helloworld-msa/aloha > - mvn package > - build docker image from Dockerfile, to CDK docker connection > - deploy docker image to openshift -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22239: ----------------------------------- Sprint: devex #119 August 2016, devex #120 September 2016 (was: devex #119 August 2016) > Allow a user to choose to permanently update their desired replicas for their deployment > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22239 > URL: https://issues.jboss.org/browse/JBIDE-22239 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Viacheslav Kabanovich > Labels: openshift_v3 > Fix For: 4.5.0.AM1 > > > When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest: > * Adding a custom dialog in the "..to.." option > * Update to use a spinner > * Add a checkbox to 'make the change perminent' > * If checkbox=true, you should only need to update the dc if it has a configchange trigger. > * Optionally show checkbox if unable to determine the dc associated with the deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22805) Add Scale... menus on Pod resources

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22805?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22805: ----------------------------------- Sprint: devex #119 August 2016, devex #120 September 2016 (was: devex #119 August 2016) > Add Scale... menus on Pod resources > ----------------------------------- > > Key: JBIDE-22805 > URL: https://issues.jboss.org/browse/JBIDE-22805 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.4.1.Final > > > I'm regularly confused/frustrated to not find the Scale... menus on the running pods. Each time I need to slap myself in the face to remind me I need to go to the Service level. > I think it'd be more intuitive if the scale menus were present on the running pods (not on the build ones). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22810: ----------------------------------- Sprint: devex #119 August 2016, devex #120 September 2016 (was: devex #119 August 2016) > OpenShift Explorer: empty at start > ---------------------------------- > > Key: JBIDE-22810 > URL: https://issues.jboss.org/browse/JBIDE-22810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.4.2.AM1 > > Attachments: EmptyViewAtStart.png > > > When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections. > I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23006) OkHttp reports leaked connections

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23006?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23006: ----------------------------------- Sprint: devex #119 August 2016, devex #120 September 2016 (was: devex #119 August 2016) > OkHttp reports leaked connections > --------------------------------- > > Key: JBIDE-23006 > URL: https://issues.jboss.org/browse/JBIDE-23006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff MAURY > Fix For: 4.4.2.AM1 > > > After connecting to an OpenShift instance, some warnings show up in the logs eventually: > {noformat} > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > {noformat} > I haven't figured out exactly what steps cause these yet. -- 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