-
Bug
-
Resolution: Done
-
Blocker
-
quay-v3.4.0
-
False
-
False
-
Quay Enterprise
-
Undefined
-
Description of problem:
Quay build manager cannot launch build worker on openshift due to verify openshift cert failure
Version-Release number of selected component (if applicable):
registry-proxy.engineering.redhat.com/rh-osbs/quay-quay@sha256:c0d9ebd1e83b300579bf01dc3d6cf4104adb1f8c93b1e7c5ddbc0a09df3c8eb1
registry-proxy.engineering.redhat.com/rh-osbs/quay-quay:v3.4.0-24
How reproducible:
Always
Steps to Reproduce:
1.Deploy Quay by operator
2.Create build trigger
3.Check build status
Actual results:
build is stuck due to no build worker launched
Expected results:
build is completed with ephemeral build worker
Additional info:
build manager config:
FEATURE_BUILD_SUPPORT: True
BUILD_MANAGER:
- ephemeral
- ALLOWED_WORKER_COUNT: 10
ORCHESTRATOR_PREFIX: buildman/production/
ORCHESTRATOR:
REDIS_HOST: quay-test-quay-redis
EXECUTORS:
- EXECUTOR: kubernetes
NAME: openshift
QUAY_USERNAME: root
QUAY_PASSWORD: quayroot
WORKER_IMAGE: brew.registry.redhat.io/rh-osbs/quay-quay-builder
WORKER_TAG: v3.4.0-6
SETUP_TIME: 180 # Time the instance has to start # Number of tries remaining the job needs to use this executor
MINIMUM_RETRY_THRESHOLD: 1 # Container VM image (Kubernetes specific)
BUILDER_VM_CONTAINER_IMAGE: brew.registry.redhat.io/rh-osbs/quay-quay-builder-qemu-rhcos:v3.4.0-1 # Kubernetes resource options
VERIFY_TLS: false
K8S_API_SERVER: api.quay-414.qe.devcluster.openshift.com:6443
VOLUME_SIZE: 8G
KUBERNETES_DISTRIBUTION: openshift
CONTAINER_MEMORY_LIMITS: 5120Mi
CONTAINER_CPU_LIMITS: 1000m
#CONTAINER_MEMORY_REQUEST: 3968Mi
#CONTAINER_CPU_REQUEST: 500m
NODE_SELECTOR_LABEL_KEY: node.kubernetes.io/instance-type
NODE_SELECTOR_LABEL_VALUE: m4.4xlarge
SERVICE_ACCOUNT_NAME: kubeadmin
SERVICE_ACCOUNT_TOKEN: c86gI-9Hwt
- causes
-
-
- Closed
-
- is documented by
-
-
- Closed
-
