July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-517) Add basic security for running images [EBZ#519581]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-517?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-517: ------------------------------ Sprint: devex #134 Jun 2017 > Add basic security for running images [EBZ#519581] > -------------------------------------------------- > > Key: ERT-517 > URL: https://issues.jboss.org/browse/ERT-517 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: 6.1.0, Docker, bzira > Fix For: Oxygen.1 (4.7) > > > In a blog by Daniel Walsh, it was recommended that Containers be run with readonly root fs (--readonly). That said, to run most Containers successfully, this option also required accessing /run and /tmp in tmpfs (--tmpfs /run --tmpfs /tmp). > A basic security option should be added to the Run Image Wizard to support: > --readonly --tmpfs /run --tmpfs /tmp -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-517) Add basic security for running images [EBZ#519581]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-517?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-517: --------------------------------- Assignee: Jeff Johnston > Add basic security for running images [EBZ#519581] > -------------------------------------------------- > > Key: ERT-517 > URL: https://issues.jboss.org/browse/ERT-517 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 6.1.0, Docker, bzira > Fix For: Oxygen.1 (4.7) > > > In a blog by Daniel Walsh, it was recommended that Containers be run with readonly root fs (--readonly). That said, to run most Containers successfully, this option also required accessing /run and /tmp in tmpfs (--tmpfs /run --tmpfs /tmp). > A basic security option should be added to the Run Image Wizard to support: > --readonly --tmpfs /run --tmpfs /tmp -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23862) Server adapter: if "oc" in preferences is set to path with a " " syncing fails

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23862?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23862: ------------------------------------- Comment from origin guys on linked issue: it's a bug and we'll fix it, i'm just trying to assess the urgency. I can't promise it's going to make the 3.6 release and it doesn't sound like something we'd backport to 3.5, so i think you will want to consider trying to handle it in your tooling. > Server adapter: if "oc" in preferences is set to path with a " " syncing fails > ------------------------------------------------------------------------------ > > Key: JBIDE-23862 > URL: https://issues.jboss.org/browse/JBIDE-23862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: oc_binary, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: ProcessMain.java, error-in-rsync-for-macos.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24666) support passing in alternative URLs for job or buildinfo.json when running getProjectSHAs.sh

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24666?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24666: ------------------------------- Description: This build shows that the check is looking in one place but the update site is in another: * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... * http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-i... vs. * http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-int... Also, Fuse is built on another server: * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... vs. * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... So, we should be able to configure alternative URLs for the job or the download.jboss.org path. was: This build shows that the check is looking in one place but the update site is in another: * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... Actual location: * http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-i... Tested location: * http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-int... Also, Fuse is built on another server: * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... vs. * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... So, we should be able to configure alternative URLs for the job or the download.jboss.org path. > support passing in alternative URLs for job or buildinfo.json when running getProjectSHAs.sh > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24666 > URL: https://issues.jboss.org/browse/JBIDE-24666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Fix For: 4.5.0.AM2 > > > This build shows that the check is looking in one place but the update site is in another: > * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > * http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-i... vs. > * http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-int... > Also, Fuse is built on another server: > * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... vs. > * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > So, we should be able to configure alternative URLs for the job or the download.jboss.org path. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24666) support passing in alternative URLs for job or buildinfo.json when running getProjectSHAs.sh

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24666?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24666: ------------------------------- Fix Version/s: 4.5.0.AM2 > support passing in alternative URLs for job or buildinfo.json when running getProjectSHAs.sh > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24666 > URL: https://issues.jboss.org/browse/JBIDE-24666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > This build shows that the check is looking in one place but the update site is in another: > * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > * http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-i... vs. > * http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-int... > Also, Fuse is built on another server: > * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... vs. > * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > So, we should be able to configure alternative URLs for the job or the download.jboss.org path. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24666) support passing in alternative URLs for job or buildinfo.json when running getProjectSHAs.sh

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24666?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24666: ---------------------------------- Assignee: Nick Boldt > support passing in alternative URLs for job or buildinfo.json when running getProjectSHAs.sh > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24666 > URL: https://issues.jboss.org/browse/JBIDE-24666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > This build shows that the check is looking in one place but the update site is in another: > * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > * http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-i... vs. > * http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-int... > Also, Fuse is built on another server: > * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... vs. > * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > So, we should be able to configure alternative URLs for the job or the download.jboss.org path. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24664) Server adapter: unusable if oc is not on the path

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24664?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24664: ------------------------------------- Steps to Reproduce: 1) create a cdk server 2) Set a workspace 'oc' location 3) MAKE SURE $PATH does NOT have an 'oc' on it. Can test this via 'which oc' and make sure not found. 4) via the created openshift connection, create a project, and an application (eap-basic-s2i etc) 5) Create a server adapter once the app is created 6) Verify that publishing functions as expected. > Server adapter: unusable if oc is not on the path > ------------------------------------------------- > > Key: JBIDE-24664 > URL: https://issues.jboss.org/browse/JBIDE-24664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Rob Stryker > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM2 > > > The openshift rest client lib is not including the full path when calling ProcessBuilder. So process builder is being asked to run a command named "oc" without the full path to it. In such situation, the process builder (or the OS, not 100% sure which) will revert to searching the system path for the given command, and choose the one on the system path. > Since my machine does not have 'oc' on the system path, openshift tools cannot run the oc command, or publish. > This also blocks adoption of JBIDE-24236, which allows users to select different OC. On linux, the system path's OC will *always* be chosen, regardless of any user settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24664) Server adapter: unusable if oc is not on the path

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24664?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24664: ------------------------------------- respin of build kicked: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > Server adapter: unusable if oc is not on the path > ------------------------------------------------- > > Key: JBIDE-24664 > URL: https://issues.jboss.org/browse/JBIDE-24664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Rob Stryker > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM2 > > > The openshift rest client lib is not including the full path when calling ProcessBuilder. So process builder is being asked to run a command named "oc" without the full path to it. In such situation, the process builder (or the OS, not 100% sure which) will revert to searching the system path for the given command, and choose the one on the system path. > Since my machine does not have 'oc' on the system path, openshift tools cannot run the oc command, or publish. > This also blocks adoption of JBIDE-24236, which allows users to select different OC. On linux, the system path's OC will *always* be chosen, regardless of any user settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24664) Server adapter: unusable if oc is not on the path

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24664?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24664: -------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.Final) > Server adapter: unusable if oc is not on the path > ------------------------------------------------- > > Key: JBIDE-24664 > URL: https://issues.jboss.org/browse/JBIDE-24664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Rob Stryker > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM2 > > > The openshift rest client lib is not including the full path when calling ProcessBuilder. So process builder is being asked to run a command named "oc" without the full path to it. In such situation, the process builder (or the OS, not 100% sure which) will revert to searching the system path for the given command, and choose the one on the system path. > Since my machine does not have 'oc' on the system path, openshift tools cannot run the oc command, or publish. > This also blocks adoption of JBIDE-24236, which allows users to select different OC. On linux, the system path's OC will *always* be chosen, regardless of any user settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24664) Server adapter: unusable if oc is not on the path

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24664?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24664: ------------------------------------- 1) create a cdk server 2) Set a workspace 'oc' location 3) MAKE SURE $PATH does NOT have an 'oc' on it. Can test this via 'which oc' and make sure not found. 4) via the created openshift connection, create a project, and an application (eap-basic-s2i etc) 5) Create a server adapter once the app is created 6) Verify that publishing functions as expected. This patch will end up re-opening https://issues.jboss.org/browse/JBIDE-23862 (even though it was already re-opened) because an underlying OC bug makes using spaces with oc rsync impossible, so for now: DO NOT consider the usecase of 'oc' with a space in it's path. This has not worked and will not work until openshift origin fixes their bug. > Server adapter: unusable if oc is not on the path > ------------------------------------------------- > > Key: JBIDE-24664 > URL: https://issues.jboss.org/browse/JBIDE-24664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Rob Stryker > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM2 > > > The openshift rest client lib is not including the full path when calling ProcessBuilder. So process builder is being asked to run a command named "oc" without the full path to it. In such situation, the process builder (or the OS, not 100% sure which) will revert to searching the system path for the given command, and choose the one on the system path. > Since my machine does not have 'oc' on the system path, openshift tools cannot run the oc command, or publish. > This also blocks adoption of JBIDE-24236, which allows users to select different OC. On linux, the system path's OC will *always* be chosen, regardless of any user settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017