Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-14724

Watcher Operator is not available in Operators catalog in OpenShift web console

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • rhos-18.0.7
    • rhos-18.0 FR 2 (Mar 2025)
    • openstack-watcher
    • None
    • Workload Evolution Sprint 1, Workload Evolution Sprint 2
    • 2
    • Important

      The watcher catalog is not available to be installed from the Operators -> OperatorHub console.

      This operator is intended to be installed as a standalone one while it is in Tecnology Preview status, not as part of OpenStack Operator.

      Workaround is to install it using yaml file.

      Validation

      It should be possible to install the watcher-operator from the openshift console. Steps:

      • Create a new CatalogSource with:
      ---
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      metadata:
        name: watcher-operator-index
        namespace: openstack-operators
      spec:
        image: images.paas.redhat.com/podified-main-rhos-18-rhel-9/watcher-operator-index:trunk-patches-latest
        sourceType: grpc
       
      •  Follow the watcher installation process:

       
      1. Log in to the RHOCP web console as a user with `cluster-admin` permissions.
      2. Select Operators → OperatorHub.
       
      3. In the Filter by keyword field, type `Watcher`. An operator with name "Watcher Operator (Technology Preview)" should appear with the `Red Hat` source label. Click on it.

       
      (in the test there may be two, as the watcher operator seems to be included in the openstack-operator catalog too, this is specific to trunk catalogs, will not appear in non-trunk and public catalog)

       
      4. Read the information about the Operator:
        - Installation mode must be set to `All namespaces in the cluster`.
        - In the Installed Namespace select `openstack-operators`  and click Install.
       The Operator is deployed and ready when the status of the Watcher Operator is Succeeded.
       

      For complete validation, deploy Watcher from this operator to make sure the operator is properly installed following the process documented in https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_Enterprise_Linux_OpenStack_Platform/-/blob/rhoso180-antelope/common/optimize/proc_deploy-optimize-exist-control-plane.adoc

        1. image1.png
          image1.png
          76 kB
        2. image2.png
          image2.png
          8 kB
        3. image-2025-03-19-14-48-59-813.png
          image-2025-03-19-14-48-59-813.png
          23 kB

              rlandy@redhat.com Ronelle Landy
              amoralej1@redhat.com Alfredo Moralejo Alonso
              David Sanz Moreno David Sanz Moreno
              rhos-workloads-evolution
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: