Known issues and limitations for Data Privacy (Masking flow)

Can't enable the horizontal pod autoscaling (HPA) configuration without upgrading and applying patches

Applies to: 5.3.0 and later

You can't enable the HPA configuration with the UI or API.

Workaround: You must disable the configuration and upgrade to 5.1.0 or later, and then enable the HPA with the following oc patch commands.

1. Disable HPA.
   {cpd_instance_ns} is the project where Data Privacy is installed.

   1. Run the command:

      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"}]'
      

   2. Run the command:

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

2. Upgrade your instance.

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

   1. Run the command:

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

   2. Run the command:

      oc patch dp dp-cr -p '{"spec":{"autoScaleConfig":true}}' --type=merge
      

CreateContainerError causes problems with running Bulk copy jobs

Applies to: 5.3.0 and later

If you're using a CSI-based storage type with volumes of large number of files, SELinux relabeling might cause a CreateContainerError error that might prevent you from running bulk jobs.

This error is also appears when the Red Hat OpenShift Container Platform is upgraded from 4.12 to 4.14 release.

Workaround: Consider disabling SELinux relabeling. To disable SELinux relabeling, see the steps specific for Data Privacy service in Disabling SELinux relabeling.

Cannot truncate CHAR data type for Teradata in masking flow

Applies to: 5.3.0 and later

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.