Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-2010

Zero-length files in ppc64le plugin registry build due to swap_plugins_memory.sh failure

XMLWordPrintable

    • False
    • False
    • Undefined

      On only ppc4le, there are zero-length files in the plugin registry as of build 2.10-4.

      containerExtract.sh --override-arch ppc64le quay.io/crw/pluginregistry-rhel8:2.10-4
      
      cd /tmp/quay.io-crw-pluginregistry-rhel8-2.10-4-*/var/www/html/v3/plugins/
      find . -type f -name "*.yaml" -exec du {} \; | grep 0
      
      0	./redhat/vscode-openshift-connector/latest/meta.yaml
      0	./redhat/vscode-openshift-connector/latest/che-theia-plugin.yaml
      0	./redhat/vscode-camelk/latest/meta.yaml
      0	./redhat/vscode-camelk/latest/che-theia-plugin.yaml
      0	./ms-python/python/latest/meta.yaml
      0	./ms-python/python/latest/che-theia-plugin.yaml
      0	./eclipse/che-theia/latest/meta.yaml
      0	./eclipse/che-theia/latest/devfile.yaml
      

      But on s390x and x64, these files are not empty:

      podman rmi quay.io/crw/pluginregistry-rhel8:2.10-4 -f
      rm -fr /tmp/quay.io-crw-pluginregistry-rhel8-2.10-4-*
      containerExtract.sh quay.io/crw/pluginregistry-rhel8:2.10-4 --override-arch s390x
      
      cd /tmp/quay.io-crw-pluginregistry-rhel8-2.10-4-*/var/www/html/v3/plugins/
      find . -type f -name "*.yaml" -exec du {} \; | grep 0
      
      podman rmi quay.io/crw/pluginregistry-rhel8:2.10-4 -f
      rm -fr /tmp/quay.io-crw-pluginregistry-rhel8-2.10-4-*
      containerExtract.sh quay.io/crw/pluginregistry-rhel8:2.10-4
      
      cd /tmp/quay.io-crw-pluginregistry-rhel8-2.10-4-*/var/www/html/v3/plugins/
      find . -type f -name "*.yaml" -exec du {} \; | grep 0
      

            yogitakulkarni Yogita Kulkarni (Inactive)
            nickboldt Nick Boldt
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: