May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20737) On Linux, non-root user is not able to use auto-detect to access running Docker instance

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20737?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-20737: --------------------------------------- I'll need to revisit that issue once ERT-165 is done. > On Linux, non-root user is not able to use auto-detect to access running Docker instance > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20737 > URL: https://issues.jboss.org/browse/JBIDE-20737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.0.CR1 > Environment: RHEL 7 > OpenJDK 1.8 > Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > CR1 includes: > com.spotify.docker.client_3.1.1.jar > org.eclipse.linuxtools.docker.core_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.docs_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.ui_1.1.0.201509082008.jar > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Fix For: 4.4.x > > Attachments: nonroot_1.png, nonroot_2.png, nonroot_3.png, root.png > > > On linux, a root user is able to rely on autoconnect to automatically connect to a running Docker instance (at unix:///var/run/docker.sock) > A non-root user is not able to connect. No warning or error is written to the UI/dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20737) On Linux, non-root user is not able to use auto-detect to access running Docker instance

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20737?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-20737: ---------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > On Linux, non-root user is not able to use auto-detect to access running Docker instance > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20737 > URL: https://issues.jboss.org/browse/JBIDE-20737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.0.CR1 > Environment: RHEL 7 > OpenJDK 1.8 > Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > CR1 includes: > com.spotify.docker.client_3.1.1.jar > org.eclipse.linuxtools.docker.core_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.docs_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.ui_1.1.0.201509082008.jar > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Fix For: 4.4.x > > Attachments: nonroot_1.png, nonroot_2.png, nonroot_3.png, root.png > > > On linux, a root user is able to rely on autoconnect to automatically connect to a running Docker instance (at unix:///var/run/docker.sock) > A non-root user is not able to connect. No warning or error is written to the UI/dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21823: ----------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.x) Story Points: 20 Sprint: devex #3 February 2016, devex #114 May 2017 (was: devex #3 February 2016) Assignee: Jeff MAURY > Unable to re-edit Service config > -------------------------------- > > Key: JBIDE-21823 > URL: https://issues.jboss.org/browse/JBIDE-21823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Jeff MAURY > Fix For: 4.4.0.Alpha2 > > > Once a service config has been changed, closing and reopening the config editor does not reveal the latest config, which then causes 409 error when saving subsequent changes, making it impossible to submit new changes. > Steps to reproduce: > - select a service in the OpenShift Explorer > - click on the {{Edit...}} command. > - in the JSON editor for the service config, note the resource version. Eg: > {code} > { > "metadata" : { > "name" : "jee-sample", > "namespace" : "sample", > "selfLink" : "/api/v1/namespaces/sample/services/jee-sample", > "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e", > "resourceVersion" : "38301", > "creationTimestamp" : "2016-02-23T16:06:03Z", > "labels" : {"app" : "jee-sample"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"} > }, > ... > {code} > - make some changes and save > - the service config version should have incremented: > {code} > { > "kind" : "Service", > "apiVersion" : "v1", > "metadata" : { > "name" : "jee-sample", > "namespace" : "sample", > "selfLink" : "/api/v1/namespaces/sample/services/jee-sample", > "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e", > "resourceVersion" : "38390", > "creationTimestamp" : "2016-02-23T16:06:03Z", > "labels" : {"app" : "jee-sample"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"} > } > .... > {code} > - close the config editor > - re-open the config editor > *ASSERT: the editor displays the latest config* > *FAIL the editor displays the initial config* > *Also, on subsequent changes, the OpenShift server responds with a {{409}} error because the new config to save is based out-dated version* > {code} > Could not update "[sample] Service : jee-sample.json" for project "sample" : services "jee-sample" cannot be updated: the object has been modified; please apply your changes to the latest version and try again > Could not update resource jee-sample: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "services \"jee-sample\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "jee-sample", > "kind": "services" > }, > "code": 409 > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20733) Support for .dockerignore file

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20733?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-20733: ---------------------------------- Story Points: 4 > Support for .dockerignore file > ------------------------------ > > Key: JBIDE-20733 > URL: https://issues.jboss.org/browse/JBIDE-20733 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.x > > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=469819 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20733) Support for .dockerignore file

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20733?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-20733: ---------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Support for .dockerignore file > ------------------------------ > > Key: JBIDE-20733 > URL: https://issues.jboss.org/browse/JBIDE-20733 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.x > > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=469819 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19988) Run Docker image wizard does not recognize image that it pulled

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19988?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19988: ---------------------------------- Story Points: 10 > Run Docker image wizard does not recognize image that it pulled > --------------------------------------------------------------- > > Key: JBIDE-19988 > URL: https://issues.jboss.org/browse/JBIDE-19988 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.3.x > > > When you're in the Run a Docker Image and search for an image that you don't have (e.g. fedora:latest) and then pull it, using the link below the Image field, after the image is pulled, the wizard still says it's not available locally. > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=469709 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21967) Cannot create server adapter if there is a running build on a project although there are more projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21967?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21967: -------------------------------- Story Points: 10 Sprint: devex #114 May 2017 > Cannot create server adapter if there is a running build on a project although there are more projects > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21967 > URL: https://issues.jboss.org/browse/JBIDE-21967 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha2 > > > When I am having several projects and some of them has already running application, I am not able to create a new server adapter for OpenShift 3 application if there is a project with running build. Once build finish, it is possible to create a project but while there is any project with not completed build (and therefore application image is not there yet) user is blocked from creating a new server adapter. This is related to JBIDE-21731 - once this issue will be fixed, it should keep in mind to allow users proceed with creation of server adapters on other projects. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19698) Dispatch selection in containers view

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19698?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19698: ---------------------------------- Story Points: 4 > Dispatch selection in containers view > ------------------------------------- > > Key: JBIDE-19698 > URL: https://issues.jboss.org/browse/JBIDE-19698 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker > Affects Versions: 4.3.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: upstream > Fix For: 4.4.x > > > When the selection changes in the container view, it should be broadcasted so that other views (Docker Explorer and Properties views) can react accordingly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19698) Dispatch selection in containers view

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19698?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19698: ---------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Dispatch selection in containers view > ------------------------------------- > > Key: JBIDE-19698 > URL: https://issues.jboss.org/browse/JBIDE-19698 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker > Affects Versions: 4.3.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: upstream > Fix For: 4.4.x > > > When the selection changes in the container view, it should be broadcasted so that other views (Docker Explorer and Properties views) can react accordingly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16144) Editing files outside the workspace and served by Live Reload fails in Windows

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16144?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-16144: ---------------------------------- Story Points: 2 (was: 1) > Editing files outside the workspace and served by Live Reload fails in Windows > ------------------------------------------------------------------------------ > > Key: JBIDE-16144 > URL: https://issues.jboss.org/browse/JBIDE-16144 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.1.CR1 > Environment: Windows 7 - 64b, JDK 1.7.0_45 x86 > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.4.x > > > * In workspace preferences > General > Workspace > enable "Refresh using native hooks or polling" > * Import https://github.com/jbosstools/jbosstools-documentation/tree/master/whatsnew as a project > * Right-click on an html file, open with > Web Browser via Live Reload > * Open the text file in a text editor (sublime text for me),change something, save -> browser reloads eventually > * Make a second change : file can't be saved "Access denied" > * Wait 1 minute, try again, it works. > * repeat, fail ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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