Skip to content
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.

ConfigMap / Wildfly quickstart fails to build #3134

Closed
ldimaggi opened this issue Apr 13, 2018 · 17 comments · May be fixed by fabric8io/fabric8-pipeline-library#412
Closed

ConfigMap / Wildfly quickstart fails to build #3134

ldimaggi opened this issue Apr 13, 2018 · 17 comments · May be fixed by fabric8io/fabric8-pipeline-library#412
Labels
area/launcher area/quickstarts priority/P4 Normal SEV2-high team/launcher type/bug
Milestone
Sprint 148

Comments

@ldimaggi
Copy link
Collaborator

ldimaggi commented Apr 13, 2018 •
edited
Loading

Steps to recreate:

  • Create a new app/quickstart - select mission= Config, Runtime = Wildfly
  • Observe build pipeline fail

Error:

EXITCODE   0[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 646.01 s <<< FAILURE! - in io.openshift.boosters.GreetingServiceTest
[ERROR] io.openshift.boosters.GreetingServiceTest  Time elapsed: 646.009 s  <<< ERROR!
org.jboss.arquillian.container.spi.client.container.DeploymentException: Process failed to start
Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Process failed to start

[INFO] 
[INFO] Results:
[INFO] 
[ERROR] Errors: 
[ERROR]   GreetingServiceTest.io.openshift.boosters.GreetingServiceTest ? Deployment Pro...
[INFO] 
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 13:24 min
[INFO] Finished at: 2018-04-13T20:11:15+00:00
[INFO] Final Memory: 53M/77M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on project app-test-1: There are test failures.
[ERROR] 
[ERROR] Please refer to /home/jenkins/workspace/testmachine_april13m_master-AU3CED4S3IAQBODSQYGEJ7MDHFKHVJY3R45J5PK6DZBRDD3EDWNQ/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on project app-test-1: There are test failures.
@msrb
Copy link
Collaborator

msrb commented Apr 15, 2018

Similar issues:

@sivaavkd sivaavkd added this to the Sprint 148 milestone Apr 17, 2018
@qodfathr qodfathr added the priority/P1 Critical label Apr 23, 2018
@gastaldi
Copy link
Member

@Ladicek @kenfinnigan any clue on what's going on? Who can own this issue?

@kenfinnigan
Copy link

As this is a Che specific issue, and there isn't much in terms of a stacktrace, it's hard to know what's going on

@ALRubinger
Copy link

ALRubinger commented Apr 24, 2018 •
edited
Loading

Requesting of the OSIO Getting Started team to triage and provide actionable requests for the runtime teams if necessary. @animuk

@gastaldi gastaldi assigned animuk and unassigned edewit, gastaldi and quintesse Apr 25, 2018
@animuk animuk removed their assignment Apr 26, 2018
@animuk
Copy link
Collaborator

animuk commented Apr 30, 2018

@kenfinnigan This is not Che specific issue. ConfigMap / Wildfly quickstart still not in workable state inside OSIO and I believe booster catalog also is not updated with the latest version which should work flawlessly in OSIO.

@kenfinnigan
Copy link

@animuk, apologies, I meant OSIO specific not Che specific.

For product the only version that will work needs to be based on 7.1.0 of WF Swarm. Those boosters won't be released until the end of May.

There is nothing that can be updated in the booster catalog to fix that now

@GeorgeActon
Copy link
Collaborator

@kenfinnigan to clarify, are the boosters not being released for any environment or not being released for OSIO?

@kenfinnigan
Copy link

There will be no release of WF Swarm Boosters based on 7.1.0 until the end of May, any environment, anywhere

@GeorgeActon
Copy link
Collaborator

GeorgeActon commented May 2, 2018 •
edited
Loading

@kenfinnigan I interpret that to mean No Wildfly Swarm boosters currently work, all of them are affected by this problem and none of them will be able to work in any environment until WF Swarm 7.1.0 is available.

Have I understood this correctly

@lordofthejars
Copy link
Collaborator

@bartoszmajsak Yes I agree that pipeline must be the correct place to make tests run just in build phase. If you want we can discuss this in BJN.

hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 13, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
5e2e343 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 13, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
e531432 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 13, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
6ecaf04 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 14, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
1036160 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 14, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
42e2862 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.
This patch adds `runTestsInUserNamespace` to use username namespace as defualt default environment to run
Integration Tests.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 14, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
5074cd9 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.
This patch adds `runTestsInUserNamespace` to use username namespace as defualt default environment to run
Integration Tests.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 14, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
a67aac1 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.
This patch adds `runTestsInUserNamespace` to use username namespace as defualt default environment to run
Integration Tests.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 14, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
ade290c 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.
This patch adds `runTestsInUserNamespace` to use username namespace as defualt default environment to run
Integration Tests.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 14, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
b7fcd5f 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.
This patch adds `runTestsInUserNamespace` to use username namespace as defualt default environment to run
Integration Tests.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 14, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
bdcc1c1 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.
This patch adds `runTestsInUserNamespace` to use username namespace as defualt default environment to run
Integration Tests.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 14, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
255d559 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.
This patch adds `runTestsInUserNamespace` to use username namespace as defualt default environment to run
Integration Tests.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 14, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
56264e1 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.
This patch adds `runTestsInUserNamespace` to use username namespace as defualt default environment to run
Integration Tests.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 16, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
be9910d 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.
It has added a util method to retrive default test namespace.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 16, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
6acc03a 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.
It has added a util method to retrive default test namespace.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-pipeline-library that referenced this issue Aug 16, 2018
@hrishin
mavenIntegrationTest: allow overriding mvn commands
d1dfb49 
This patch allows the `mavenCI{}` to over maven command in order
to allow `mavenIntegrationTes{}` to pass specific command to execute.
It has added a util method to retrive default test namespace.

Fixes: openshiftio/openshift.io#763
Fixes: openshiftio/openshift.io#3134
Related to: fabric8io#412
hrishin added a commit to hrishin/fabric8-jenkinsfile-library that referenced this issue Aug 20, 2018
@hrishin
fixes maven integration tests
dfee9a7 
Maven integration tests are failing because it tries to create a
test namespace (project) on openshift, hence call to openshift API gets
fail due to permission issue.
This patch fixes the `mavenCI` step by inputing maven command to run
integration test along with valid test namespace.

Resolves:
 - openshiftio/openshift.io#3134
 - openshiftio/openshift.io#763
@hrishin hrishin mentioned this issue Aug 20, 2018
Merged
@bartoszmajsak
Copy link
Contributor

@sthaha does it mean that it was re-tested and now those boosters work? I see the default command still being the one which was failing tests - hence my question. Or was the "close" a side-effect of referencing this issue in the commit?

@sthaha
Copy link
Collaborator

sthaha commented Aug 28, 2018

@bartoszmajsak

does it mean that it was re-tested and now those boosters work?

No, I think the bug got closed when I merged the patch that referenced this issue (thanks to GH :-) . I am reopening the issue

fabric8io/fabric8-jenkinsfile-library#36 IIRC is open for your feedback
/cc @hrishin

@sthaha sthaha reopened this Aug 28, 2018
@ldimaggi
Copy link
Collaborator Author

ldimaggi commented Dec 2, 2018

Closing as issue is superceded by - #4547

@ldimaggi ldimaggi closed this as completed Dec 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/launcher area/quickstarts priority/P4 Normal SEV2-high team/launcher type/bug
Projects
None yet
Milestone
Sprint 148
Development

Successfully merging a pull request may close this issue.

WIP fix: integration tests are now built in the user namespace