Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-24352

Builder Image: Persistent Volume Claim overrides deployment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Critical Critical
    • 8.0.0.GA-CR1, 8.0.0.GA
    • 8.0.0.Beta-CR1
    • OpenShift
    • None
    • False
    • None
    • False
    • Hide

      Here we present 4 scenarios: the first uses upstream image and has no issue; the following use product images and show that adding a PVC triggers the error

      quay.io/wildfly/wildfly-s2i-jdk11:latest + PVC --> OK

      After S2I build using builder image `quay.io/wildfly/wildfly-s2i-jdk11:latest` completes and application is deployed, if we connect to the application POD:

      sh-4.4$ ls -l /opt/server/standalone/
total 0
drwxrwxr-x. 1 jboss      root 84 Dec 14 08:15 configuration
drwxrwxr-x. 1 jboss      root 55 Dec 14 08:15 data
drwxrwxr-x. 2 jboss      root 24 Dec 14 08:15 deployments
drwxr-xr-x. 2 1000710000 root 23 Dec 14 08:15 log
drwxr-xr-x. 5 1000710000 root 67 Dec 14 08:15 tmp
sh-4.4$ ls -l /opt/server/standalone/data/
total 0
drwxrwxr-x. 3 jboss      root 16 Dec 14 08:15 content
drwxrwxr-x. 2 jboss      root 26 Dec 14 08:15 kernel
drwxr-xr-x. 2 1000710000 root  6 Dec 14 08:15 timer-service-data
drwxr-xr-x. 3 1000710000 root 35 Dec 14 08:15 tx-object-store
sh-4.4$ ls -l /opt/server/standalone/data/content/
total 0
drwxrwxr-x. 3 jboss root 52 Dec 14 08:15 3a
sh-4.4$ ls -l /opt/server/standalone/data/content/3a/0106200965b83c63b1206f336c9088b9c120b1/content 
-rw-rw-r--. 1 jboss root 13167 Dec 14 08:15 /opt/server/standalone/data/content/3a/0106200965b83c63b1206f336c9088b9c120b1/content

      Note, on the POD, we added a PCV on `/opt/eap/standalone/data`:

            volumeMounts:
        - name: data-dir
          mountPath: /opt/eap/standalone/data
...
  volumes:
    - name: data-dir
      persistentVolumeClaim:
        claimName: data-dir

      registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk11-builder-openshift-rhel8:1.0.0.Beta-8 + PVC --> ERR

      After S2I build using builder image `registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk11-builder-openshift-rhel8:1.0.0.Beta-8` completes and application is deployed, if we connect to the application POD:

      sh-4.4$ ls -l /opt/server/standalone/
total 0
drwxrwxr-x. 2 jboss root 185 Dec 14 09:20 configuration
drwxrwxrwx. 4 root  root  35 Dec 14 09:21 data
drwxrwxr-x. 2 jboss root  24 Dec 14 09:20 deployments
sh-4.4$ ls -l /opt/server/standalone/data/
total 0
drwxr-xr-x. 2 1000710000 root  6 Dec 14 09:21 content
drwxr-xr-x. 2 1000710000 root 26 Dec 14 09:21 kernel
sh-4.4$ ls -l /opt/server/standalone/data/content/
total 0

      and in th server log:

      09:21:59,341 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0057: No deployment content with hash 3a0106200965b83c63b1206f336c9088b9c120b1 is available in the deployment content repository for deployment ROOT.war. Because this Host Controller is booting in ADMIN-ONLY mode, boot will be allowed to proceed to provide administrators an opportunity to correct this problem. If this Host Controller were not in ADMIN-ONLY mode this would be a fatal boot failure.

      Note, on the POD, we added a PCV on `/opt/eap/standalone/data`:

            volumeMounts:
        - name: data-dir
          mountPath: /opt/eap/standalone/data
...
  volumes:
    - name: data-dir
      persistentVolumeClaim:
        claimName: data-dir

      registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk17-builder-openshift-rhel8:latest + PVC --> ERR

      After S2I build using builder image `registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk17-builder-openshift-rhel8:latest` completes and application is deployed, if we connect to the application POD:

      sh-4.4$ ls -l /opt/server/standalone/
total 0
drwxrwxr-x. 2 jboss root 185 Dec 14 09:32 configuration
drwxrwxrwx. 4 root  root  35 Dec 14 09:32 data
drwxrwxr-x. 2 jboss root  24 Dec 14 09:32 deployments
sh-4.4$ ls -l /opt/server/standalone/data
total 0
drwxr-xr-x. 2 1000710000 root  6 Dec 14 09:32 content
drwxr-xr-x. 2 1000710000 root 26 Dec 14 09:32 kernel
sh-4.4$ ls -l /opt/server/standalone/data/content/
total 0

      and in th server log:

      09:33:29,958 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0057: No deployment content with hash 3a0106200965b83c63b1206f336c9088b9c120b1 is available in the deployment content repository for deployment ROOT.war. Because this Host Controller is booting in ADMIN-ONLY mode, boot will be allowed to proceed to provide administrators an opportunity to correct this problem. If this Host Controller were not in ADMIN-ONLY mode this would be a fatal boot failure.

      Note, on the POD, we added a PCV on `/opt/eap/standalone/data`:

            volumeMounts:
        - name: data-dir
          mountPath: /opt/eap/standalone/data
...
  volumes:
    - name: data-dir
      persistentVolumeClaim:
        claimName: data-dir

      registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk17-builder-openshift-rhel8:latest NO PVC --> OK

      4. If we repeat the process in (3) but without adding the PCV on `/opt/eap/standalone/data`, everything works fine

      Show
      Here we present 4 scenarios: the first uses upstream image and has no issue; the following use product images and show that adding a PVC triggers the error quay.io/wildfly/wildfly-s2i-jdk11:latest + PVC --> OK After S2I build using builder image `quay.io/wildfly/wildfly-s2i-jdk11:latest` completes and application is deployed, if we connect to the application POD: sh-4.4$ ls -l /opt/server/standalone/ total 0 drwxrwxr-x. 1 jboss root 84 Dec 14 08:15 configuration drwxrwxr-x. 1 jboss root 55 Dec 14 08:15 data drwxrwxr-x. 2 jboss root 24 Dec 14 08:15 deployments drwxr-xr-x. 2 1000710000 root 23 Dec 14 08:15 log drwxr-xr-x. 5 1000710000 root 67 Dec 14 08:15 tmp sh-4.4$ ls -l /opt/server/standalone/data/ total 0 drwxrwxr-x. 3 jboss root 16 Dec 14 08:15 content drwxrwxr-x. 2 jboss root 26 Dec 14 08:15 kernel drwxr-xr-x. 2 1000710000 root 6 Dec 14 08:15 timer-service-data drwxr-xr-x. 3 1000710000 root 35 Dec 14 08:15 tx-object-store sh-4.4$ ls -l /opt/server/standalone/data/content/ total 0 drwxrwxr-x. 3 jboss root 52 Dec 14 08:15 3a sh-4.4$ ls -l /opt/server/standalone/data/content/3a/0106200965b83c63b1206f336c9088b9c120b1/content -rw-rw-r--. 1 jboss root 13167 Dec 14 08:15 /opt/server/standalone/data/content/3a/0106200965b83c63b1206f336c9088b9c120b1/content Note, on the POD, we added a PCV on `/opt/eap/standalone/data`: volumeMounts: - name: data-dir mountPath: /opt/eap/standalone/data ... volumes: - name: data-dir persistentVolumeClaim: claimName: data-dir registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk11-builder-openshift-rhel8:1.0.0.Beta-8 + PVC --> ERR After S2I build using builder image `registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk11-builder-openshift-rhel8:1.0.0.Beta-8` completes and application is deployed, if we connect to the application POD: sh-4.4$ ls -l /opt/server/standalone/ total 0 drwxrwxr-x. 2 jboss root 185 Dec 14 09:20 configuration drwxrwxrwx. 4 root root 35 Dec 14 09:21 data drwxrwxr-x. 2 jboss root 24 Dec 14 09:20 deployments sh-4.4$ ls -l /opt/server/standalone/data/ total 0 drwxr-xr-x. 2 1000710000 root 6 Dec 14 09:21 content drwxr-xr-x. 2 1000710000 root 26 Dec 14 09:21 kernel sh-4.4$ ls -l /opt/server/standalone/data/content/ total 0 and in th server log: 09:21:59,341 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0057: No deployment content with hash 3a0106200965b83c63b1206f336c9088b9c120b1 is available in the deployment content repository for deployment ROOT.war. Because this Host Controller is booting in ADMIN-ONLY mode, boot will be allowed to proceed to provide administrators an opportunity to correct this problem. If this Host Controller were not in ADMIN-ONLY mode this would be a fatal boot failure. Note, on the POD, we added a PCV on `/opt/eap/standalone/data`: volumeMounts: - name: data-dir mountPath: /opt/eap/standalone/data ... volumes: - name: data-dir persistentVolumeClaim: claimName: data-dir registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk17-builder-openshift-rhel8:latest + PVC --> ERR After S2I build using builder image `registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk17-builder-openshift-rhel8:latest` completes and application is deployed, if we connect to the application POD: sh-4.4$ ls -l /opt/server/standalone/ total 0 drwxrwxr-x. 2 jboss root 185 Dec 14 09:32 configuration drwxrwxrwx. 4 root root 35 Dec 14 09:32 data drwxrwxr-x. 2 jboss root 24 Dec 14 09:32 deployments sh-4.4$ ls -l /opt/server/standalone/data total 0 drwxr-xr-x. 2 1000710000 root 6 Dec 14 09:32 content drwxr-xr-x. 2 1000710000 root 26 Dec 14 09:32 kernel sh-4.4$ ls -l /opt/server/standalone/data/content/ total 0 and in th server log: 09:33:29,958 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0057: No deployment content with hash 3a0106200965b83c63b1206f336c9088b9c120b1 is available in the deployment content repository for deployment ROOT.war. Because this Host Controller is booting in ADMIN-ONLY mode, boot will be allowed to proceed to provide administrators an opportunity to correct this problem. If this Host Controller were not in ADMIN-ONLY mode this would be a fatal boot failure. Note, on the POD, we added a PCV on `/opt/eap/standalone/data`: volumeMounts: - name: data-dir mountPath: /opt/eap/standalone/data ... volumes: - name: data-dir persistentVolumeClaim: claimName: data-dir registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk17-builder-openshift-rhel8:latest NO PVC --> OK 4. If we repeat the process in (3) but without adding the PCV on `/opt/eap/standalone/data`, everything works fine

      The error happens when building an application image using S2I with the following images:

      • registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk11-builder-openshift-rhel8:1.0.0.Beta-8
      • registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-8-tech-preview-eap8-openjdk17-builder-openshift-rhel8:latest

      If in the final application POD we add a PVC, e.g.:

      kind: Pod
apiVersion: v1
metadata:
  ...
  name: eap-jms-1-46njg
  ...
spec:
  ...
  containers:
    - resources: {}
      name: eap-jms
      ...
      volumeMounts:
        - name: data-dir
          mountPath: /opt/eap/standalone/data
      image: >-
        image-registry.openshift-image-registry.svc:5000/amq-tb-1-bm/eap-jms@sha256:bed91f404a29d215196bc620eea73cd31ff6eb34f0f92c1a3b39c33e46f65082
  serviceAccount: default
  volumes:
    - name: data-dir
      persistentVolumeClaim:
        claimName: data-dir
...

      we get the following error:

      09:33:29,958 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0057: No deployment content with hash 3a0106200965b83c63b1206f336c9088b9c120b1 is available in the deployment content repository for deployment ROOT.war. Because this Host Controller is booting in ADMIN-ONLY mode, boot will be allowed to proceed to provide administrators an opportunity to correct this problem. If this Host Controller were not in ADMIN-ONLY mode this would be a fatal boot failure.

      looks like the deployment in the application image is overridden by the volumeMounts.

      The issue was spotted in APPSINT test Eap8AmqBrokerSslTest.

              yborgess1@redhat.com Yeray Borges Santana
              tborgato@redhat.com Tommaso Borgato
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: