-
Bug
-
Resolution: Done
-
Minor
-
quay-v3.7.0
-
1
-
False
-
-
False
Description of problem:
Depending on developer's confirmation, in quay 3.7.0, the operator includes the port 55443. That means, for quay build feature, customer do not need to expose 55443 port manually.
But after deploying quay by quay-operator-bundle-container-v3.7.0-42 build, can not find port 55443 in quay pod definition. The build process will fail when quay-builder dial grpc server in bare metal builder environment.
Version-Release number of selected component (if applicable):
quay-operator-bundle-container-v3.7.0-42
How reproducible:
always
Steps to Reproduce:
1. deploy quay with quay-operator-bundle-container-v3.7.0-42 build by operator
2. After quay pods are running, check the ports setting
Actual results:
$ oc get pod NAME READY STATUS RESTARTS AGE ...... quayregistry-quay-app-65d758c889-26mzn 1/1 Running 0 27m quayregistry-quay-app-65d758c889-9cllh 1/1 Running 1 (26m ago) 26m $ oc get pod quayregistry-quay-app-65d758c889-26mzn -o yaml apiVersion: v1 kind: Pod metadata: ...... spec: containers: - args: - registry-nomigrate .... name: quay-app ports: - containerPort: 8443 protocol: TCP - containerPort: 8080 protocol: TCP - containerPort: 8081 protocol: TCP - containerPort: 9091 protocol: TCP readinessProbe: failureThreshold: 10
Expected results:
55443 port should be exposed by default by operator.
Additional info:
Before exposing 55443 port manually, the quay-builder dial grpc server failed in bare metal builder environment.
$ journalctl -f -u quay-builder -- Logs begin at Tue 2022-03-22 05:47:23 UTC. -- Mar 22 05:48:37 380f5b0a-0a34-4807-bea4-7ed944a8ed86 podman[1430]: Copying config sha256:1a3b859ef54417925c498b044ebbe9e185b4d63039ad1628a71f0e3721004da6 Mar 22 05:48:37 380f5b0a-0a34-4807-bea4-7ed944a8ed86 podman[1430]: Writing manifest to image destination Mar 22 05:48:37 380f5b0a-0a34-4807-bea4-7ed944a8ed86 podman[1430]: Storing signatures Mar 22 05:49:24 380f5b0a-0a34-4807-bea4-7ed944a8ed86 podman[1430]: Copying custom certs to trust if they exist Mar 22 05:49:25 380f5b0a-0a34-4807-bea4-7ed944a8ed86 podman[1430]: time="2022-03-22T05:49:25Z" level=info msg="starting quay-builder: v3.7.0" Mar 22 05:49:25 380f5b0a-0a34-4807-bea4-7ed944a8ed86 podman[1430]: time="2022-03-22T05:49:25Z" level=info msg="connecting to gRPC server...: quayregistry-quay-quay-enterprise.apps.whu410osp5.0322-xzx.qe.rhcloud.com:55443" Mar 22 05:49:35 380f5b0a-0a34-4807-bea4-7ed944a8ed86 podman[1430]: time="2022-03-22T05:49:35Z" level=fatal msg="failed to dial grpc server: context deadline exceeded" Mar 22 05:49:36 380f5b0a-0a34-4807-bea4-7ed944a8ed86 systemd[1]: quay-builder.service: Main process exited, code=exited, status=1/FAILURE Mar 22 05:49:36 380f5b0a-0a34-4807-bea4-7ed944a8ed86 systemd[1]: quay-builder.service: Failed with result 'exit-code'. Mar 22 05:49:36 380f5b0a-0a34-4807-bea4-7ed944a8ed86 systemd[1]: Failed to start quay-builder.service.
After exposing 55443 port manually, the build process is successful
$ oc patch deployment quayregistry-quay-app -n quay-enterprise -p '{"spec": {"template": {"spec": {"containers": [ {"name":"quay-app","ports": [{"containerPort": 55443,"protocol": "TCP"}]}]}}}}'
