[jboss-jira] [JBoss JIRA] (WFWIP-169) Galleon provisioning does not work when layers defined using env vars
[
https://issues.jboss.org/browse/WFWIP-169?page=com.atlassian.jira.plugin....
]
Nikoleta Ziakova updated WFWIP-169:
-----------------------------------
Description:
When running s2i build using the builder image at
docker-registry.engineering.redhat.com/kwills/eap-cd-openshift:EAP7-891 and
[kitchensink|https://github.com/jboss-developer/jboss-eap-quickstarts/tree...]
quickstart using {{cloud-profile-h2}}, h2 is not installed:
{code}
oc new-app --template=eap-cd-basic-s2i \
-p IMAGE_STREAM_NAMESPACE=eap-demo \
-p SOURCE_REPOSITORY_URL=https://github.com/nziakova/jboss-eap-quickstarts \
-p SOURCE_REPOSITORY_REF=test \
-p CONTEXT_DIR=kitchensink \
-p APPLICATION_NAME=kitchensink \
-e GALLEON_PROVISION_DEFAULT_CONFIG_LAYERS=h2-datasource
# OR: -e GALLEON_PROVISION_SERVER=cloud-profile-h2
{code}
{code}
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.jdbc-driver.h2 (missing) dependents: [service
jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS"]
{code}
When running the same build with
[helloworld|https://github.com/jboss-developer/jboss-eap-quickstarts/tree/...]
quickstart (which does not use h2), the build passes and the app is successfully deployed.
The issue is, the server is not provisioned as requested.
This blocks our testing.
was:
When running s2i build using the builder
[image|docker-registry.engineering.redhat.com/kwills/eap-cd-openshift:EAP7...] and
[kitchensink|https://github.com/jboss-developer/jboss-eap-quickstarts/tree...]
quickstart using {{cloud-profile-h2}}, h2 is not installed:
{code}
oc new-app --template=eap-cd-basic-s2i \
-p IMAGE_STREAM_NAMESPACE=eap-demo \
-p SOURCE_REPOSITORY_URL=https://github.com/nziakova/jboss-eap-quickstarts \
-p SOURCE_REPOSITORY_REF=test \
-p CONTEXT_DIR=kitchensink \
-p APPLICATION_NAME=kitchensink \
-e GALLEON_PROVISION_DEFAULT_CONFIG_LAYERS=h2-datasource
# OR: -e GALLEON_PROVISION_SERVER=cloud-profile-h2
{code}
{code}
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.jdbc-driver.h2 (missing) dependents: [service
jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS"]
{code}
When running the same build with
[helloworld|https://github.com/jboss-developer/jboss-eap-quickstarts/tree/...]
quickstart (which does not use h2), the build passes and the app is successfully deployed.
The issue is, the server is not provisioned as requested.
This blocks our testing.
Galleon provisioning does not work when layers defined using env
vars
---------------------------------------------------------------------
Key: WFWIP-169
URL: https://issues.jboss.org/browse/WFWIP-169
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Nikoleta Ziakova
Assignee: Jean Francois Denise
Priority: Critical
When running s2i build using the builder image at
docker-registry.engineering.redhat.com/kwills/eap-cd-openshift:EAP7-891 and
[kitchensink|https://github.com/jboss-developer/jboss-eap-quickstarts/tree...]
quickstart using {{cloud-profile-h2}}, h2 is not installed:
{code}
oc new-app --template=eap-cd-basic-s2i \
-p IMAGE_STREAM_NAMESPACE=eap-demo \
-p SOURCE_REPOSITORY_URL=https://github.com/nziakova/jboss-eap-quickstarts \
-p SOURCE_REPOSITORY_REF=test \
-p CONTEXT_DIR=kitchensink \
-p APPLICATION_NAME=kitchensink \
-e GALLEON_PROVISION_DEFAULT_CONFIG_LAYERS=h2-datasource
# OR: -e GALLEON_PROVISION_SERVER=cloud-profile-h2
{code}
{code}
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.jdbc-driver.h2 (missing) dependents: [service
jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS"]
{code}
When running the same build with
[helloworld|https://github.com/jboss-developer/jboss-eap-quickstarts/tree/...]
quickstart (which does not use h2), the build passes and the app is successfully deployed.
The issue is, the server is not provisioned as requested.
This blocks our testing.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)