January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23020) Integration tests: provide a cdk instance that tests running in jenkins can use

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23020?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-23020. -------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.x) Resolution: Done > Integration tests: provide a cdk instance that tests running in jenkins can use > ------------------------------------------------------------------------------- > > Key: JBIDE-23020 > URL: https://issues.jboss.org/browse/JBIDE-23020 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.3.AM2 > > > We dont have a dedicated OS instance for the integration tests. > Currently the best approach is to have a local CDK since console.engint.openshift.com takes about 2x the time to execute these. > Automatically installing the CDK in jenkins isnt possible since nested virtualization isnt possible: https://engineering.redhat.com/rt/Ticket/Display.html?id=410151 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23020) Integration tests: provide a cdk instance that tests running in jenkins can use

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23020?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23020: ------------------------------------- Summary: Integration tests: provide a cdk instance that tests running in jenkins can use (was: Integration tests: Have a dedicated OS instance) > Integration tests: provide a cdk instance that tests running in jenkins can use > ------------------------------------------------------------------------------- > > Key: JBIDE-23020 > URL: https://issues.jboss.org/browse/JBIDE-23020 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.x > > > We dont have a dedicated OS instance for the integration tests. > Currently the best approach is to have a local CDK since console.engint.openshift.com takes about 2x the time to execute these. > Automatically installing the CDK in jenkins isnt possible since nested virtualization isnt possible: https://engineering.redhat.com/rt/Ticket/Display.html?id=410151 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23020) Integration tests: Have a dedicated OS instance

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23020?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23020 at 1/24/17 8:30 AM: ------------------------------------------------------------------- [~psrna] so I believe that the aim of this issue is achieved. The goal was to be able to have the cdk available when running the tests in jenkins. Achived, awesome! Updating the summary and resolving. was (Author: adietish): [~psrna] so I believe that the aim of this issue is achieved. The goal was to be able to have the cdk available when running the tests in jenkins. Achived, awesome! > Integration tests: Have a dedicated OS instance > ----------------------------------------------- > > Key: JBIDE-23020 > URL: https://issues.jboss.org/browse/JBIDE-23020 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.x > > > We dont have a dedicated OS instance for the integration tests. > Currently the best approach is to have a local CDK since console.engint.openshift.com takes about 2x the time to execute these. > Automatically installing the CDK in jenkins isnt possible since nested virtualization isnt possible: https://engineering.redhat.com/rt/Ticket/Display.html?id=410151 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23020) Integration tests: Have a dedicated OS instance

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23020?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23020: ------------------------------------------ [~psrna] so I believe that the aim of this issue is achieved. The goal was to be able to have the cdk available when running the tests in jenkins. Achived, awesome! > Integration tests: Have a dedicated OS instance > ----------------------------------------------- > > Key: JBIDE-23020 > URL: https://issues.jboss.org/browse/JBIDE-23020 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.x > > > We dont have a dedicated OS instance for the integration tests. > Currently the best approach is to have a local CDK since console.engint.openshift.com takes about 2x the time to execute these. > Automatically installing the CDK in jenkins isnt possible since nested virtualization isnt possible: https://engineering.redhat.com/rt/Ticket/Display.html?id=410151 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23422: ------------------------------------------ [~rcernich] [~kconner] I believe that we still experience this. Can you please give us any update or headsup? > Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23422 > URL: https://issues.jboss.org/browse/JBIDE-23422 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.2.AM2 > Environment: windows 10 > Fedora 24 > Reporter: Ilya Buziuk > Assignee: Jeff MAURY > Priority: Critical > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.4.3.AM2 > > > We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout. > The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)). > We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23761) ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23761?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23761: ------------------------------------- Core tests site: http://download.jboss.org/jbosstools/neon/snapshots/updates/coretests/mas... If you click org.jboss.ide.eclipse.as.test.feature and open it, and look at the feature.xml, it has following content: {code} <plugin id="org.jboss.tools.jmx.core.test" download-size="35" install-size="68" version="1.8.2.v20161121-2100" /> <plugin id="org.jboss.tools.as.management.itests" download-size="8528" install-size="8570" version="3.2.2.v20161128-1945" unpack="false" /> <plugin id="org.jboss.tools.as.test.core" download-size="363" install-size="734" version="3.2.2.v20161121-2100" /> <plugin id="org.jboss.tools.as.itests" download-size="65" install-size="141" version="3.2.2.v20161121-2100" /> {code} But the code in jbt-master has following content {code} <plugin id="org.jboss.tools.jmx.core.test" download-size="0" install-size="0" version="0.0.0" /> <plugin id="org.jboss.ide.eclipse.as.reddeer" download-size="0" install-size="0" version="0.0.0" /> <plugin id="org.jboss.tools.as.test.core" download-size="0" install-size="0" version="0.0.0" /> <plugin id="org.jboss.tools.as.itests" download-size="0" install-size="0" version="0.0.0" /> <plugin id="org.jboss.tools.as.management.itests" download-size="0" install-size="0" version="0.0.0" unpack="false" /> <plugin id="org.jboss.tools.as.ui.bot.itests" download-size="0" install-size="0" version="0.0.0" /> {code} So something here is very strange > ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23761 > URL: https://issues.jboss.org/browse/JBIDE-23761 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, server, updatesite > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.4.3.AM2 > > > [7:30 AM] Pavol Srna: @RobStryker hi Rob, got a minute? > [7:31 AM] Pavol Srna: @RobStryker wondering if the (as, runtime) test-framework can be made available e.g. here: http://download.jboss.org/jbosstools/neon/snapshots/updates/coretests/mas... > [7:31 AM] Pavol Srna: what do you think? > [7:34 AM] Pavol Srna: I don't see it in the org.jboss.ide.eclipse.as.test.feature on site, maybe needs a rebuild? > [12:49 PM] Nick Boldt: if you want more test plugins/features in the coretests site... make sure they're part of the server site [1] and then PR me to add them to the coretests site [2]. > [1] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser... > [2] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > Submit PR against this: > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23771) Pushing Image into Openshift registry fails

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23771?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-23771: ------------------------------------------ [~jeffmaury] do you know, is there a JIRA or a bug registered in github for origin? > Pushing Image into Openshift registry fails > ------------------------------------------- > > Key: JBIDE-23771 > URL: https://issues.jboss.org/browse/JBIDE-23771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: oc version > oc v1.3.2 > kubernetes v1.3.0+52492b4 > features: Basic-Auth GSSAPI Kerberos SPNEGO > Server https://openshift.hughestech.co:8443 > openshift v1.3.2 > kubernetes v1.3.0+52492b4 > Reporter: Dmitrii Bocharov > Attachments: FailedPush.png > > > See the issue created in upstream: https://github.com/openshift/origin/issues/12603 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23767) Jenkins build for OpenShift is failing with mirror problems

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23767?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23767: ------------------------------------------ [~nickboldt] I believe that having announced this would have allowed me to react upfront vs after noticing that the build fails. But if me and rob were the only ones affected, there's no need for further action. Is it? I'd love though if we could announce such potentially build breaking changes, I prefer to act upfront if possible. > Jenkins build for OpenShift is failing with mirror problems > ----------------------------------------------------------- > > Key: JBIDE-23767 > URL: https://issues.jboss.org/browse/JBIDE-23767 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: build > Fix For: 4.4.3.AM2 > > > Starting with [#1782|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Master/job/jbosstools-openshift_master/1782/] jenkins build for OpenShift started to fail with problems in the mirror tool (basic maven build competes successfully): > {code} > Results : > Tests run: 15, Failures: 0, Errors: 0, Skipped: 0 > [INFO] All tests passed! > [INFO] > [INFO] --- tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) @ org.jboss.tools.openshift.cdk.server.test --- > [INFO] Skipped > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] openshift.tests .................................... SUCCESS [ 1.115 s] > [INFO] org.jboss.tools.openshift.egit.test ................ SUCCESS [ 20.698 s] > [INFO] org.jboss.tools.openshift.express.test ............. SUCCESS [ 17.420 s] > [INFO] org.jboss.tools.openshift.test ..................... SUCCESS [ 40.148 s] > [INFO] org.jboss.tools.openshift.cdk.server.test .......... SUCCESS [ 17.296 s] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 02:20 min > [INFO] Finished at: 2017-01-18T05:49:08-05:00 > [INFO] Final Memory: 68M/657M > [INFO] ------------------------------------------------------------------------ > Terminating xvnc. > $ vncserver -kill :91 > Killing Xvnc process ID 589 > Checking console output > /qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-openshift_master/builds/1788/log: > [WARNING] Mirror tool: Problems resolving provisioning plan.: [Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.js.feature.source.feature.group [1.0.0.v20161116-1518].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.js.feature.feature.group [1.0.0.v20161116-1518].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.test.feature.source.feature.group [3.3.1.v20161124-1528].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.cdk.test.feature.feature.group [3.3.1.v20160928-2042].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.feature.feature.group [3.3.1.v20161202-0851].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.express.test.feature.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.egit.integration.feature.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.egit.integration.test.feature.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.feature.source.feature.group [3.3.1.v20161202-0851].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.egit.integration.feature.source.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.test.feature.feature.group [3.3.1.v20161124-1528].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.express.feature.source.feature.group [3.3.1.v20161117-0751].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.cdk.feature.feature.group [3.3.1.v20161025-0131].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.egit.integration.test.feature.source.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.cdk.test.feature.source.feature.group [3.3.1.v20160928-2042].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.express.test.feature.source.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.express.feature.feature.group [3.3.1.v20161117-0751].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.cdk.feature.source.feature.group [3.3.1.v20161025-0131].] > Build step 'Jenkins Text Finder' changed build result to FAILURE > Archiving artifacts > Recording test results > [description-setter] Description set: > Sending e-mails to: jbosstools-builds(a)lists.jboss.org adietish(a)redhat.com jcantril(a)redhat.com fbricon(a)redhat.com slkabanovich(a)gmail.com > Notifying upstream projects of job completion > Finished: FAILURE > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23771) Pushing Image into Openshift registry fails

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23771?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23771: ------------------------------------ This is a know issue. Pushing an image to OpenShift registry does not work if you are not working with the OpenShift docker daemon. This happens when the OpenShift env (ie the registry) is using a non standard certificate (self signed,....) that cannot be validated by the Docker daemon > Pushing Image into Openshift registry fails > ------------------------------------------- > > Key: JBIDE-23771 > URL: https://issues.jboss.org/browse/JBIDE-23771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: oc version > oc v1.3.2 > kubernetes v1.3.0+52492b4 > features: Basic-Auth GSSAPI Kerberos SPNEGO > Server https://openshift.hughestech.co:8443 > openshift v1.3.2 > kubernetes v1.3.0+52492b4 > Reporter: Dmitrii Bocharov > Attachments: FailedPush.png > > > See the issue created in upstream: https://github.com/openshift/origin/issues/12603 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23771) Pushing Image into Openshift registry fails

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23771?page=com.atlassian.jira.plugi... ] Jeff MAURY edited comment on JBIDE-23771 at 1/24/17 7:27 AM: ------------------------------------------------------------- This is a known issue. Pushing an image to OpenShift registry does not work if you are not working with the OpenShift docker daemon. This happens when the OpenShift env (ie the registry) is using a non standard certificate (self signed,....) that cannot be validated by the Docker daemon was (Author: jeffmaury): This is a know issue. Pushing an image to OpenShift registry does not work if you are not working with the OpenShift docker daemon. This happens when the OpenShift env (ie the registry) is using a non standard certificate (self signed,....) that cannot be validated by the Docker daemon > Pushing Image into Openshift registry fails > ------------------------------------------- > > Key: JBIDE-23771 > URL: https://issues.jboss.org/browse/JBIDE-23771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: oc version > oc v1.3.2 > kubernetes v1.3.0+52492b4 > features: Basic-Auth GSSAPI Kerberos SPNEGO > Server https://openshift.hughestech.co:8443 > openshift v1.3.2 > kubernetes v1.3.0+52492b4 > Reporter: Dmitrii Bocharov > Attachments: FailedPush.png > > > See the issue created in upstream: https://github.com/openshift/origin/issues/12603 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017