June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22644) Unable to perform oc binary actions because of insecure flag

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22644?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22644: --------------------------------------- Can be fixed with: ProcessBuilder builder = new ProcessBuilder(args); builder.environment().clear(); in AbstractOpenshiftBinaryCapability in the openshift-restclient > Unable to perform oc binary actions because of insecure flag > ------------------------------------------------------------ > > Key: JBIDE-22644 > URL: https://issues.jboss.org/browse/JBIDE-22644 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff Cantrill > > Trying to retrieve pod logs or any oc binary action results in warning of: > specifying a root certificates file with the insecure flag is not allowed > Per deads openshift dev "...it means that your kubeconfig file has a CA set, but you're trying to connect insecurely" > Persumably this requires us to make sure KUBECONFIG env var is not set when executing oc binary commands. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22645) Pre-select OpenShift 3 in New OpenShift Connection wizard

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-22645: -------------------------------------- Summary: Pre-select OpenShift 3 in New OpenShift Connection wizard Key: JBIDE-22645 URL: https://issues.jboss.org/browse/JBIDE-22645 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Reporter: Alexey Kazakov Currently OS 2 is selected by default. We should pre-select OS 3 instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22644) Unable to perform oc binary actions because of insecure flag

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-22644: ------------------------------------- Summary: Unable to perform oc binary actions because of insecure flag Key: JBIDE-22644 URL: https://issues.jboss.org/browse/JBIDE-22644 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Final Reporter: Jeff Cantrill Trying to retrieve pod logs or any oc binary action results in warning of: specifying a root certificates file with the insecure flag is not allowed Per deads openshift dev "...it means that your kubeconfig file has a CA set, but you're trying to connect insecurely" Persumably this requires us to make sure KUBECONFIG env var is not set when executing oc binary commands. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-249) Add Registry Account UI improvement [EBZ#495693]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-249?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg closed ERT-249. ------------------------------- Fix Version/s: Neon.1 (4.6) Resolution: Done Upstream bug has been resolved so marking as closed. Some additional changes may also come to Registry Accounts and the way they are used from the Pull/Push Image page, but there are bugs for this. > Add Registry Account UI improvement [EBZ#495693] > ------------------------------------------------ > > Key: ERT-249 > URL: https://issues.jboss.org/browse/ERT-249 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: Docker, bzira > Fix For: Neon.1 (4.6) > > > I suggest to add note/change labels in dialog Preferences->Docker->Registry Accounts-> Add . > In Server Address could be just username on Docker Hub or address of the OpenShift Docker Registry - this should be mentioned at least as a note or as a tooltip. > This dialog could be also wider(if server address longer...). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22594: ------------------------------------- The docker credentials required to log in to a docker registry consist in a username and password (at least for what is supported now by the docker tooling) For the CDK docker registry, it turns out the docker password IS the openshift connection token, but this is really specific to the CDK. If a user were to deploy to an other docker registry, then it'd be a real password. TL;DR; you must keep the password label > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: connection_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.S116 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Dmitry Bocharov commented on JBIDE-22594: ----------------------------------------- [~akazakov], i see. Actually [this line of code|https://github.com/jbosstools/jbosstools-openshift/blob/558a15c7cc4c...] also confused me. Is it ok that we are trying to set a token from connection to the Password field for registry? Firstly, i corrected it, but then thought it is ok. > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: connection_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.S116 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22594: ---------------------------------------- [~bdshadow] "password/token" is what confused me. There is no "token" for regestry in the wizard. Only "password". > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: connection_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.S116 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22594: ---------------------------------------- [~fbricon] yes, if the wizard is open from OS explorer it makes sense to start with the second page. When the wizard is opened from the docker view then it's not optimal but I agree it's a minor issue and should be discussed separately. > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: connection_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.S116 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-794) Deprecate ModeShape for 9.0.1

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-794: -------------------------------- Summary: Deprecate ModeShape for 9.0.1 Key: JBTIS-794 URL: https://issues.jboss.org/browse/JBTIS-794 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: distribution, modeshape Affects Versions: 9.0.0.GA Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 9.0.0.GA Deprecate ModeShape - update labels. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3644) Document installer/cdk/devstudio basic workflow

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3644?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3644: ---------------------------------- [~mhusnain] is this done for 9.1? Is it updated for 10.0.0? Can this be completed by EOD tomorrow Friday Jun 24? Need it ready before Summit on Monday. > Document installer/cdk/devstudio basic workflow > ----------------------------------------------- > > Key: JBDS-3644 > URL: https://issues.jboss.org/browse/JBDS-3644 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: documentation, platform-installer > Reporter: Max Rydahl Andersen > Assignee: Misha Ali > Priority: Blocker > Fix For: 10.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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