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

Documentation feedback: namespace selecton on openstack watcher installation

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • rhos-18.0.7
    • rhos-18.0.6
    • documentation
    • None
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • None
    • Workload Evolution Sprint 2
    • 1
    • Moderate

      When [installing watcher-operator|https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_Enterprise_Linux_OpenStack_Platform/-/blob/rhoso180-antelope/common/optimize/proc_install-watcher-operator.adoc,] on step 1, we include the namespace on the yaml file, to ensure that it is created on the correct one.

       

      But, when [creating the certificates|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,] step 4, we are not including it and step 5 do not add `-n openstack` to the command, so if you are not in the opestack namespace, the certificate will be created on the default namespace.

       

      We can fix it adding `namespace: openstack` to the certificates yaml file and also in the watcher yaml file to avoid the same error (watcher oc apply of point 7 has the -n openstack parameter, so it is not going to fail, but better having in both files).

       

      This is also valid for upstream docs: https://openstack-k8s-operators.github.io/watcher-operator/#_deploying_the_watcher_service

       

              grakausk@redhat.com Greg Rakauskas
              rhn-support-dsanzmor David Sanz Moreno
              rhos-workloads-evolution
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: