Release Notes

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 : 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 : 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'