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

Apicast won't provide any log, when configuration from configmap is invalid

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • None
    • 2.0 ER3
    • Gateway
    • None
    • Hide
      • Deploy Apicast to openshift
      • Create configMap with configuration, where only one service is set
      • Edit deploymentconfig to mount configMap and set THREESCALE_CONFIG_FILE appropriately
      • Save it and wait for start of deployment
      • The newly created pods will not be recognized as started, because liveness probe will fail
      Show
      Deploy Apicast to openshift Create configMap with configuration, where only one service is set Edit deploymentconfig to mount configMap and set THREESCALE_CONFIG_FILE appropriately Save it and wait for start of deployment The newly created pods will not be recognized as started, because liveness probe will fail

      When started with invalid configMap, apicast won't log any usable info, but will fail to start due to timeout in openshift's liveness check.

        1. apicast.log
          9 kB

              mcichra Michal Cichra (Inactive)
              mjaros@redhat.com Miroslav Jaroš (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: