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

Amp 2.0 not running on ocp 3.5

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.0 GA
    • 2.0 GA
    • None
    • None

      I'm not able to deploy AMP on ocp 3.5 due to redis instances not booting up.

      Error syncing pod, skipping: failed to "StartContainer" for "backend-redis" with RunContainerError: "GenerateRunContainerOptions: mkdir /var/lib/origin/openshift.local.volumes/pods/d07af666-3f99-11e7-ad04-02c0191b7b7c/volumes/kubernetes.io~configmap/redis-config/redis.conf: not a directory"

      This is related to the way we override the default /etc/redis.conf file:

      containers:

      • args:
        image: ${REDIS_IMAGE}
        imagePullPolicy: IfNotPresent
        name: system-redis
        terminationMessagePath: /dev/termination-log
        volumeMounts:
      • name: system-redis-storage
        mountPath: "/var/lib/redis/data"
      • name: redis-config
        mountPath: /etc/redis.conf
        subPath: redis.conf

      My environment:

      Version

      OpenShift Master: v3.5.5.15
      Kubernetes Master: v1.5.2+43a9be4

      Investigating the root cause:

      Internal bug:

      Looks like the patch has been merged into 3.5, and a new release has been created, but still has to be productised into a linux container image.

              jprusi@redhat.com Joaquim Moreno Prusi (Inactive)
              ppenicka@redhat.com Petr Penicka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: