"Open Storage WORM lock error" when trying to extend WORM lock image to infinity retention level.

Problem

A WORM lock image cannot be extended to infinity retention level.
Image Cleanup job fails with Status 88, Open Storage lock error.

Error Message

When trying to extend a WORM locked image to infinity retention level, the command returns "Open Storage WORM lock error".

# bpexpdate -backupid xxxxxxx2_1703595712 -d infinity -copy 1 -extend_worm_locks
Are you SURE you want to change xxxxxxx2_1703595712 copy 1 to NEVER expire y/n (n)? y
Open Storage WORM lock error

Indelible attribute of the image is set to pending:

# bpimagelist -backupid xxxxxxx2_1703595712 -L

Client:            xxxxxxx2
Backup ID:         xxxxxxx2_1703595712
(snip)
Expiration Time:             INFINITY       (32535212400)
Maximum Expiration Time:             INFINITY       (32535212400)
(snip)
Fragment Flags:            0x8004    (WORM locked immutable)
 Media Descriptor:        1;PureDisk;worm2.xxxxx.veritas.com;WORM_DP;PureDiskVolume;0
 Expiration Time:            INFINITY       (32535212400)
 MPX:              0
 retention_lvl:    1 day (11)
 Try to Keep Time:  Thu 01 Jan 1970 09:00:00 AM JS (0)
 Copy Creation Time:  Tue 26 Dec 2023 10:02:06 PM JS (1703595726)
 Data Format:      Tar
Copy 1 Flags:            0x12 WORM_LOCK_PENDING IMMUTABLE
 Copy WORM Unlock Time: Wed 27 Dec 2023 10:02:06 PM JS (1703682126)
(snip)

Image Cleanup job fails with the following error:

Critical bpdm(pid=xxxxx)Failed to set WORM immutable and indelible lock for image:xxxxxxx2_1703595712_C1_IM with status:2060065 WORM invalid max
OpenStorage WORM lock error.  (88)
 

Cause

It is not possible to extend a WORM lock image to infinity retention level, because the image expiration date cannot exceed the configured worm-max retention period.
 

Solution

When extending a WORM locked image, do not use "infinity" retention level. The expiration date must be within the WORM retention policy.

In order to view the WORM retention policy, open an SSH session to the WORM storage server as the msdpadm user and run the following command:
> setting WORM status

If the issue has already been encountered, set the image expiration period to fall within the WORM retention policy.

# bpexpdate -backupid xxxxxxx2_1703595712 -d 02/04/24 23:01:56 -copy 1 -extend_worm_locks
Are you SURE you want to change xxxxxxx2_1703595712 copy 1
to expire on Sun 04 Feb 2024 11:01:56 PM JS y/n (n)? y

Check if the indelible attribute is still showing as pending: 
# bpimagelist -backupid xxxxxxx2_1703595712 -L | grep PENDING
#