V4.0.6 Fix List for Financial Transaction Manager for Red Hat OpenShift

Batch rejected after doing DB2 failover with no reason given.
During db2 failover, on very rare occasions, a batch is rejected without an error code assigned, and it is marked as not overrideable. 

Issue when overriding a file (or batch) using "Accept" with revalidation

After file (or batch) ingestion, if an error occurs (example: duplicate file/batch); if you try to override the file/batch using "Accept" with revalidation, then items in this file are marked incorrectly with the validation error flag.

A Db2 Pod restart (failover) during ingestion, may cause some ingested files to be flagged as duplicaes
A Db2 Pod restart (failover) during ingestion, may cause some ingested files to be flagged as duplicates because the auto-recovery process does not clear the gateway duplicate detection records before restarting the ingestion of these files.

Setting the environment variable TZ in the FTM operator yaml file is not working for j2se pods

FTM operator is ignoring the spec.scheduling configuration

User is not able to set spec.scheduling to configure the OpenShift scheduling for FTM pods.

“oc explain” command not working for FTM CRD

The user is unable to run the “oc explain” command to get a description of the fields in the FTM CRD.

The user is not able to mount custom volumes in FTM pods.

A user cannot mount custom volumes, such as config maps, secrets, PVCs, or other types of volumes, into any of the FTM pods.

The FTM operator ignores the exclude clause once the FTM instance is deployed.

Once FTM is deployed, the FTM operator ignores the init container exclude clause. If a user adds a pod to the exclude clause, the FTM operator will not remove the init container from that pod.

Users cannot scale down individual pods after deployment.

Users cannot scale down individual pods after deployment. If they try, errors show up in the FTM operator log.

Unable to customize FTM pod security context.

Users are not able to customize the security context for FTM pods. For example, it is not possible to specify the uid or gid that the FTM pods run as.

FTM documentation erroneously includes quotes around the values in the sample vars.env file.

The values in the vars.env file must not be enclosed in quotes. The FTM documentation erroneously includes quotes around the sample vars.env file.

FTM instance status stays as Ready when the user makes updates to the instance.

When FTM is deployed and the operator has finished reconciling the custom resource, the CR's status changes to "Ready." If the customer updates the CR again, the status stays as Ready. Once the instance is reconciled, the status should change to NotReady and then back to Ready.

FTM web-server is not getting TLS secret from the external vault.

If the user is getting the TLS certificates from an external vault, then the artifacts web server needs to configure TLS with those certs. Currently, it only configures TLS with certificates from OpenShift.

Updated AdjustmentRuleUtility.getAdjustmentRule(long,long,short).

There is a line of code where we retrieve the user default value for the insert amount, but we weren't passing the configured default amount to the method, so it didn't recognize the need to use the configured default amount instead of the current amount.