November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23463: ---------------------------------- Priority: Major (was: Minor) > Properties: Build pod has state of exit code 0 instead of correct status completed > ---------------------------------------------------------------------------------- > > Key: JBIDE-23463 > URL: https://issues.jboss.org/browse/JBIDE-23463 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.x > > Attachments: exit-code-0.png > > > When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests. > steps: > # EXEC: create an application via a s2i template > # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view" > # EXEC: in Properties: select "Pods" tab. > # ASSERT: a build pod is appearing > # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods > Result: > The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise) > !exit-code-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-23463: --------------------------------------- I think this is a bug not an enhancement. For common users exit codes values has almost no information - they are forced to learn which number means what. Or users could assume, as in some languages/common practices, that exit code 0 is ok, but in other cases just guess. This is in contradiction with oc binary and web UI where state is displayed OK. Changing back to bug and raising to major. > Properties: Build pod has state of exit code 0 instead of correct status completed > ---------------------------------------------------------------------------------- > > Key: JBIDE-23463 > URL: https://issues.jboss.org/browse/JBIDE-23463 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3 > Fix For: 4.4.x > > Attachments: exit-code-0.png > > > When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests. > steps: > # EXEC: create an application via a s2i template > # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view" > # EXEC: in Properties: select "Pods" tab. > # ASSERT: a build pod is appearing > # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods > Result: > The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise) > !exit-code-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23463: ---------------------------------- Issue Type: Bug (was: Enhancement) > Properties: Build pod has state of exit code 0 instead of correct status completed > ---------------------------------------------------------------------------------- > > Key: JBIDE-23463 > URL: https://issues.jboss.org/browse/JBIDE-23463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.x > > Attachments: exit-code-0.png > > > When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests. > steps: > # EXEC: create an application via a s2i template > # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view" > # EXEC: in Properties: select "Pods" tab. > # ASSERT: a build pod is appearing > # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods > Result: > The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise) > !exit-code-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-446) DockerException in ProcessUtils$FluentProcessBuilder.<init> [EBZ#507143]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-446?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-446: ------------------------------ Issue Type: Bug (was: Task) > DockerException in ProcessUtils$FluentProcessBuilder.<init> [EBZ#507143] > ------------------------------------------------------------------------ > > Key: ERT-446 > URL: https://issues.jboss.org/browse/ERT-446 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Affects Versions: Neon.1 (4.6) > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.2.0, Docker, bzira > Fix For: Neon.2 (4.6) > > > The following problem was reported via the automated error reporting: > Message: The 'docker-machine' command could not be located in '/usr/local/bin' > org.eclipse.linuxtools.docker.core.DockerException: The 'docker-machine' command could not be located in '/usr/local/bin' > at org.eclipse.linuxtools.internal.docker.core.ProcessUtils$FluentProcessBuilder.<init>(ProcessUtils.java:96) > at org.eclipse.linuxtools.internal.docker.core.ProcessUtils$FluentProcessBuilder.<init>(ProcessUtils.java:88) > at org.eclipse.linuxtools.internal.docker.core.ProcessUtils.processBuilder(ProcessUtils.java:69) > at org.eclipse.linuxtools.internal.docker.core.DockerMachine.getNames(DockerMachine.java:45) > at org.eclipse.linuxtools.internal.docker.ui.wizards.NewDockerConnectionPage$4.retrieveDockerMachineNames(NewDockerConnectionPage.java:806) > at org.eclipse.linuxtools.internal.docker.ui.wizards.NewDockerConnectionPage$4.widgetSelected(NewDockerConnectionPage.java:714) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > Bundles: > | org.eclipse.linuxtools.docker.core | 2.1.0.201609141916 | 2.1.0.201609141916 | > | org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 | > | org.eclipse.swt | 3.105.1.v20160907-0248 | 3.105.1.v20160907-0248 | > Operating Systems: > | Linux | 4.4.0 | 4.4.0 | > | Windows | 10.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5813b... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. > Created on behalf of xcoulon(a)xxxxxx.xxx -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-429) Improve UI: avoid borders to have clean UI on Windows [EBZ#504028]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-429?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-429: ------------------------------ Sprint: devex #122 October 2016 > Improve UI: avoid borders to have clean UI on Windows [EBZ#504028] > ------------------------------------------------------------------ > > Key: ERT-429 > URL: https://issues.jboss.org/browse/ERT-429 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Affects Versions: Neon.1 (4.6) > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Priority: Trivial > Labels: Docker, bzira > Fix For: Neon.2 (4.6) > > > Created attachment 264595 > Search and pull a docker image bad border -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-429) Improve UI: avoid borders to have clean UI on Windows [EBZ#504028]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-429?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon resolved ERT-429. ------------------------------- Resolution: Done > Improve UI: avoid borders to have clean UI on Windows [EBZ#504028] > ------------------------------------------------------------------ > > Key: ERT-429 > URL: https://issues.jboss.org/browse/ERT-429 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Affects Versions: Neon.1 (4.6) > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Priority: Trivial > Labels: Docker, bzira > Fix For: Neon.2 (4.6) > > > Created attachment 264595 > Search and pull a docker image bad border -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-429) Improve UI: avoid borders to have clean UI on Windows [EBZ#504028]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-429?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon reassigned ERT-429: --------------------------------- Issue Type: Bug (was: Task) Fix Version/s: Neon.2 (4.6) Affects Version/s: Neon.1 (4.6) Assignee: Xavier Coulon > Improve UI: avoid borders to have clean UI on Windows [EBZ#504028] > ------------------------------------------------------------------ > > Key: ERT-429 > URL: https://issues.jboss.org/browse/ERT-429 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Affects Versions: Neon.1 (4.6) > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Priority: Trivial > Labels: Docker, bzira > Fix For: Neon.2 (4.6) > > > Created attachment 264595 > Search and pull a docker image bad border -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-204: ------------------------------ Sprint: devex #118 July 2016, devex #120 September 2016 (was: devex #118 July 2016, devex #120 September 2016, devex #122 October 2016) > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-446) DockerException in ProcessUtils$FluentProcessBuilder.<init> [EBZ#507143]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-446?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon reassigned ERT-446: --------------------------------- Affects Version/s: Neon.1 (4.6) Assignee: Xavier Coulon > DockerException in ProcessUtils$FluentProcessBuilder.<init> [EBZ#507143] > ------------------------------------------------------------------------ > > Key: ERT-446 > URL: https://issues.jboss.org/browse/ERT-446 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Affects Versions: Neon.1 (4.6) > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.2.0, Docker, bzira > Fix For: Neon.2 (4.6) > > > The following problem was reported via the automated error reporting: > Message: The 'docker-machine' command could not be located in '/usr/local/bin' > org.eclipse.linuxtools.docker.core.DockerException: The 'docker-machine' command could not be located in '/usr/local/bin' > at org.eclipse.linuxtools.internal.docker.core.ProcessUtils$FluentProcessBuilder.<init>(ProcessUtils.java:96) > at org.eclipse.linuxtools.internal.docker.core.ProcessUtils$FluentProcessBuilder.<init>(ProcessUtils.java:88) > at org.eclipse.linuxtools.internal.docker.core.ProcessUtils.processBuilder(ProcessUtils.java:69) > at org.eclipse.linuxtools.internal.docker.core.DockerMachine.getNames(DockerMachine.java:45) > at org.eclipse.linuxtools.internal.docker.ui.wizards.NewDockerConnectionPage$4.retrieveDockerMachineNames(NewDockerConnectionPage.java:806) > at org.eclipse.linuxtools.internal.docker.ui.wizards.NewDockerConnectionPage$4.widgetSelected(NewDockerConnectionPage.java:714) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > Bundles: > | org.eclipse.linuxtools.docker.core | 2.1.0.201609141916 | 2.1.0.201609141916 | > | org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 | > | org.eclipse.swt | 3.105.1.v20160907-0248 | 3.105.1.v20160907-0248 | > Operating Systems: > | Linux | 4.4.0 | 4.4.0 | > | Windows | 10.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5813b... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. > Created on behalf of xcoulon(a)xxxxxx.xxx -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-446) DockerException in ProcessUtils$FluentProcessBuilder.<init> [EBZ#507143]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-446?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon resolved ERT-446. ------------------------------- Resolution: Done > DockerException in ProcessUtils$FluentProcessBuilder.<init> [EBZ#507143] > ------------------------------------------------------------------------ > > Key: ERT-446 > URL: https://issues.jboss.org/browse/ERT-446 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Affects Versions: Neon.1 (4.6) > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.2.0, Docker, bzira > Fix For: Neon.2 (4.6) > > > The following problem was reported via the automated error reporting: > Message: The 'docker-machine' command could not be located in '/usr/local/bin' > org.eclipse.linuxtools.docker.core.DockerException: The 'docker-machine' command could not be located in '/usr/local/bin' > at org.eclipse.linuxtools.internal.docker.core.ProcessUtils$FluentProcessBuilder.<init>(ProcessUtils.java:96) > at org.eclipse.linuxtools.internal.docker.core.ProcessUtils$FluentProcessBuilder.<init>(ProcessUtils.java:88) > at org.eclipse.linuxtools.internal.docker.core.ProcessUtils.processBuilder(ProcessUtils.java:69) > at org.eclipse.linuxtools.internal.docker.core.DockerMachine.getNames(DockerMachine.java:45) > at org.eclipse.linuxtools.internal.docker.ui.wizards.NewDockerConnectionPage$4.retrieveDockerMachineNames(NewDockerConnectionPage.java:806) > at org.eclipse.linuxtools.internal.docker.ui.wizards.NewDockerConnectionPage$4.widgetSelected(NewDockerConnectionPage.java:714) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > Bundles: > | org.eclipse.linuxtools.docker.core | 2.1.0.201609141916 | 2.1.0.201609141916 | > | org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 | > | org.eclipse.swt | 3.105.1.v20160907-0248 | 3.105.1.v20160907-0248 | > Operating Systems: > | Linux | 4.4.0 | 4.4.0 | > | Windows | 10.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5813b... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. > Created on behalf of xcoulon(a)xxxxxx.xxx -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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