June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22773: ------------------------------------- Fix Version/s: 4.5.0.AM2 > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: server > Fix For: 4.5.0.AM2 > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 commented on JBIDE-22810: ------------------------------------------ [~jeffmaury] This wont happen for me on MacOS either. But since the majority of users is using Windows I consider this as a major annoyance, something that we *SHOULD* fix. > 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 > Environment: windows > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: explorer, openshift_v3, windows > Fix For: 4.5.0.AM2 > > 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 (v7.2.3#72005)

8 years, 10 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.5.0.AM2 (was: 4.5.0.AM1) > 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 > Environment: windows > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: explorer, openshift_v3, windows > Fix For: 4.5.0.AM2 > > 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 (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22869) Server adapter: Publishing code changes (via rsync) is buggy

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22869?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22869: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Server adapter: Publishing code changes (via rsync) is buggy > ------------------------------------------------------------ > > Key: JBIDE-22869 > URL: https://issues.jboss.org/browse/JBIDE-22869 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM2 > > > Across the platform we have quite a few serious issues when publishing code via the server editor. This shows us that_ > - we don't test well enough > - we lack time -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22969: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Make sure OpenShift Tools support proxies > ----------------------------------------- > > Key: JBIDE-22969 > URL: https://issues.jboss.org/browse/JBIDE-22969 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM2 > > Attachments: proxy_settings.png, proxy_settings_2.png > > > CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too. > If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side. > This issue covers: > - testing > - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests) > - fixing any problems we have in OpenShift tooling regarding proxy support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23771) Deploy Docker wizard: Pushing Image into Openshift registry fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23771?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23771: ------------------------------------------ This seems duplicate to JBIDE-23771, correct? > Deploy Docker wizard: Pushing Image into Openshift registry fails > ----------------------------------------------------------------- > > Key: JBIDE-23771 > URL: https://issues.jboss.org/browse/JBIDE-23771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Environment: oc version > oc v1.3.2 > kubernetes v1.3.0+52492b4 > features: Basic-Auth GSSAPI Kerberos SPNEGO > Server https://openshift.hughestech.co:8443 > openshift v1.3.2 > kubernetes v1.3.0+52492b4 > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.AM2 > > Attachments: FailedPush.png > > > See the issue created in upstream: https://github.com/openshift/origin/issues/12603 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23771) Deploy Docker wizard: Pushing Image into Openshift registry fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23771?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23771 at 6/6/17 4:13 AM: ------------------------------------------------------------------ [~dbocharov] This seems duplicate to JBIDE-23771, correct? was (Author: adietish): This seems duplicate to JBIDE-23771, correct? > Deploy Docker wizard: Pushing Image into Openshift registry fails > ----------------------------------------------------------------- > > Key: JBIDE-23771 > URL: https://issues.jboss.org/browse/JBIDE-23771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Environment: oc version > oc v1.3.2 > kubernetes v1.3.0+52492b4 > features: Basic-Auth GSSAPI Kerberos SPNEGO > Server https://openshift.hughestech.co:8443 > openshift v1.3.2 > kubernetes v1.3.0+52492b4 > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.AM2 > > Attachments: FailedPush.png > > > See the issue created in upstream: https://github.com/openshift/origin/issues/12603 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23771) Deploy Docker wizard: Pushing Image into Openshift registry fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23771?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23771: ------------------------------------- Summary: Deploy Docker wizard: Pushing Image into Openshift registry fails (was: Pushing Image into Openshift registry fails) > Deploy Docker wizard: Pushing Image into Openshift registry fails > ----------------------------------------------------------------- > > Key: JBIDE-23771 > URL: https://issues.jboss.org/browse/JBIDE-23771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Environment: oc version > oc v1.3.2 > kubernetes v1.3.0+52492b4 > features: Basic-Auth GSSAPI Kerberos SPNEGO > Server https://openshift.hughestech.co:8443 > openshift v1.3.2 > kubernetes v1.3.0+52492b4 > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.AM2 > > Attachments: FailedPush.png > > > See the issue created in upstream: https://github.com/openshift/origin/issues/12603 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23771) Deploy Docker wizard: Pushing Image into Openshift registry fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23771?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23771: ------------------------------------- Labels: deploy_docker_wizard openshift_v3 (was: ) > Deploy Docker wizard: Pushing Image into Openshift registry fails > ----------------------------------------------------------------- > > Key: JBIDE-23771 > URL: https://issues.jboss.org/browse/JBIDE-23771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Environment: oc version > oc v1.3.2 > kubernetes v1.3.0+52492b4 > features: Basic-Auth GSSAPI Kerberos SPNEGO > Server https://openshift.hughestech.co:8443 > openshift v1.3.2 > kubernetes v1.3.0+52492b4 > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.AM2 > > Attachments: FailedPush.png > > > See the issue created in upstream: https://github.com/openshift/origin/issues/12603 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23373) Application Wizard: Connection info could be visible on first wizard page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23373?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23373: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Application Wizard: Connection info could be visible on first wizard page > ------------------------------------------------------------------------- > > Key: JBIDE-23373 > URL: https://issues.jboss.org/browse/JBIDE-23373 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: application_wizard, openshift_v3 > Fix For: 4.5.x > > > In New OpenShift Application wizard on the first wizard page there is a project combo to choose a project for a new application. We are missing a connection info on this page so user don't see for which connection is an application created. It seems to be obvious, that it is for selected project from OpenShift Explorer (if view is visible = modal dialog is not on top of it at that moment) but in case of several connections with same project, it could cause troubles. > We could have it similar as it is in Deploy Docker Image wizard, where we display connection info. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 June 2017