August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23053) Central news info does not seem uptodate

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23053?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23053: ------------------------------------ Do we have a limitation in the carousel because I can see only the first 5 items when http://feeds.feedburner.com/jbossbuzz has 10 entries ? > Central news info does not seem uptodate > ---------------------------------------- > > Key: JBIDE-23053 > URL: https://issues.jboss.org/browse/JBIDE-23053 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.1.AM3 > Reporter: Jeff MAURY > Assignee: Fred Bricon > Fix For: 4.4.1.Final > > > The RedHat Central view does not seem to display uptodate news: latest info is from June 2016 which is almost 3 months old -- 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 Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22239: --------------------------------------- Based on the original impl of how we support scaling I would expect: * scale deployment config - updates DC and RC * scale deployment/replication controller - updates only the rc This would imply further changes to the DC will over-write any changes to the RC. But, this PR/issue may no longer be valid since the rework I added for #JBIDE-23030 which changes our scaling workflow to utilize the 'scale' endpoint over direct edit of a DC. > 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.4.1.Final > > > 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-22243) Properties: "Refresh" has no effect

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22243: --------------------------------------- [~fbricon] [~adietish] You might consider re-assigning this based on the priority as I will not be addressing it anytime soon, as far as I know. > Properties: "Refresh" has no effect > ----------------------------------- > > Key: JBIDE-22243 > URL: https://issues.jboss.org/browse/JBIDE-22243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Fix For: 4.4.2.AM1 > > Attachments: refreshing-wont-help.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23005) Server Adapter: Stuck on creating/publishing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23005: ------------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Server Adapter: Stuck on creating/publishing > -------------------------------------------- > > Key: JBIDE-23005 > URL: https://issues.jboss.org/browse/JBIDE-23005 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.4.2.AM1 > > Attachments: stucked_server_adapter > > > When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22319) Make OpenshiftServer implement IConnectionFacade

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22319?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22319: ------------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Make OpenshiftServer implement IConnectionFacade > ------------------------------------------------ > > Key: JBIDE-22319 > URL: https://issues.jboss.org/browse/JBIDE-22319 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Assignee: Fred Bricon > Fix For: 4.4.2.AM1 > > > Add support for having a jmx conection via JBoss remoting to OpenShiftServer. > * need to add jmx client library > * find out the correct url > * configure deployment config with necessary env, ports, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22860) Application Wizard: Improve layout for templates

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22860?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22860: ------------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Application Wizard: Improve layout for templates > ------------------------------------------------ > > Key: JBIDE-22860 > URL: https://issues.jboss.org/browse/JBIDE-22860 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.2.AM1 > > > In the New OpenShift Application wizard we have 2 tabs for a decision on what should a new application be based. One for server-template-based application (either from templates or builder images) and one for "Local template". Problem with local template is that it supports usage of URL templates - I can provide an URL of a template. This is not really local template. I think we should rename "Local template" tab to "Custom template" or something what would suggest usage of URLs as well as templates from local file system. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22860) Application Wizard: Improve layout for templates

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22860?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22860: ------------------------------------- Sprint: devex #120 September 2016 (was: devex #119 August 2016) > Application Wizard: Improve layout for templates > ------------------------------------------------ > > Key: JBIDE-22860 > URL: https://issues.jboss.org/browse/JBIDE-22860 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.2.AM1 > > > In the New OpenShift Application wizard we have 2 tabs for a decision on what should a new application be based. One for server-template-based application (either from templates or builder images) and one for "Local template". Problem with local template is that it supports usage of URL templates - I can provide an URL of a template. This is not really local template. I think we should rename "Local template" tab to "Custom template" or something what would suggest usage of URLs as well as templates from local file system. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22914) OpenShift Deployment: Deploy latest does not work correctly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22914?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22914: ------------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > OpenShift Deployment: Deploy latest does not work correctly > ----------------------------------------------------------- > > Key: JBIDE-22914 > URL: https://issues.jboss.org/browse/JBIDE-22914 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.2.AM1 > > > When I have an application where no replication controller is yet and I want to deploy latest, I get following error: > {code} > Unable to perform a deployment for config hello-openshift > com.openshift.restclient.NotFoundException: replicationcontrollers "hello-openshift-0" not found > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:105) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:59) > at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163) > at okhttp3.RealCall.execute(RealCall.java:57) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:200) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:181) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:269) > at com.openshift.internal.restclient.capability.resources.DeployCapability.deploy(DeployCapability.java:59) > at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1$1.visit(TriggerDeploymentHandler.java:90) > at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1$1.visit(TriggerDeploymentHandler.java:1) > at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91) > at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1.doRun(TriggerDeploymentHandler.java:85) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > This is wrong, because it is trying to "deploy latest replication controller" instead of deploying latest deployment configuration (as it works e.g. from oc binary - deployment uses latest deployment configuration not replication controller which could be understood as instance of deployment configuration). Therefore if there is no replication controller and I click Deploy Latest in context menu of a service in OpenShift Explorer view or in context menu of a deployment configuration in properties view, I get the error. -- 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22810: ------------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > 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-22915) Deploy Docker Image: Replication controller is not created for some images

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22915?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22915: ------------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Deploy Docker Image: Replication controller is not created for some images > -------------------------------------------------------------------------- > > Key: JBIDE-22915 > URL: https://issues.jboss.org/browse/JBIDE-22915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM1 > > > When I am trying to deploy docker image docker.io/openshift/hello-openshift:v1.2.1 from context menu of the image in Docker Explorer it does not trigger a new replication controller and thus an application pod is not spinned up. When working from oc binary, replication controller is created successfully ("oc new-app docker.io/openshift/hello-openshift:v1.2.1") -- 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 August 2016