If image-registry-private-configuration secret already exists in openshift-image-registry namespace, creating image-registry-private-configuration-user secret does not take precedence to supply storage account to registry.

4.13.0-0.nightly-2024-04-22-142044 

always

    1.Create image-registry-private-configuration-user secret with incorrect account info
    2.Check registry pod
    3.Update image-registry-private-configuration-user secret with correct account info, then update image-registry-private-configuration secret to the invalid account
    4. Check registry pod

    2.image registry pods are still running, even they are recreated by deleted
    4. registry pods go to crash with account issues.

    image-registry-private-configuration-user should take precedence.

In an cluster which image registry is not installed in day0, user configures registry with customer object storage, image-registry-private-configuration-user is created firstly, then image-registry-private-configuration secret will be created by operator with same account with image-registry-private-configuration-user secret.
But if image registry is installed in day0, image-registry-private-configuration secret created earlier than image-registry-private-configuration-user secret, image-registry-private-configuration will not be updated by creating image-registry-private-configuration-user secret.