Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-32

Gateway image fails to start in openshift cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 1.0 CR1
    • 1.0 CR1
    • OSE Templates
    • None
    • Hide 
      oc cluster up --version=v1.2.2
oc create -f "${template-file}" # extracted from rpm
oc secret new-basicauth threescale-gw-secret --password="$THREESCALE_AUTH"
oc new-app 3scale-gateway --param "THREESCALE_PORTAL_ENDPOINT_SECRET=threescale-gw-secret" --param "APICAST_LOG_LEVEL=debug"
      Show
      oc cluster up --version=v1.2.2 oc create -f "${template-file}" # extracted from rpm oc secret new -basicauth threescale-gw-secret --password= "$THREESCALE_AUTH" oc new -app 3scale-gateway --param "THREESCALE_PORTAL_ENDPOINT_SECRET=threescale-gw-secret" --param "APICAST_LOG_LEVEL=debug"

      The 3scale-gateway image fails to start in openshift environment with following output:

      2016/12/05 05:16:40 [emerg] 1#1: mkdir() "/opt/app-root/src/client_body_temp" failed (13: Permission denied)
nginx: [emerg] mkdir() "/opt/app-root/src/client_body_temp" failed (13: Permission denied)

      When started manually in docker it starts as expected.
      Tested on rpm based openshift cluster and on developer cluster (deployed by oc cluster up)

              ncross@redhat.com Nick Cross
              mjaros@redhat.com Miroslav Jaroš (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: