Known issues and limitations for Data Privacy (Masking flow)

The following known issues and limitations apply to Masking flow.

Known issues

Limitations

Known issues

When upgrading, you may need to run patches if the horizontal pod autoscaling (HPA) feauture is enabled

Applies to: 5.2.0 and later

If you have the horizontal pod autoscaling (HPA) feature enabled and you are upgrading to 5.1.x, you will need to run the following patch commands:

oc patch -n ${cpd_instance_ns} crd dp.dp.cpd.ibm.com --type='json' -p '[{"op": "replace", "path": "/spec/versions/0/schema/openAPIV3Schema/properties/spec/properties/autoScaleConfig/type", "value": "string"}, {"op": "replace", "path": "/spec/versions/0/schema/openAPIV3Schema/properties/spec/properties/autoScaleConfig/default", "value": "false"}]'

oc patch -n ${cpd_instance_ns} dp dp-cr -p '{"spec":{"autoScaleConfig":"false"}}' --type=merge

Where {cpd_instance_ns} is the project where Data Privacy is installed.

CreateContainerError cause problems to run Bulk copy jobs

Applies to: 5.2.0

If you're using a CSI-based storage type with volumes of large number of files, consider disabling SELinux relabeling. SELinux relabeling can cause a CreateContainerError that can prevent you from running bulk jobs. This error is also known to happen when the Red Hat OpenShift Container Platform is upgraded from 4.12 to 4.14 release. To disable SELinux relabeling, see the steps specific for Data Privacy service in the Disabling SELinux relabeling topic.

Details for masked columns display incorrectly

Applies to: 5.2.0
Fixed in: 5.2.1

In the asset preview page, which is known to happen for virtualized join views and watsonx.data connected data, the value for the Masked columns displays an incorrect count. In addition, the masked indicator icon image A masked columns indicator icon is either missing or incorrectly displayed from the header of columns with masked data. For details, see the Known issues and limitations for IBM Knowledge Catalog.

Data Privacy (Masking flow) is not FIPS-compliant

Applies to: 5.2.0 and later
Fixed in: 5.2.2

Data Privacy (Masking flow) is not Federal Information Processing Standards (FIPS) compliant.

Limitations

Cannot truncate CHAR data type for Teradata in masking flow

Applies to: 5.2.0

Masking flow job fail as CHAR data type cannot truncate for Teradata relational database. For example, the masking flow job fails with the following error message:

Character data truncation detected for the field <COLUMN_NAME>. The length of the value is 44 and the length of the target column is 26. (error code: INVALID_DATA)

The masked data output contains extra space padding even after the library truncates the data.

A screen capture highlighting the masked data output containing extra space padding.

Tip:

This issue is not applicable to VARCHAR data type for Teradata or CHAR data types for Db2 relational databases.