-------------------------------------------------------------------------------
Fix Number: CG-8.1.2
     Fujitsu Enterprise Postgres 
         with Cryptographic Module 18 Operator for Kubernetes

 * Release date
   - March 16, 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
   - Providing fixes for the existing bugs
   
   - Supports OCP4.20
   
   - Populating Container's Base OS Image Vulnerability Patches

 * Target of correction(image tag name)
   - Operator Container(v8.1.2)
   - Database Server Container(ubi9-18-1.2)
   - Backup Container(ubi9-18-1.2)
   - Restore Container(ubi9-18-1.2)
   - PGPool2 Container(ubi9-18-1.2)
   - Exporter Container(ubi9-18-1.2)
   - Fluentd Container(ubi9-18-1.2)
   - Fluentbit Container(ubi9-18-1.2)
   - Cronjob Container(ubi9-18-1.2)
   - Upgrade Container(ubi9-18-1.2)
   - Utils Container(ubi9-18-1.2)


-------------------------------------------------------------------------------
[Patch Description]

 The following fixes are included in this patch:

Fix Number: CG-8.1.2
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.