Bug 1456009 - [paid][online-stg] Creation fails for all eap persistent templates
Summary: [paid][online-stg] Creation fails for all eap persistent templates
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Templates
Version: 3.x
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Abhishek Gupta
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-26 16:41 UTC by Mike Fiedler
Modified: 2018-03-27 18:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-27 18:08:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike Fiedler 2017-05-26 16:41:51 UTC
Description of problem:

None of the eap*peristent* templates will start because the PVC is smaller than the minimum claim size for the projects.

The error is:  error: persistentvolumeclaims "eap-app-postgresql-claim" is forbidden: minimum storage usage per PersistentVolumeClaim is 1Gi, but request is 512Mi.


Example:

oc new-app --template eap70-postgresql-persistent-s2i
--> Deploying template "openshift/eap70-postgresql-persistent-s2i" to project mff2

     eap70-postgresql-persistent-s2i
     ---------
     Application template for EAP 7 PostgreSQL applications with persistent storage built using S2I.


     * With parameters:
        * APPLICATION_NAME=eap-app
        * HOSTNAME_HTTP=
        * HOSTNAME_HTTPS=
        * SOURCE_REPOSITORY_URL=https://github.com/jboss-openshift/openshift-quickstarts
        * SOURCE_REPOSITORY_REF=1.3
        * CONTEXT_DIR=todolist/todolist-jdbc
        * DB_JNDI=java:jboss/datasources/TodoListDS
        * DB_DATABASE=root
        * VOLUME_CAPACITY=512Mi
        * MQ_QUEUES=
        * MQ_TOPICS=
        * SERVICE_ACCOUNT_NAME=eap7-service-account
        * HTTPS_SECRET=eap7-app-secret
        * HTTPS_KEYSTORE=keystore.jks
        * HTTPS_KEYSTORE_TYPE=
        * HTTPS_NAME=
        * HTTPS_PASSWORD=
        * DB_MIN_POOL_SIZE=
        * DB_MAX_POOL_SIZE=
        * DB_TX_ISOLATION=
        * POSTGRESQL_MAX_CONNECTIONS=
        * POSTGRESQL_SHARED_BUFFERS=
        * MQ_CLUSTER_PASSWORD=2gg1xp5P # generated
        * DB_USERNAME=userYSy # generated
        * DB_PASSWORD=y1lLuGow # generated
        * GITHUB_WEBHOOK_SECRET=0TTg0og0 # generated
        * GENERIC_WEBHOOK_SECRET=RMgoePSd # generated
        * IMAGE_STREAM_NAMESPACE=openshift
        * JGROUPS_ENCRYPT_SECRET=eap7-app-secret
        * JGROUPS_ENCRYPT_KEYSTORE=jgroups.jceks
        * JGROUPS_ENCRYPT_NAME=
        * JGROUPS_ENCRYPT_PASSWORD=
        * JGROUPS_CLUSTER_PASSWORD=JG5Rlgxk # generated
        * AUTO_DEPLOY_EXPLODED=false

--> Creating resources ...
    service "eap-app" created
    service "secure-eap-app" created
    service "eap-app-postgresql" created
    route "eap-app" created
    route "secure-eap-app" created
    imagestream "eap-app" created
    buildconfig "eap-app" created
    deploymentconfig "eap-app" created
    deploymentconfig "eap-app-postgresql" created
    error: persistentvolumeclaims "eap-app-postgresql-claim" is forbidden: minimum storage usage per PersistentVolumeClaim is 1Gi, but request is 512Mi.
--> Failed


Version-Release number of selected component (if applicable):  3.5.5.10


How reproducible: Always


Steps to Reproduce:
1.  oc new-app --template eap70-postgresql-persistent-s2i   (or any other persistent eap template)


Actual results

No PVC created and deployment fails.


Expected results:

Deployment succeeds

Comment 1 Abhishek Gupta 2017-05-31 16:49:11 UTC
Ben Parees: Can we consider increasing the volume size to 1Gi for these templates?

Comment 2 Ben Parees 2017-05-31 20:35:03 UTC
Unless you're proposing doing it as a patch for online, you'll need to ask the xpaas team (Kevin Conner is still the primary point of contact as far as i know, but you can try Rob Cernich also) to make that change as we don't own the templates.

But yes, it sounds like a reasonable change.

Comment 3 Abhishek Gupta 2017-06-06 20:52:52 UTC
This template is NOT packaged with the paid tier. We should bump up the volume capacity to 1Gi to avoid having issues with Online, but at this point, its a lower priority.

Comment 4 Abhishek Gupta 2017-09-27 20:51:37 UTC
Lowering the priority as the template is not packaged with Online and the users can modify the storage size at the time of instantiating the template.

Comment 5 Ben Parees 2018-03-05 19:29:45 UTC
these templates appear to have been updated to use 1Gi volumes:
https://github.com/openshift/library/blob/master/official/eap/templates/eap70-postgresql-persistent-s2i.json#L673-L677

Comment 6 XiuJuan Wang 2018-03-06 02:51:23 UTC
Could create app with templates eap71-amq-persistent-s2i and eap71-postgresql-persistent-s2i in online-stg without error.

https://api.online-stg.openshift.com:443
openshift v3.7.9
kubernetes v1.7.6+a08f5eeb62


Note You need to log in before you can comment on or make changes to this bug.