[JBoss JIRA] (JBIDE-23486) Build: DeployImageJobtest#testStubImageStreamWhereOneDoesNotExistAndImageIsPublic is failing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23486?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23486:
------------------------------------------
merged into master
> Build: DeployImageJobtest#testStubImageStreamWhereOneDoesNotExistAndImageIsPublic is failing
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-23486
> URL: https://issues.jboss.org/browse/JBIDE-23486
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.4.2.Final
>
>
> Our tests are failing
> {code}
> testStubImageStreamWhereOneDoesNotExistAndImageIsPublic(org.jboss.tools.openshift.test.ui.job.DeployImageJobTest) Time elapsed: 0.016 sec <<< FAILURE!
> java.lang.AssertionError: expected:<repo/mynamespace/myimagename:latest> but was:<:latest>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.jboss.tools.openshift.test.ui.job.DeployImageJobTest.testStubImageStreamWhereOneDoesNotExistAndImageIsPublic(DeployImageJobTest.java:219)
> {code}
> the failing assertion is the following:
> {code}
> assertEquals(new DockerImageURI("repo/mynamespace/myimagename:latest"), is.getDockerImageRepository());
> {code}
> Starting with [#1677|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/1677/] our jenkins is thus failing.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23487) Server adapter: Publishing fails when server adapter is created out of eap app running on openshift (in cdk)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23487?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23487 at 11/14/16 5:50 AM:
--------------------------------------------------------------------
[~mlabuda] [~mmalina] this could be MacOS specific. I never experienced this on Linux. We should thus make sure [~mmalina], who reported this, cant replicate it.
[~mmalina] you said that the pod is running, when experience this. Can you connect to the pod by other means?
* Can you access the pod logs via Eclipse?
* Can you oc rsh into the pod?
was (Author: adietish):
[~mlabuda] [~mmalina] this could be MacOS specific. I never experienced this on Linux. We should thus make sure [~mmalina], who reported this, cant replicate it.
> Server adapter: Publishing fails when server adapter is created out of eap app running on openshift (in cdk)
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23487
> URL: https://issues.jboss.org/browse/JBIDE-23487
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Martin Malina
> Labels: openshift_v3, rsync, server_adapter
> Fix For: 4.4.2.Final
>
>
> While testing Rob's jolokia stuff from JBIDE-23429 I did this:
> 1. Start CDK (2.3.cr1)
> 2. Create eap64-basic-s2i app
> 3. Wait till the app is built and the pod is running
> 4. Right-click the eap-app in OpenShift explorer and create a server adapter
> 5. Now the server adapter is publishing and this will fail:
> {code}
> Could not sync /Users/rasp/jbossqa/JBDS/10.0.0/workspace-neon-1a/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy to all pods running the service eap-app
> Syncing com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@41249d31 to com.openshift.restclient.capability.resources.IRSyncable$PodPeer@27c8ba3a failed: Unable to connect to the server: net/http: TLS handshake timeout
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
> error: exit status 12
> {code}
> This is on macOS Sierra with JBoss Tools from master with Rob's patches, but he says his patches have nothing to do with publishing. I may try out a normal build of devstudio or JBT later.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23487) Server adapter: Publishing fails when server adapter is created out of eap app running on openshift (in cdk)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23487?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23487:
------------------------------------------
[~mlabuda] [~mmalina] this could be MacOS specific. I never experienced this on Linux. We should thus make sure [~mmalina], who reported this, cant replicate it.
> Server adapter: Publishing fails when server adapter is created out of eap app running on openshift (in cdk)
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23487
> URL: https://issues.jboss.org/browse/JBIDE-23487
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Martin Malina
> Labels: openshift_v3, rsync, server_adapter
> Fix For: 4.4.2.Final
>
>
> While testing Rob's jolokia stuff from JBIDE-23429 I did this:
> 1. Start CDK (2.3.cr1)
> 2. Create eap64-basic-s2i app
> 3. Wait till the app is built and the pod is running
> 4. Right-click the eap-app in OpenShift explorer and create a server adapter
> 5. Now the server adapter is publishing and this will fail:
> {code}
> Could not sync /Users/rasp/jbossqa/JBDS/10.0.0/workspace-neon-1a/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy to all pods running the service eap-app
> Syncing com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@41249d31 to com.openshift.restclient.capability.resources.IRSyncable$PodPeer@27c8ba3a failed: Unable to connect to the server: net/http: TLS handshake timeout
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
> error: exit status 12
> {code}
> This is on macOS Sierra with JBoss Tools from master with Rob's patches, but he says his patches have nothing to do with publishing. I may try out a normal build of devstudio or JBT later.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23486) Build: DeployImageJobtest#testStubImageStreamWhereOneDoesNotExistAndImageIsPublic is failing
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23486?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23486:
-------------------------------
Sprint: devex #123 November 2016 (was: devex #124 December 2017)
> Build: DeployImageJobtest#testStubImageStreamWhereOneDoesNotExistAndImageIsPublic is failing
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-23486
> URL: https://issues.jboss.org/browse/JBIDE-23486
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.4.2.Final
>
>
> Our tests are failing
> {code}
> testStubImageStreamWhereOneDoesNotExistAndImageIsPublic(org.jboss.tools.openshift.test.ui.job.DeployImageJobTest) Time elapsed: 0.016 sec <<< FAILURE!
> java.lang.AssertionError: expected:<repo/mynamespace/myimagename:latest> but was:<:latest>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.jboss.tools.openshift.test.ui.job.DeployImageJobTest.testStubImageStreamWhereOneDoesNotExistAndImageIsPublic(DeployImageJobTest.java:219)
> {code}
> the failing assertion is the following:
> {code}
> assertEquals(new DockerImageURI("repo/mynamespace/myimagename:latest"), is.getDockerImageRepository());
> {code}
> Starting with [#1677|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/1677/] our jenkins is thus failing.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23486) Build: DeployImageJobtest#testStubImageStreamWhereOneDoesNotExistAndImageIsPublic is failing
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23486?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23486:
-------------------------------
Sprint: devex #124 December 2017
> Build: DeployImageJobtest#testStubImageStreamWhereOneDoesNotExistAndImageIsPublic is failing
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-23486
> URL: https://issues.jboss.org/browse/JBIDE-23486
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.4.2.Final
>
>
> Our tests are failing
> {code}
> testStubImageStreamWhereOneDoesNotExistAndImageIsPublic(org.jboss.tools.openshift.test.ui.job.DeployImageJobTest) Time elapsed: 0.016 sec <<< FAILURE!
> java.lang.AssertionError: expected:<repo/mynamespace/myimagename:latest> but was:<:latest>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.jboss.tools.openshift.test.ui.job.DeployImageJobTest.testStubImageStreamWhereOneDoesNotExistAndImageIsPublic(DeployImageJobTest.java:219)
> {code}
> the failing assertion is the following:
> {code}
> assertEquals(new DockerImageURI("repo/mynamespace/myimagename:latest"), is.getDockerImageRepository());
> {code}
> Starting with [#1677|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/1677/] our jenkins is thus failing.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-932) Fix import tests
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/JBTIS-932?page=com.atlassian.jira.plugin.... ]
Matej Kralik updated JBTIS-932:
-------------------------------
Description:
ImportDDL - fix property in the materialized view and extend test about check extension properties, add jar to UDF test
DynamicDDL - dataroles test in the windows and /r /t in the check same function in the windows
was:
ImportDDL - fix property in the materialized view and extend test about check extension properties, add jar to UDF test
TeiidConnectionImport - fix issues on the Jenkins
DynamicDDL - dataroles test in the windows and /r /t in the check same function in the windows
> Fix import tests
> ----------------
>
> Key: JBTIS-932
> URL: https://issues.jboss.org/browse/JBTIS-932
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: QE, teiid
> Affects Versions: 4.3.2.Final
> Reporter: Matej Kralik
> Assignee: Matej Kralik
>
> ImportDDL - fix property in the materialized view and extend test about check extension properties, add jar to UDF test
> DynamicDDL - dataroles test in the windows and /r /t in the check same function in the windows
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4173) Popup error "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments."
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4173?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier commented on JBDS-4173:
---------------------------------------
I'm using the version embedded in the latest dev suite installer which seems to be the 2.3.0.CR1
> Popup error "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments."
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4173
> URL: https://issues.jboss.org/browse/JBDS-4173
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, openshift, platform-installer
> Affects Versions: 10.2.0.AM3
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 10.2.0.GA
>
> Attachments: image-2016-11-10-16-04-30-182.png
>
>
> Version: 10.2.0.AM3
> Build id: AM3-v20161108-0111-B6398
> i noticed that the OpenShift Connection ha snot been created by th einstaller either.
> - after that the COntainer is marked as Started
> - when doing vagrant up in the cdk, there are no errors
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23489) Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23489?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-23489:
-------------------------------
Description:
We need to find a way how to run automated tests agains devstudio rpm.
I've tried the following paths:
1) (as root) mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/shareclipse/droplets/devstudio/eclipse/
2) (as hudson) mvn clean verify -Dtest.installBase=~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
But none of the above works.
was:
We need to find a way how to run automated tests agains devstudio rpm.
I've tried the following paths:
1) mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/shareclipse/droplets/devstudio/eclipse/
2) mvn clean verify -Dtest.installBase=~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
But none of the above works.
> Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23489
> URL: https://issues.jboss.org/browse/JBIDE-23489
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.2.AM3
> Reporter: Pavol Srna
> Fix For: 4.4.2.Final
>
>
> We need to find a way how to run automated tests agains devstudio rpm.
> I've tried the following paths:
> 1) (as root) mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/shareclipse/droplets/devstudio/eclipse/
> 2) (as hudson) mvn clean verify -Dtest.installBase=~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
> But none of the above works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23489) Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23489?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-23489:
---------------------------------------
We may exclude also this option:
mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/bin/
which is the path where eclipse binary executable is located. Usually the problem is that user under who the maven command is executed has no rights (and should not have) to write to that location and thus, this results in error:
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.26.0:test (default-test) on project org.jboss.tools.freemarker.ui.bot.test: Execution default-test of goal org.eclipse.tycho:tycho-surefire-plugin:0.26.0:test failed: Exception creating test eclipse runtime: /opt/rh/rh-eclipse46/root/usr/bin/dev.properties (Permission denied)
After some digging, maybe [osgi.user.area|http://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclips...] parameter (or some other in section "Locations") is the way how to change the location of folders where user has access. Although, I have yet to figure out how to pass/set this parameters.
> Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23489
> URL: https://issues.jboss.org/browse/JBIDE-23489
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.2.AM3
> Reporter: Pavol Srna
> Fix For: 4.4.2.Final
>
>
> We need to find a way how to run automated tests agains devstudio rpm.
> I've tried the following paths:
> 1) mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/shareclipse/droplets/devstudio/eclipse/
> 2) mvn clean verify -Dtest.installBase=~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
> But none of the above works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23489) Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-23489:
----------------------------------
Summary: Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
Key: JBIDE-23489
URL: https://issues.jboss.org/browse/JBIDE-23489
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.4.2.AM3
Reporter: Pavol Srna
Fix For: 4.4.2.Final
We need to find a way how to run automated tests agains devstudio rpm.
I've tried the following paths:
1) mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/shareclipse/droplets/devstudio/eclipse/
2) mvn clean verify -Dtest.installBase=~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
But none of the above works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months