-
Bug
-
Resolution: Done
-
Major
-
None
-
quay-v3.7.0
Description of problem:
In build official document, there is a DEBUG config flag, when set to true, DEBUG will prevent the build nodes from shutting down after the quay-builder service is done or fails.
In kubernetesPodman build executor environment, set DEBUG as true, when the quay-builder service failed, the pods will gone.
Version-Release number of selected component (if applicable):
quay-operator-bundle-container-v3.7.0-98
Index image v4.8: registry-proxy.engineering.redhat.com/rh-osbs/iib:221490 quay-operator-rhel8@sha256:7e54a746b2a705e7d0ef76f7cdf1876ad4a320d2fd92f91dce0727e08db6a58d
How reproducible:
always
Steps to Reproduce:
1. enable build with kubernetesPodman executor and set DEBUG:true
BUILDMAN_HOSTNAME: quayregistry-quay-builder-quay-enterprise.apps.whu48az7.qe.azure.devcluster.openshift.com:443 BUILD_MANAGER: - ephemeral - ALLOWED_WORKER_COUNT: 20 ORCHESTRATOR_PREFIX: buildman/production/ ORCHESTRATOR: REDIS_HOST: quayregistry-quay-redis REDIS_PASSWORD: "" REDIS_SSL: false REDIS_SKIP_KEYSPACE_EVENT_SETUP: false EXECUTORS: - EXECUTOR: kubernetesPodman DEBUG: true NAME: openshift BUILDER_NAMESPACE: virtual-builds SETUP_TIME: 180 MINIMUM_RETRY_THRESHOLD: 1 QUAY_USERNAME: '..6' QUAY_PASSWORD: ey.....5cc8 BUILDER_CONTAINER_IMAGE: brew.registry.redhat.io/rh-osbs/quay-quay-builder-rhel8:v3.7.0 # Kubernetes resource options K8S_API_SERVER: api.whu48az7.qe.azure.devcluster.openshift.com:6443 K8S_API_TLS_CA: /conf/stack/extra_ca_certs/build_cluster.crt VOLUME_SIZE: 8G KUBERNETES_DISTRIBUTION: openshift CONTAINER_MEMORY_LIMITS: 300Mi CONTAINER_CPU_LIMITS: 1000m CONTAINER_MEMORY_REQUEST: 300Mi CONTAINER_CPU_REQUEST: 500m NODE_SELECTOR_LABEL_KEY: "" NODE_SELECTOR_LABEL_VALUE: "" SERVICE_ACCOUNT_NAME: quay-builder SERVICE_ACCOUNT_TOKEN: e.....5zxqAGAMjgc USERFILES_LOCATION: default USERFILES_PATH: userfiles
2. trigger a build process with a invalid Dockerfile
ENV first FROM registry.access.redhat.com/ubi7/ubi USER root LABEL maintainer="whu" # Update image RUN yum update --disableplugin=subscription-manager -y && rm -rf /var/cache/yum RUN yum install --disableplugin=subscription-manager httpd -y && rm -rf /var/cache/yum # Add default Web page and expose port RUN echo "The Web Server is Running" > /var/www/html/index.html EXPOSE 80 # Start the service CMD ["-D", "FOREGROUND"] ENTRYPOINT ["/usr/sbin/httpd"]
3. start the build, when quay-builder pod failed, wait for a while check the pods again.
Actual results:
The failed quay-builder pods will gone after about 5 minutes later.
Expected results:
The failed quay-builder pods should exist for debug.
Additional info:
$ date Wed Apr 27 08:59:50 UTC 2022 $ oc get all -n virtual-builds NAME READY STATUS RESTARTS AGE pod/3f2fb9d3-a11c-4c19-aa07-6a1337c93242-877kg-2fwj2 0/1 Error 0 20s pod/3f2fb9d3-a11c-4c19-aa07-6a1337c93242-877kg-nxlv8 0/1 Error 0 29s NAME COMPLETIONS DURATION AGE job.batch/3f2fb9d3-a11c-4c19-aa07-6a1337c93242-877kg 0/1 29s 29s $ date Wed Apr 27 09:05:14 UTC 2022 $ oc get all -n virtual-builds No resources found in virtual-builds namespace.
