------------------------------------------------------------------------------- Fix Number: 8.3.3 Fujitsu Enterprise Postgres 17 Operator for Kubernetes * Release date - July 15, 2026 ------------------------------------------------------------------------------- [High Risk Activity] The Customer acknowledges and agrees that the Product is designed, developed and manufactured as contemplated for general use, including without limitation, general office use, personal use, household use, and ordinary industrial use, but is not designed, developed and manufactured as contemplated for use accompanying fatal risks or dangers that, unless extremely high safety is secured, could lead directly to death, personal injury, severe physical damage or other loss (hereinafter "High Safety Required Use"), including without limitation, nuclear reaction control in nuclear facility, aircraft flight control, air traffic control, mass transport control, medical life support system, missile launch control in weapon system. The Customer, shall not use the Product without securing the sufficient safety required for the High Safety Required Use. In addition, Fujitsu (or other affiliate's name) shall not be liable against the Customer and/or any third party for any claims or damages arising in connection with the High Safety Required Use of the Product. Product and company names mentioned in this manual are the trademarks or registered trademarks of their respective owners. Copyright 2026 FUJITSU LIMITED ------------------------------------------------------------------------------- * Purpose - Enterprise Postgres Emergency Patches It incorporates the following modifications. For more information, please see Fixes for Fujitsu Enterprise Postgres. - for x86_64 - FJSVfsep-SV-17-1702-5.el9.x86_64 - FJSVfsep-CL-17-1702-5.el9.x86_64 - FJSVfsep-POOL2-17-1702-5.el9.x86_64 - Providing fixes for the existing bugs * Target of CPU architecture [*] x86 [ ] s390x [ ] ppc64le * Target of correction(image tag name) - Operator Container(v8.3.3) - Database Server Container(ubi9-17-3.9) - Backup Container(ubi9-17-3.9) - Restore Container(ubi9-17-3.9) - PGPool2 Container(ubi9-17-3.9) - Exporter Container(ubi9-18-3.2) - Fluentd Container(ubi9-18-3.2) - Fluentbit Container(ubi9-18-3.2) - Upgrade Container(ubi9-17-3.9) - Cronjob Container(ubi9-18-3.2) - Utils Container(ubi9-17-3.9) * Fujitsu Enterprise Postgres client - for x86_64 - FJSVfsep-CL-17-1702-5.el8.x86_64.rpm - FJSVfsep-CL-17-1702-5.el9.x86_64.rpm - FJSVfsep-CL-17-1702-5.s15.x86_64.rpm - FJSVfsep-DOTNET-17-1702-5.el8.x86_64.rpm - FJSVfsep-DOTNET-17-1702-5.el9.x86_64.rpm - FJSVfsep-DOTNET-17-1702-5.s15.x86_64.rpm - FJSVfsep-JDBC-17-1702-5.el8.x86_64.rpm - FJSVfsep-JDBC-17-1702-5.el9.x86_64.rpm - FJSVfsep-JDBC-17-1702-5.s15.x86_64.rpm - FJSVfsep-ODBC-17-1702-5.el8.x86_64.rpm - FJSVfsep-ODBC-17-1702-5.el9.x86_64.rpm - FJSVfsep-ODBC-17-1702-5.s15.x86_64.rpm - FJSVfsep-PSYPG-17-1702-5.el8.x86_64.rpm - FJSVfsep-PSYPG-17-1702-5.el9.x86_64.rpm - FJSVfsep-PSYPG-17-1702-5.s15.x86_64.rpm - for Windows(64bit) - FJSVfsep-ADMIN4-1702-5.msi - FJSVfsep-CL-1702-5.msi - FJSVfsep-DOTNET-1702-5.msi - FJSVfsep-JDBC-1702-5.msi - FJSVfsep-ODBC-1702-5.msi - FJSVfsep-PSYPG-1702-5.msi - for Windows(32bit) - FJSVfsep-CL-1702-5.msi - FJSVfsep-DOTNET-1702-5.msi - FJSVfsep-JDBC-1702-5.msi - FJSVfsep-ODBC-1702-5.msi - FJSVfsep-PSYPG-1702-5.msi ------------------------------------------------------------------------------- [Patch Description] The following fixes are included in this patch: Fix Number: 8.3.3 01 PH25494 [ ]Security failure [ ]Serious failure ([ ]Degradation) [*]Incompatibility does not exist / [ ]Incompatibility exists - Frequency ([*]Always / [ ]Rarely / [ ]Irregularly) - Description When restoring to a new database cluster, certain parameters of the source FEPCluster custom resource were not propagated to the destination FEPCluster custom resource. - Requirements to reproduce this issue This issue occurs when all of the following conditions are met: One or more of the following parameters are specified in the source FEPCluster custom resource: - spec.fep.fepEnvSec - spec.fep.fepcronjob - spec.globalEnvSec - spec.ldap2pg - spec.ldap - Action Modified the restore process so that the parameters of the source FEPCluster custom resource are propagated to the destination FEPCluster custom resource. - Compatibility Information None. ------------------------------------------------------------------------------- [Accumulated Patches] The following fixes are included in this patch: Fix Number: 8.3.0 01 PH25428 [ ]Security failure [*]Serious failure ([*]Degradation) [*]Incompatibility does not exist / [ ]Incompatibility exists - Frequency ([*]Always / [ ]Rarely / [ ]Irregularly) - Description When a database cluster is created using Operator version v8.2.0 or later, the -vectorizer-cert Secret resource is not created during recovery using Velero, causing the creation of the target database cluster to fail. Error Message: When the FEPCluster custom resource name is new-fep, it is as follows: Warning FailedMount 2m22s (x10 over 20m) kubelet Unable to attach or mount volumes: unmounted volumes=[fep-vectorizer-tls], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition Warning FailedMount 29s (x19 over 22m) kubelet MountVolume.SetUp failed for volume "fep-vectorizer-tls" : secret "new-fep-vectorizer-cert" not found - Requirements to reproduce this issue 1) Automatic certificate generation is enabled, and 2) The Operator version v8.2.0 or later is installed, and 3) A FEPCluster custom resource is created with spec.fep.velero.enable set to true, and 4) A backup is executed using the velero backup create command with the --selector option set to either the values specified in spec.fep.velero.labels of the FEPCluster custom resource, or, if spec.fep.velero.labels is not specified, velero-backup: "fep-velero", and 5) In the target recovery environment, Velero is used to perform the recovery and restore the database cluster - Action The conditions have been modified so that the target Secret resources are recreated in the restore destination. - Compatibility Information None. Fix Number: 8.2.2 01 PH25288 [ ]Security failure [*]Serious failure ([*]Degradation) [*]Incompatibility does not exist / [ ]Incompatibility exists - Frequency ([*]Always / [ ]Rarely / [ ]Irregularly) - Description After upgrading the Operator to version 8.2.0, the following error is displayed for all existing FEPClusterCRs, causing the process to terminate abnormally. As a result, processing does not continue beyond that point. Error Message: Description of query: Unexpected templating type error occurred on ({ { validate_fepvol.diff.after | json_query("spec.*.size") | length }}) : object of type 'NoneType' has no len(). object of type 'NoneType' has no len() - Requirements to reproduce this issue 1) Create an FEPClusterCR in an environment where an operator version prior to v8.2.0 is installed. and 2) Upgrade the operator to v8.2.0 - Action Added a condition to the FEPVolume update process so that it is triggered only when differences exist under the spec field. - Compatibility Information None. Fix Number: 8.2.0 01 PH25181 [ ]Security failure [ ]Serious failure ([ ]Degradation) [*]Incompatibility does not exist / [ ]Incompatibility exists - Frequency ([*]Always / [ ]Rarely / [ ]Irregularly) - Description When performing an operation that restarts a database Pod, the restart fails and the following error is output to the Operator Pod log. Error Message: TASK [subtask-restart-cluster:ngs-service-test-pod-restart-all-177182 2876-pod_restart_all - Set switchover result and concatenate switchover message to ops_result_msg] ******************************* fatal: [localhost]: FAILED! => { "msg": "The task includes an option with an undefined variable.. 'dict object' has no attribute 'rc' The error appears to be in '/opt/ansible/roles/fepaction/tasks/ subtask-restart-cluster.yaml': line 165, column 7, but may be elsewhere in the file depending on the exact syntax problem. - Requirements to reproduce this issue Condition 1) 1)The Operator version is v8.1.1, and 2)The database is created with the following settings in the FEPCluster custom resource: - spec.fep.instances is set to 2 or more, and 3)A FEPAction custom resource is executed with the following settings to restart Pods: - spec.fepAction.type: pod_restart - spec.fepAction.args: ALL, or the name of the master Pod at the time of execution or Condition 2) 1)The Operator version is v8.1.1, and 2)The database is created with the following settings in the FEPCluster custom resource: - spec.fep.instances is set to 2 or more - spec.fep.autoPodRestart is omitted or set to true, and 3)One of the following fields in the FEPCluster custom resource is updated: - spec.fep.image.image - spec.fep.mcSpec - spec.fepChildCrVal.backup.image.image - spec.fepChildCrVal.backup.mcSpec - spec.fep.remoteLogging - spec.fep.feputils.image - FEPExporter.spec.fepExporter.image.image - spec.fep.fixedStats.* - spec.fep.multiMasterReplication When the operations in Condition 2 are performed, the Operator automatically creates a FEPAction custom resource that satisfies the conditions in Condition 1 and restarts the Pods. As a result, the same issue may occur. - Action Remove the execution condition for the Patroni connection information acquisition process. - Compatibility Information None. Fix Number: 7.3.0 01 PH24794 [ ]Security failure [*]Serious failure ([ ]Degradation) [*]Incompatibility does not exist / [ ]Incompatibility exists - Frequency ([*]Always / [ ]Rarely / [ ]Irregularly) - Description If the automatic certificate generation function is enabled and restoration is performed to a new cluster, the connection to the restore-destination cluster using the certificate fails. - Requirements to reproduce this issue Condition 1) 1)Install Fujitsu Enterprise Postgres Operator with automatic certificate generation enabled. and 2)Deploy the FEPCluster using the automatic certificate generation feature. and 3)Restore to a new FEPCluster or Condition 2) 1)Install Fujitsu Enterprise Postgres Operator with certificate auto-generation enabled or disabled. and 2)Deploy the FEPCluster using its own certificate with the FEPCluster name listed in the certificate as CommonName. 3)Restore to a new FEPCluster - Action Fix the program for rewriting the definition of the FEPCluster custom resource at the restore destination when restoring to a new cluster using a certificate. - Compatibility Information None. Fix Number: 7.2.7 01 PH24727 [ ]Security failure [*]Serious failure ([ ]Degradation) [*]Incompatibility does not exist / [ ]Incompatibility exists - Frequency ([*]Always / [ ]Rarely / [ ]Irregularly) - Description Applying the FEPCluster custom resource fails to deploy the database cluster. The FEPCluster custom resource displays the following error message. message: |- MODULE FAILURE: No start of json char found See stdout/stderr for the exact error - Requirements to reproduce this issue 1)Kubevirt is installed on the platform. and 2)The Fujitsu Enterprise Postgres Operator is installed. and 3)Apply FEPCluster custom resources - Action Incorporate a plugin that has been modified to correctly retrieve operator Kubernetes resource information. - Compatibility Information None. -------------------------------------------------------------------------------