What is the probability and severity of the issue? I.e. the overall risk

Watcher operator is being added as Technology Preview so the impact will be limited and should not hit any production environment.

Said this, the bug affects to the documented installation process for any customer willing to install Watcher which will make it very visible for any potential watcher user.

Fix is simple and it's already merged in main branch.

Does this affect specific configurations, hardware, environmental factors, etc.?

Will affect any customer willing to install Watcher operator.

Are any partners relying on this functionality in order to ship an ecosystem product?

No.

What proportion of our customers could hit this issue?

small, only users trying to deploy watcher for testing purposes.

Does this happen for only a specific use case?

No, this can be reproduced by following the standard documented use of the Telemetry Operator.

What proportion of our CI infrastructure, automation, and test cases does this issue impact?

None. This is not (yet) integrated to our CI infrastructure.

Is this a regression in supported functionality from a previous release?

No.

Is there a clear workaround?

Customers can install the watcher-operator using oc cli and yaml file.

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: watcher-operator
  namespace: openstack-operators
spec:
  name: watcher-operator
  channel: stable-v1.0
  source: redhat-operators
  sourceNamespace: openshift-marketplace
 

Is there potential doc impact?

Yes, this impacts the documented procedure to install the operator. We may add the workaround to the doc.

What's the rationale for the blocker?

While this is affecting only a TechPreview feature and there is a workaround, it affects the installation process which is very visible and the fix is easy and clean.

It may be worthy to include in a respin in case there is one before FR2 release.