PITR restore without matching user Secrets doesn't work

[JosefRypacek]

Report

Version 1.18 introduced More resilient database restores without matching user Secrets. I tried 1.19 and tried to restore backup to new cluster with different passwords. It works and changes passwords of system users in the database.
Sadly, this does not work when PITR is enabled on the restore. It gets stucked on starting PXC pod and I verified the database is using passwords from backup and they are different from ones from the secret.
I don't think this is expected behavior as there is no mention in the documentation that this feature is for base restore only.

More about the problem

Steps to reproduce

1. Restore backup with enabled PITR secition to another cluster.

apiVersion: pxc.percona.com/v1
kind: PerconaXtraDBClusterRestore
metadata:
  name: restore-pitr-1
  namespace: pxc-database
spec:
  pxcCluster: pxc-database-recovery
  backupName: cron-pxc-database-origin-s3-pxc-backups-202613012052-6oioo
  pitr:
    type: latest
    backupSource:
      s3:
        bucket: pxc-database-origin/binlogs
        credentialsSecret: pxc-database-backup-s3-creds
        region: eu-frankfurt-1
        endpointUrl: "https://namespace.compat.objectstorage.eu-frankfurt-1.oraclecloud.com"

Versions

1. Kubernetes 1.34
2. Operator 1.19

Anything else?

No response

[egegunes]

@JosefRypacek I reproduced the issue. You're right, it's a bug. I created K8SPXC-1800 to fix this in the next release.