------------------------------------------------------------------------------- Fix Number: 6.1.1 Fujitsu Enterprise Postgres 14 Operator for Kubernetes * Release date - July 5, 2024 ------------------------------------------------------------------------------- [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 2024 FUJITSU LIMITED ------------------------------------------------------------------------------- * Purpose - Populating Enterprise Postgres Periodic Patches It incorporates the following modifications:. For more information, please see Fixes for FUJITSU Enterprise Postgres. - for x86_64 - FJSVfsep-SV-14-1401-11.el8.x86_64 - FJSVfsep-CL-14-1401-8.el8.x86_64 - FJSVfsep-POOL2-14-1401-2.el8.x86_64 - Populating Container's Base OS Image Vulnerability Patches * Target of correction(image tag name) - Operator Container(v6.1.1) - Database Server Container(ubi8-14-1.26) - Backup Container(ubi8-14-1.26) - Restore Container(ubi8-14-1.26) - PGPool2 Container(ubi8-14-1.26) - Exporter Container(ubi9-16-1.1) - Fluentd Container(ubi9-16-1.1) - Fluentbit Container(ubi9-16-1.1) - Upgrade Container(ubi8-14-1.25) - Cronjob Container(ubi9-16-1.1) * FUJITSU Enterprise Postgres client - for x86_64 - FJSVfsep-CL-14-1401-7.el7.x86_64.rpm - FJSVfsep-CL-14-1401-8.el8.x86_64.rpm - FJSVfsep-JDBC-14-1401-7.el7.x86_64.rpm - FJSVfsep-JDBC-14-1401-8.el8.x86_64.rpm - FJSVfsep-ODBC-14-1401-7.el7.x86_64.rpm - FJSVfsep-ODBC-14-1401-8.el8.x86_64.rpm - for Windows(64bit) - FJSVfsep-ADMIN4-1401-7.msi - FJSVfsep-CL-1401-7.msi - FJSVfsep-DOTNET-1401-7.msi - FJSVfsep-JDBC-1401-7.msi - FJSVfsep-Npgsql-1401-7.msi - FJSVfsep-ODBC-1401-7.msi - for Windows(32bit) - FJSVfsep-CL-1401-7.msi - FJSVfsep-DOTNET-1401-7.msi - FJSVfsep-JDBC-1401-7.msi - FJSVfsep-Npgsql-1401-7.msi - FJSVfsep-ODBC-1401-7.msi ------------------------------------------------------------------------------- [Accumulated Patches] The following fixes are included in this patch: Fix Number: 5.2.4 01 PH23800 [ ]Security failure [ ]Serious failure ([ ]Degradation) [*]Incompatibility does not exist / [ ]Incompatibility exists - Frequency ([*]Always / [ ]Rarely / [ ]Irregularly) - Description After deploying the FEPCluster custom resource, the FEP server container is not created and the FEPCluster custom resource displays the following error message: Message: Failed to create object: b'{""kind"":""Status"",""apiVersion"":""v1"",""metadata"": {},""status"":""Failure"",""message"":""admission webhook \\""webhook.cert-manager.io\\"" denied the request: json: cannot unmarshal string into Go struct field CertificateSpec.spec.dnsNames of type []string"",""reason"":""BadRequest"",""code"":400}\n' - Requirements to reproduce this issue 1)cert-manager is installed. and 2)Install Operator v5.1.8 or later. and 3)Apply FEPCluster Custom Resources - Action Changing the definition location so that the Role is created with the correct name. - Compatibility Information None. Fix Number: 5.2.3 01 PH23705 [ ]Security failure [ ]Serious failure ([ ]Degradation) [*]Incompatibility does not exist / [ ]Incompatibility exists - Frequency ([*]Always / [ ]Rarely / [ ]Irregularly) - Description If the restart option of the FEPAction custom resource causes the database to restart, the following message is printed to the database container log and the restart fails: FATAL: data directory ""/database/userdata/data"" has invalid permissions DETAIL: Permissions should be u=rwx (0700) or u=rwx,g=rx (0750). - Requirements to reproduce this issue 1)Apply the FEPCluster custom resource to create the FEP server container. and 2)Restart kubelet on the Kubernetes node where the FEP server container is deployed. and 3)Run the restart option for the FEPAction custom resource - Action By changing the DB pod volume permission and ownership change policy to a policy that changes only when the permissions set for the volume do not match, the data folder permission change is suppressed during volume mount processing. - Compatibility Information None. -------------------------------------------------------------------------------