Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-636

Quay CR deployment was stuck when specify external access as nodeport

XMLWordPrintable

    • NodePort will not be a supported configuration with the Operator.
    • 0

      Description:
      This is an issue found when use latest Quay operator to deploy Quay CR resource, when configure externalaccess as nodeport in CR file, the Quay CR deployment was stuck, the error message is as the following, the interesting point is Quay operator use the CR name+"-quay-config" as the hostname of Quay config-app, hence can't reach to the expected endpoint.

      "error":"Get https://demonodeport-quayecosystem-quay-config:30101/api/v1/superuser/registrystatus: dial tcp 172.30.92.11:30101: connect: no route to host",

      Quay Operator:
      quay.io/quay/quay-rhel8-operator:1.1.0-1

      Expected Results:
      Quay CR deployment should be completed successfully.

      Actual Results:
      Quay CR deployment was stuck.

      *Quay CR file:*
      lizhang@lzha-mac Quay3.3_operator_testing % cat quayecosystem_cr_nodeport.yaml
      apiVersion: redhatcop.redhat.io/v1alpha1
      kind: QuayEcosystem
      metadata:
      name: demonodeport-quayecosystem
      spec:
      quay:
      imagePullSecretName: redhat-pull-secret
      image: quay.io/quay/quay:v3.3.0-3
      externalAccess:
      type: NodePort
      nodePort: 30100
      configNodePort: 30101
      hostname: quconfig33.apps.lzha0426.qe.gcp.devcluster.openshift.com

      enableRepoMirroring: true
      database:
      volumeSize: 30Gi
      envVars:

      • name: DEBUGLOG
        value: "true"
        clair:
        enabled: true
        image: quay.io/quay/clair-jwt:v3.3.0-1
        imagePullSecretName: redhat-pull-secret
        updateInterval: "60m"

      Quay operator logs, for detailed logs see attachment:

      {"level":"error","ts":1587879262.51259,"logger":"controller_quayecosystem","msg":"Failed to obtain initial registry status","error":"Get https://demonodeport-quayecosystem-quay-config:30101/api/v1/superuser/registrystatus: dial tcp 172.30.92.11:30101: connect: no route to host","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/tmp/quay-operator/vendor/github.com/go-logr/zapr/zapr.go:128\ngithub.com/redhat-cop/quay-operator/pkg/controller/quayecosystem/setup.(*QuaySetupManager).SetupQuay\n\t/tmp/quay-operator/pkg/controller/quayecosystem/setup/setup.go:62\ngithub.com/redhat-cop/quay-operator/pkg/controller/quayecosystem.(*ReconcileQuayEcosystem).Reconcile\n\t/tmp/quay-operator/pkg/controller/quayecosystem/quayecosystem_controller.go:269\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/tmp/quay-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:256\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/tmp/quay-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:232\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/tmp/quay-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:211\nk8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/tmp/quay-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:152\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/tmp/quay-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:153\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/tmp/quay-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88"}

            kmullins@redhat.com Kurtis Mullins (Inactive)
            lzha1981 luffy zhang
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: