Release Notes

6.1.7

Release Date : 10th Feb'2026

What's New?

1. Support for OpenStack Helm Epoxy (2025.1).

2. Support for OpenStack MOSK25.2.

3. Separate Rabbitmq cluster on RHOSO18.0.

4. Separate Galera on RHOSO18.0.

5. Bug fixes:

   • Backups failing due to Unable to connect to cinder volumes.

   • All services log to journald and /var/log/containers is not used at all.

   • Pulling RHOSO containers for YM from the redhat registry mirror.

   • Full backup created at the time which is not present in the policy.

   • Cross tenant snapshot creation for non admin user.

   • Private cloud backup failing with error Failed creating workload snapshot: 'dict' object has no attribute 'done'.

   • Private cloud vm doesn't boot after restore from incremental backup.

   • VM doesn't boot restored via selective restore from backup.

   • Show the Restore ID, VM ID, hostname of the compute node in the restore logs.

   • [API] retention manual value if given empty breaks the policy-list on the horizon.

   • [API] wrong status code: 500 while deleting a workload in locked state.

   • [API+CLI] Listing snapshots of a different project snapshot gives status code of 500.

   • [API+CLI] Creating a snapshot of a workload of different project return status code is 200.

   • [API+CLI] workloadmgr workload-list --all True not working as expected.

   • [API+CLI] Advanced scheduler doesn't accept last in the --monthly section.

   • Should display the project IDs also along with the name while assigning the project to the BTT.

   • Limit openstackdataplanedeployment for on single execution.

   • Procedure for deleting dynamically added backup target on RHOSO18.0.

   • [Cross tenant vulnerability] Able to delete workload of other project even when it has snapshots using API.

   • [API + CLI] workload should not be created if there are no schedule values for hourly interval.

   • API documentation corrections.

Known Issues

1. 504 gateway timeout error in bulk deletion of error state snapshot from UI.

   • Workaround:

     • Delete multiple snapshots (in loop) from CLI using a script which will delete 1 snapshot at a time.

2. Retention failing intermittently with NFS V4.

6.1.6

Release Date : 19th Nov'2025

What's New?

1. Bug fixes:

   • User is unable to remove projects from BTT after assigning them; from UI & CLI.

   • User is unable to assign project to the BTT from the UI.

   • Project id is not correct in the backup-target-type-list.

   • Dynamic btt cleanup is incomplete on the WLM pods and the nodes.

2. Support for deletion of dynamically added S3 Backup Target without the need of T4O redeployment on RHOSO18.0.

3. Feasibility to attach additional networks to Trilio Pods on RHOSO18.0.

4. Feasibility to have separate RabbitMQ Installation on OpenStack Helm

Known Issues

1. 504 gateway timeout error in bulk deletion of error state snapshot from UI.

   • Workaround:

     • Delete multiple snapshots (in loop) from CLI using a script which will delete 1 snapshot at a time.

2. workload-reassign-workloads with --source-btt-all cli option doesn't work as expected

   • Workaround:

     • User can use --source-btt option to reassign the workloads from provided backup target type. Sample Command below:

       workloadmgr workload-reassign-workloads \
       --old_tenant_ids 71637e3b98434ceeb5158087074af4aa \
       --new_tenant_id 8e325e1056c94625854b3dffb4d1e64e \ 
       --user_id 3a446f94fb57448a8c99c08238df0f13 \
       --migrate_cloud True \
       --source-btt 979a459d-26f9-4aa9-8f0d-21ca7a1f6b4f

6.1.5

Release Date : 31st Oct'2025

What's New?

1. Bug fixes:

   • Restore fails with error Failed restoring snapshot: Timeout waiting for the instance to boot from volume.

   • Backup failing with error Failed creating workload snapshot: 'dict' object has no attribute 'done'.

   • VM doesn't boot after restore from incremental backup.

   • Non admin user can't list the policy assigned to the projects so that policy can be used with workloadmgr cli to create the workload.

   • Workload policy not getting rendered.

   • Workload creation via cli fails with error Policy could not be found.

   • If any policy is assigned to a project but not used by any workloads, same cannot be removed.

   • Sort Order of Policies in Horizon DropDown.

   • Notification Emails - Time Taken displayed wrong.

Known Issues

1. 504 gateway timeout error in bulk deletion of error state snapshot from UI.

   • Workaround:

     • Delete multiple snapshots (in loop) from CLI using a script which will delete 1 snapshot at a time.

2. workload-reassign-workloads with --source-btt-all cli option doesn't work as expected

   • Workaround:

     • User can use --source-btt option to reassign the workloads from provided backup target type. Sample Command below:

       workloadmgr workload-reassign-workloads \
       --old_tenant_ids 71637e3b98434ceeb5158087074af4aa \
       --new_tenant_id 8e325e1056c94625854b3dffb4d1e64e \ 
       --user_id 3a446f94fb57448a8c99c08238df0f13 \
       --migrate_cloud True \
       --source-btt 979a459d-26f9-4aa9-8f0d-21ca7a1f6b4f

6.1.4

Release Date : 17th Sept'2025

What's New?

1. Bug fixes:

   • Rabbitmq out-of-memory issue/connection blocking fixed.

   • Intermittent backup failures with "Error Failed creating workload snapshot: cannot schedule new futures after shutdown" fixed.

   • Dmapi exhausting the SQLAlchemy connection pool fixed.

   • Slow backup performance in some scenarios now fixed.

   • Cross-Tenant Access Vulnerability in Trilio Workload, Policy, and Backup APIs now fixed.

   • Deletion of workloads on Immutable BTT taking longer than expected now fixed.

   • Fixed slow backup performance for backups stored on buckets without object locking enabled.

Known Issues

1. If Backup Targets (BT) are slow/offline, then workload/snapshot creation slows down OR fails

   • Workaround:

     • If the impacted Backup Target is default, change the default to another Backup Target which is currently not impacted.

     • Delete the impacted Backup Target from CLI.

     • Manually unmount the Backup Target from wlm, datamover and respective Backup Target units/containers.

2. workload-reassign-workloads with --source-btt-all cli option doesn't work as expected

   • Workaround:

     • User can use --source-btt option to reassign the workloads from provided backup target type. Sample Command below:

       workloadmgr workload-reassign-workloads \
       --old_tenant_ids 71637e3b98434ceeb5158087074af4aa \
       --new_tenant_id 8e325e1056c94625854b3dffb4d1e64e \ 
       --user_id 3a446f94fb57448a8c99c08238df0f13 \
       --migrate_cloud True \
       --source-btt 979a459d-26f9-4aa9-8f0d-21ca7a1f6b4f

6.1.3

Release Date : 18th July'2025

What's New?

1. High priority bug fixes:

   i. S3 endpoint was not reachable due to large number of file descriptors (fd) against s3fuse.

   ii. Snapshot of single workload with 50 VMs was failing.

   iii. TLS certificate expiry on RHOSO18.0.

2. Support for T4O on Canonical 2024.1(Caracal) on Jammy.

Known Issues

1. If any of the configured BT is slow/offline, then workload/snapshot creation slows down OR fails

   • Workaround:

     • If the impacted BT is default, change the default to other BT which doesn't seem impacted.

     • Delete the impacted BT from CLI.

     • Manually unmount from wlm, datamover and respective BT units/containers.

2. To update any BTT so as to make it default, modify command should NOT be used. Instead, user should use backup-target-set-default CLI command.

3. During T4O deployment, if S3 Immutable bucket is set as the default target, the UI goes into hang state.

   • Workaround:

     • Deploy T4O on OpenStack helm by keeping s3 immutable target as default, then add s3 mutable/NFS as dynamic target. Later, change the s3 mutable(dynamic target) target to default.

4. workload-reassign-workloads with --source-btt-all cli option doesn't work as expected

   • Workaround:

     • User can use --source-btt option to reassign the workloads from provided backup target type. Sample Command below:

       workloadmgr workload-reassign-workloads \
       --old_tenant_ids 71637e3b98434ceeb5158087074af4aa \
       --new_tenant_id 8e325e1056c94625854b3dffb4d1e64e \ 
       --user_id 3a446f94fb57448a8c99c08238df0f13 \
       --migrate_cloud True \
       --source-btt 979a459d-26f9-4aa9-8f0d-21ca7a1f6b4f

6.1.2

Release Date : 3rd July'2025

What's New?

1. Support for T4O on MOSK.

2. Addition/Deletion of Backup Target (BT) is enabled without the need of T4O redeployment.

Known Issues

1. If any of the configured BT is slow/offline, then workload/snapshot creation slows down OR fails

   • Workaround:

     • If the impacted BT is default, change the default to other BT which doesn't seem impacted.

     • Delete the impacted BT from CLI.

     • Manually unmount from wlm, datamover and respective BT units/containers.

2. To update any BTT so as to make it default, modify command should NOT be used. Instead, user should use backup-target-set-default CLI command.

3. During T4O deployment, if S3 Immutable bucket is set as the default target, the UI goes into hang state.

   • Workaround:

     • Deploy T4O on OpenStack helm by keeping s3 immutable target as default, then add s3 mutable/NFS as dynamic target. Later, change the s3 mutable(dynamic target) target to default.

4. workload-reassign-workloads with --source-btt-all cli option doesn't work as expected

   • Workaround:

     • User can use --source-btt option to reassign the workloads from provided backup target type. Sample Command below:

       workloadmgr workload-reassign-workloads \
       --old_tenant_ids 71637e3b98434ceeb5158087074af4aa \
       --new_tenant_id 8e325e1056c94625854b3dffb4d1e64e \ 
       --user_id 3a446f94fb57448a8c99c08238df0f13 \
       --migrate_cloud True \
       --source-btt 979a459d-26f9-4aa9-8f0d-21ca7a1f6b4f

6.1.1

Release Date : 21st May'2025

What's New?

1. Support for T4O on OpenStack Helm.

Known Issues

1. [OpenStack Helm] During T4O deployment, if S3 Immutable bucket is set as the default target, the UI goes into hang state.

   • Workaround:

     • Deploy T4O on OpenStack helm by keeping s3 immutable target as default, then add s3 mutable/NFS as dynamic target. Later, change the s3 mutable(dynamic target) target to default.

2. workload-reassign-workloads with --source-btt-all cli option doesn't work as expected

   • Workaround:

     • User can use --source-btt option to reassign the workloads from provided backup target type. Sample Command below:

       workloadmgr workload-reassign-workloads \
       --old_tenant_ids 71637e3b98434ceeb5158087074af4aa \
       --new_tenant_id 8e325e1056c94625854b3dffb4d1e64e \ 
       --user_id 3a446f94fb57448a8c99c08238df0f13 \
       --migrate_cloud True \
       --source-btt 979a459d-26f9-4aa9-8f0d-21ca7a1f6b4f

6.1.0

Release Date : 10th April'2025

What's New?

1. Support for T4O on RHOSO18.0.

2. Support for Dynamic Backup Target addition without the need of redeployment of T4O.

3. Support for T4O on OpenStack Helm.

Known Issues

1. trilio-openstack-operator-rhoso images are not available on Operator Hub

   • Workaround:

     • To install from cli using install script as mentioned in the deployment doc.

2. workload-reassign-workloads with --source-btt-all cli option doesn't work as expected

   • Workaround:

     • User can use --source-btt option to reassign the workloads from provided backup target type. Sample Command below:

       workloadmgr workload-reassign-workloads \
       --old_tenant_ids 71637e3b98434ceeb5158087074af4aa \
       --new_tenant_id 8e325e1056c94625854b3dffb4d1e64e \ 
       --user_id 3a446f94fb57448a8c99c08238df0f13 \
       --migrate_cloud True \
       --source-btt 979a459d-26f9-4aa9-8f0d-21ca7a1f6b4f

6.0.0

Release Date : 18th Jan'2025

What's New?

1. Deployment of Trilio on RHOCP (with RHOSP17.1).

2. Support for multiple target backends.

3. Support for advanced scheduling of workloads' snapshots.

4. Support for Immutable Backups on S3 target backend.

5. Support for Canonical Yoga, 2023.1(Antelope) & 2023.2(Bobcat) on Jammy.

Known Issues

1. T4O upgrade on Canonical OpenStack is not supported

2. Restore operations fail for image-booted instance after changing the image from public to private

   • Workaround:

     • Make the image public or accessible to the project/user.

3. Select All option does not work on Backup Target Types page

4. Sorting the columns on the backup's admin page is not working

5. Workload Policy field is missing in the workload creation wizard until the scheduler is enabled

6. In the workload-reassign-workloads help text --new_tenant_ids is provided instead of --new_tenant_id

7. [Canonical multiple Backup Target] If NFS Backup Target getting deployed before S3 Backup Targets, then object store services against S3 Backup Target go into error state

   • If the overlay bundle is having multiple Backup Target Types defined such that at least one is NFS and one is S3 and if deployment of NFS happens first, then it is noticed that NFS mount happens successfully whereas object store services against S3 Backup Target Types start failing. Error An error occured (403) when calling HeadBucket operation: Forbidden is observed.

   • Workaround:

     • manually unmount the NFS mountpoint. All required S3 object store services will start successfully along with mounting of S3 sharepath. Unmounted NFS also gets remounted within 2-3 min (via mtab).

8. workload modify CLI command with workload_id at end is throwing an error

   • Workaround:

     • Place the workload_id before the optional arguments.

     • Sample command workloadmgr workload-modify 858da6e0-5b55-4c63-9a8e-d9f116130686 --jobschedule enabled=True --jobschedule start_time='07:00 AM' --jobschedule start_date='01/08/2025' --hourly interval='1' retention='2' snapshot_type='incremental'