February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21100) start process of WildFly-8.2.0-Final never finish (Starting, Synchronized)

by carl zhang (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21100?page=com.atlassian.jira.plugi... ] carl zhang commented on JBIDE-21100: ------------------------------------ Sorry. I remembered I ever replied an email about this. I found the problem and fixed. The problem is that somehow the "Server Location" option in server's overview (double click the server name) is changed. I changed back. It works > start process of WildFly-8.2.0-Final never finish (Starting, Synchronized) > --------------------------------------------------------------------------- > > Key: JBIDE-21100 > URL: https://issues.jboss.org/browse/JBIDE-21100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: start process of WildFly-8.2.0-Final never finish (Starting, Synchronized) > Reporter: carl zhang > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > please refer to > https://developer.jboss.org/thread/265726?start=0&tstart=0 > refer to the picture of 28-Oct-2015 9:46 AM (layer 3) > In the left panel: WildFly 8.x is configured to connect to localhost > WildFly 8.x(1) is configured to connect to remote host (Linux) > The localhost cannot finish start process. WildFly 8.x(1) (remote) can. > What ports, or temp files, or anything else are checked when changing from starting to started state? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21700) Listen to pod redeployment after changing deployment configuration

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21700?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21700: --------------------------------------- Right now, relationships for this only can be walked from pod->rc(deployment)->dc via annotations pod: {{ "annotations": { "kubernetes.io/created-by": "{\"kind\":\"SerializedReference\",\"apiVersion\":\"v1\",\"reference\":{\"kind\":\"ReplicationController\",\"namespace\":\"hello-world\",\"name\":\"hello-openshift-2\",\"uid\":\"7b7dec8c-d4bf-11e5-b828-080027c5bfa9\",\"apiVersion\":\"v1\",\"resourceVersion\":\"41026\"}}\n", "openshift.io/deployment-config.latest-version": "2", "openshift.io/deployment-config.name": "hello-openshift", "openshift.io/deployment.name": "hello-openshift-2", "openshift.io/scc": "restricted" } }} rep controller: {{ "annotations": { "openshift.io/deployer-pod.name": "hello-openshift-2-deploy", "openshift.io/deployment-config.latest-version": "2", "openshift.io/deployment-config.name": "hello-openshift", "openshift.io/deployment.phase": "Complete", "openshift.io/deployment.replicas": "",}} We can either listen to the connection events directly, try to hook into the observable project cache, or try to write an event mechanism to encapsulate a deployment change to notify when the pod is available. > Listen to pod redeployment after changing deployment configuration > ------------------------------------------------------------------ > > Key: JBIDE-21700 > URL: https://issues.jboss.org/browse/JBIDE-21700 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Fix For: 4.3.1.CR1 > > > We need an easy way to detect a deployment configuration change triggered a new deployment and then be notified of its completion -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21681) Truncated lines seen on openshift login page

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21681?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21681: ----------------------------------------------- [~adietish], it may be that fixing JBIDE-21678 also fixes this issue, because when getting started link in New Connection wizard is not shown at wizard opening, the window is shaped to a smaller dimension than needed when link appears later during user input. As soon as link is shown at wizard opening, window size will be correct and checkbox truncating should not happen. > Truncated lines seen on openshift login page > -------------------------------------------- > > Key: JBIDE-21681 > URL: https://issues.jboss.org/browse/JBIDE-21681 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: OpenShift 3 Tools: 3.1.0.CR1-v20160212-1935-B177 > OS: Fedora 17 & 22 > Reporter: Xia Zhao > Priority: Minor > Labels: login_wizard, openshift_v3 > Fix For: 4.4.x > > Attachments: Screenshot from 2016-02-15 10-21-30.png > > > On the latest openshift login wizard inside JBT, the checkbox in the last line about whether you want to save credential is truncated. Please refer to the attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21701) Enable port forwarding on a given pod and a given debug port

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21701?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21701: ------------------------------------- We'll prolly need to add something like this to PortForwardingWizardModel (or refactored equivalent) {code} public int getLocalPort(String name) { if(!getPortForwarding()) { return -1; } Optional<PortPair> targetPort = ports.stream().filter(p -> p.getName().equals(name)).findFirst(); return targetPort.isPresent()? targetPort.get().getLocalPort():-1; } {code} > Enable port forwarding on a given pod and a given debug port > ------------------------------------------------------------ > > Key: JBIDE-21701 > URL: https://issues.jboss.org/browse/JBIDE-21701 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Fix For: 4.3.1.CR1 > > > Given a remote debug port, we need to ensure to programmatically enable port forwarding on a pod, return the matching local debug port (named debug). > The local port could be determined as the next available free port, or read from the server adapter's preferences. But that latter case would also require adding some UI to let a user set the local port. That could be done in a later iteration. > If port forwarding is already enabled on the remote pod, then the current local debug port should be returned -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21701) Enable port forwarding on a given pod and a given debug port

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21701?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-21701 at 2/16/16 12:43 PM: --------------------------------------------------------------- This will rely on org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardModel, which might need to be tweaked (or not) to satisfy our needs. was (Author: fbricon): This will rely on org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardModel, which might need to be tweak (or not) to satisfy our needs. > Enable port forwarding on a given pod and a given debug port > ------------------------------------------------------------ > > Key: JBIDE-21701 > URL: https://issues.jboss.org/browse/JBIDE-21701 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Fix For: 4.3.1.CR1 > > > Given a remote debug port, we need to ensure to programmatically enable port forwarding on a pod, return the matching local debug port (named debug). > The local port could be determined as the next available free port, or read from the server adapter's preferences. But that latter case would also require adding some UI to let a user set the local port. That could be done in a later iteration. > If port forwarding is already enabled on the remote pod, then the current local debug port should be returned -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21701) Enable port forwarding on a given pod and a given debug port

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21701?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21701: ------------------------------------- This will rely on PortForwardingWizardModel, which might need to be tweak (or not) to satisfy our needs > Enable port forwarding on a given pod and a given debug port > ------------------------------------------------------------ > > Key: JBIDE-21701 > URL: https://issues.jboss.org/browse/JBIDE-21701 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Fix For: 4.3.1.CR1 > > > Given a remote debug port, we need to ensure to programmatically enable port forwarding on a pod, return the matching local debug port (named debug). > The local port could be determined as the next available free port, or read from the server adapter's preferences. But that latter case would also require adding some UI to let a user set the local port. That could be done in a later iteration. > If port forwarding is already enabled on the remote pod, then the current local debug port should be returned -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21701) Enable port forwarding on a given pod and a given debug port

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21701?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-21701 at 2/16/16 12:42 PM: --------------------------------------------------------------- This will rely on org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardModel, which might need to be tweak (or not) to satisfy our needs. was (Author: fbricon): This will rely on PortForwardingWizardModel, which might need to be tweak (or not) to satisfy our needs > Enable port forwarding on a given pod and a given debug port > ------------------------------------------------------------ > > Key: JBIDE-21701 > URL: https://issues.jboss.org/browse/JBIDE-21701 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Fix For: 4.3.1.CR1 > > > Given a remote debug port, we need to ensure to programmatically enable port forwarding on a pod, return the matching local debug port (named debug). > The local port could be determined as the next available free port, or read from the server adapter's preferences. But that latter case would also require adding some UI to let a user set the local port. That could be done in a later iteration. > If port forwarding is already enabled on the remote pod, then the current local debug port should be returned -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21703) Server adapter wizard: pod deployment path is always default (/opt/app-root/src)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21703?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21703: ------------------------------------------ [~jcantrill] I see DeploymentResourceMapper always returning empty image stream tags. This is most likely caused by the changes you reported being introduced. Can you please help fixing? > Server adapter wizard: pod deployment path is always default (/opt/app-root/src) > -------------------------------------------------------------------------------- > > Key: JBIDE-21703 > URL: https://issues.jboss.org/browse/JBIDE-21703 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.1.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21703) Server adapter wizard: pod deployment path is always default (/opt/app-root/src)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21703?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21703: ------------------------------------- Fix Version/s: 4.3.1.CR1 > Server adapter wizard: pod deployment path is always default (/opt/app-root/src) > -------------------------------------------------------------------------------- > > Key: JBIDE-21703 > URL: https://issues.jboss.org/browse/JBIDE-21703 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.1.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21703) Server adapter wizard: pod deployment path is always default (/opt/app-root/src)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21703?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21703: ---------------------------------------- Assignee: Andre Dietisheim > Server adapter wizard: pod deployment path is always default (/opt/app-root/src) > -------------------------------------------------------------------------------- > > Key: JBIDE-21703 > URL: https://issues.jboss.org/browse/JBIDE-21703 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 2016