Known issues and limitations for Watson OpenScale

Attempt to import settings from pre-prod deployment space fails

If you are assigned the admin or editor role for a deployment space, your attempt to import settings from a pre-prod deployment space might fail.

You can work around this issue by being assigned the admin or editor role for the associated Watson OpenScale instance. You can also login as the cpadmin user to import settings.

Applies to: 5.0.3

Model details fail to display when viewing threshold violation alert notifications

If you are invited to a deployment space as an admin user and send metric threshold violation results to your email address, your attempt to view model details might fail. When you click View model details in your email notification, a WOS instance opens and fails to display model details.

To work around this issue, you must be assigned a collaborator role for the Watson OpenScale service instance that is associated with your deployment space to view model details.

Drift v2 evaluation configuration displays setting that is not enabled

When you configure drift v2 evaluations, you can set a threshold value for the input metadata drift metric even if you did not provide metadata columns to enable the setting.

You can workaround this issue by specifying any threshold value for the input metadrift metric to complete the configuration. The value that you specify does not affect your evaluation results.

Applies to: 5.0.0
Fixed in: 5.0.1

Drift v2 evaluation results summary displays metric that is not calculated

When you review drift v2 evaluation results, the dashboard displays a score for the input metadata drift metric even if you did not provide metadata columns to enable the calculation. This issue does not affect how you can analyze your evaluation results.

Applies to: 5.0.0
Fixed in: 5.0.1

Watson OpenScale fails to restore to a different cluster

After you attempt to restore Watson OpenScale to a different cluster, the service instance might still have the same cluster information. To workaround this issue, you can complete the following steps:

1. Log in to Red Hat OpenShift Container Platform with the following command:

${OC_LOGIN}

2. Change to the project where Watson OpenScale operands are installed and configured.

oc project <Project>

3. Move the Watson OpenScale custom resource to maintenance.

oc patch WOService aiopenscale --type merge --patch '{"spec": {"ignoreForMaintenance": true}}'

4. Delete the service secrets.

oc delete secret aiopenscale-ibm-aios-service-secrets

5. Scale down the service pods.

oc scale deployment -l "component in (aios-bias,aios-bkpi,aios-common,aios-configuration,aios-dashboard,aios-datamart,aios-drift,aios-explainability,aios-fast,aios-feedback,aios-ml,aios-mrm,aios-metrics,aios-notification,aios-payload,aios-scheduling)" --replicas=0

6. Move the Watson OpenScale custom resource out of maintenance.

oc patch WOService aiopenscale --type merge --patch '{"spec": {"ignoreForMaintenance": false}}'

7. Verify that the custom resource reconcilliation completed successfully.

Applies to: 5.0.1
Fixed in: 5.0.3

Parent topic: Service issues