July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22766) Cannot load discovery directory

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22766?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22766: -------------------------------- Story Points: 2 Sprint: devex #117 July 2016 > Cannot load discovery directory > ------------------------------- > > Key: JBIDE-22766 > URL: https://issues.jboss.org/browse/JBIDE-22766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 4.4.1.AM2 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.1.AM2 > > > Central is trying to access the following directories on the update site: > - https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... for devstudio > - http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-dis... for JBT > These directories don't exist on the update sites, so central software/update cannot load. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22766) Cannot load discovery directory

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22766?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-22766: --------------------------------- Fix Version/s: 4.4.1.AM2 > Cannot load discovery directory > ------------------------------- > > Key: JBIDE-22766 > URL: https://issues.jboss.org/browse/JBIDE-22766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 4.4.1.AM2 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.1.AM2 > > > Central is trying to access the following directories on the update site: > - https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... for devstudio > - http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-dis... for JBT > These directories don't exist on the update sites, so central software/update cannot load. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22593) New application wizard: preselect v3 connection that I most recently used

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22593?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22593: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > New application wizard: preselect v3 connection that I most recently used > ------------------------------------------------------------------------- > > Key: JBIDE-22593 > URL: https://issues.jboss.org/browse/JBIDE-22593 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Labels: application_wizard, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.4.1.AM3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > # ASSERT: make sure that you have used a v3 connection (ex. import an application from your OpenShift server to your workspace) > # EXEC: launch openshift wizard via File->New->OpenShift Application > # ASSERT: connection dialog shows up > Result: > Connection dialog shows up with <New Connection> and connection type "OpenShift 2" pre-selected. > Expected result: > Connection dialog has my v3 connection preselected, that I recently used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22684) CDK server adapter: Show In > OpenShift Explorer causes login prompts to show up

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22684?page=com.atlassian.jira.plugi... ] Dmitry Bocharov commented on JBIDE-22684: ----------------------------------------- I suppose, yes. PR fixes the behavior, that the dialogs appear for all connections. > CDK server adapter: Show In > OpenShift Explorer causes login prompts to show up > -------------------------------------------------------------------------------- > > Key: JBIDE-22684 > URL: https://issues.jboss.org/browse/JBIDE-22684 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Fix For: 4.4.1.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22684) CDK server adapter: Show In > OpenShift Explorer causes login prompts to show up

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22684?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22684: ------------------------------------ I tested the PR but still got a dialog asking for a password. My conf (in the order of apparence in Openshift explorer) * admin connection without password saved to CDK * openshift-dev connection with password saved to CDK The dialog ask me to provide password for admin. Is it the expected behavior ? > CDK server adapter: Show In > OpenShift Explorer causes login prompts to show up > -------------------------------------------------------------------------------- > > Key: JBIDE-22684 > URL: https://issues.jboss.org/browse/JBIDE-22684 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Fix For: 4.4.1.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22650) When starting an OS3 server adapter from scratch, error is reported although connection can be established

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22650?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22650: ------------------------------------------ I just tried to reproduce this in latest master and it doesnt happen for me (without the patch applied). > When starting an OS3 server adapter from scratch, error is reported although connection can be established > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22650 > URL: https://issues.jboss.org/browse/JBIDE-22650 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Fix For: 4.4.1.AM2 > > Attachments: screenshot-1.png > > > ASSERT: create an OS3 connection without password saved > ASSERT: create an OS3 server adapter > EXEC: restart Eclipse > EXEC: start the OS3 server adapter and give correct password > ASSERT: error is reported [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22641) When an Openshift connection is deleted, the secure entries are not removed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22641?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22641: ------------------------------------------ thx, tested it, works for me! applied to master > When an Openshift connection is deleted, the secure entries are not removed > --------------------------------------------------------------------------- > > Key: JBIDE-22641 > URL: https://issues.jboss.org/browse/JBIDE-22641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Dmitry Bocharov > Priority: Critical > Labels: connection, openshift_v3, secure_storage > Fix For: 4.4.1.AM2 > > > When a token or password is saved in secure storage for an Openshift connection, then deleting this connection will not remove this data from secure storage. Then creating a new connection with the same address will reuse this infos. This is a security breach -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22767) Deploy Docker Wizard: Create image stream contains wrong tags in some cases

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22767?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22767: ---------------------------------- Description: In Deploy Image to OpenShift wizard when I am trying to deploy image docker.io/openshift/hello-openshift:v1.2.1, the image stream created contains some weird tags. If I deploy this image via oc binary then a created image stream contains correct tag v1.2.1, but from tooling it contains more tags and none of them is the desired one (there are 0.4, 0.5, latest...). Some behaviour is also common for normal usage. When deploying a image with tag latest, there are also defined other tags. OC binary creates IS only with the one tag, the one which was passed as "partial" argument when deploying an image. Consequences of this issue are no pods created once the deploy image to OpenShift is finished. User has to manually trigger Deploy Latest from context menu of a deployment configuration to spin up an application pod. was: In Deploy Image to OpenShift wizard when I am trying to deploy image docker.io/openshift/hello-openshift:v1.2.1, the image stream created contains some weird tags. If I deploy this image via oc binary then a created image stream contains correct tag v1.2.1, but from tooling it contains more tags and none of them is the desired one (there are 0.4, 0.5, latest...). Some behaviour is also common for normal usage. When deploying a image with tag latest, there are also defined other tags. OC binary creates IS only with the one tag, the one which was passed as "partial" argument when deploying an image. > Deploy Docker Wizard: Create image stream contains wrong tags in some cases > --------------------------------------------------------------------------- > > Key: JBIDE-22767 > URL: https://issues.jboss.org/browse/JBIDE-22767 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > > In Deploy Image to OpenShift wizard when I am trying to deploy image docker.io/openshift/hello-openshift:v1.2.1, the image stream created contains some weird tags. If I deploy this image via oc binary then a created image stream contains correct tag v1.2.1, but from tooling it contains more tags and none of them is the desired one (there are 0.4, 0.5, latest...). > Some behaviour is also common for normal usage. When deploying a image with tag latest, there are also defined other tags. OC binary creates IS only with the one tag, the one which was passed as "partial" argument when deploying an image. > Consequences of this issue are no pods created once the deploy image to OpenShift is finished. User has to manually trigger Deploy Latest from context menu of a deployment configuration to spin up an application pod. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22767) Deploy Docker Wizard: Create image stream contains wrong tags in some cases

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22767?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22767: ---------------------------------- Labels: docker openshift_v3 (was: ) > Deploy Docker Wizard: Create image stream contains wrong tags in some cases > --------------------------------------------------------------------------- > > Key: JBIDE-22767 > URL: https://issues.jboss.org/browse/JBIDE-22767 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > > In Deploy Image to OpenShift wizard when I am trying to deploy image docker.io/openshift/hello-openshift:v1.2.1, the image stream created contains some weird tags. If I deploy this image via oc binary then a created image stream contains correct tag v1.2.1, but from tooling it contains more tags and none of them is the desired one (there are 0.4, 0.5, latest...). > Some behaviour is also common for normal usage. When deploying a image with tag latest, there are also defined other tags. OC binary creates IS only with the one tag, the one which was passed as "partial" argument when deploying an image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22767) Deploy Docker Wizard: Create image stream contains wrong tags in some cases

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22767: ------------------------------------- Summary: Deploy Docker Wizard: Create image stream contains wrong tags in some cases Key: JBIDE-22767 URL: https://issues.jboss.org/browse/JBIDE-22767 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.1.AM2 Reporter: Marián Labuda In Deploy Image to OpenShift wizard when I am trying to deploy image docker.io/openshift/hello-openshift:v1.2.1, the image stream created contains some weird tags. If I deploy this image via oc binary then a created image stream contains correct tag v1.2.1, but from tooling it contains more tags and none of them is the desired one (there are 0.4, 0.5, latest...). Some behaviour is also common for normal usage. When deploying a image with tag latest, there are also defined other tags. OC binary creates IS only with the one tag, the one which was passed as "partial" argument when deploying an image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 July 2016