T4O-5.x

Release Notes

5.2.2

What's New?

  1. Support for Kolla Bobcat OpenStack added.

  2. Fixed the issues reported by customers.

Fixed Bugs and issues

  1. [VMware Migration] Migration failure due to minor issues in handling vm and network names.

  2. [VMware migration] boot options shows BIOS when the guest VM has unsecured efi boot.

  3. [VMware Migration] Migration fails when the network name of the guest VM contains - and _ both.

  4. Support multi ceph config in same /etc/ceph location.

  5. Trilio looks for instance in wrong region if openstack is multi region.

  6. T4O deployment on Kolla Antelope failing. DMAPI and horizon container fail to start.

  7. Quota updation when admin user have access to projects of multiple domains

Known Issues

  1. Encryption checkbox is disabled when creating 1st workload from UI

    • While creating 1st workload from the UI, the Enable Encryption checkbox on the Create workload page is disabled. Creating a non-encrypted workload first will resolve this issue and the user can start creating the encrypted workloads.

  2. RHOSP16.1/16.2 : Unexpected behavior with OpenStack UI

    • At times, after the overcloud deployment, the OpenStack UI encounters issues, leading to unexpected behavior in certain functionalities.

    • Workaround:

      1. Login to the Horizon container and run the following commands: podman exec -it -u root horizon /bin/bash /usr/bin/python3 /usr/share/openstack-dashboard/manage.py collectstatic --clear --noinput /usr/bin/python3 /usr/share/openstack-dashboard/manage.py compress --force

      2. Restart the Horizon container : podman restart horizon

  3. Horizon pod keeps restarting on RHOSP 16.2.4

    • It has been observed that on a specific RHOSP minor version, i.e. 16.2.4, the horizon pod keeps restarting.

    • Either of the below workarounds can be performed on all the controller nodes where the issue seems to occur.

    • Workaround:

      1. Workaround 1 : Restart the memcached service on the controller using systemctl systemctl restart tripleo_memcached.service

      2. Workaround 2 : Restart the memcached pod podman restart memcached

  4. get-importworkload-list and get-orphaned-workloads-list show incorrect workloads

    • The commands get-importworkload-list and get-orphaned-workloads-list show incorrect workloads in the output.

    • Workaround:

      • Use --project option with get-importworkload-list CLI command to get the list of workloads that can be imported on any particular project of the OpenStack. workloadmgr workload-get-importworkloads-list --project_id <project_id>

  5. workload-importworklaods cli command throws gateway timed out error

    • workload-importworklaods CLI command throws gateway timed out error, however, import actually succeeds.

    • In the background, the import process continues to run in spite of timeout until the operation is complete.

    • Workaround:

      • To avoid the timeout error, the respective timeout server value can be increased inside /var/lib/config-data/puppet-generated/haproxy/etc/haproxy/haproxy.cfg for RHOSP

5.2.1

What's New?

  1. Software Driven Migration : VMware to OpenStack With T4O-5.2.1 release, Trilio now supports migration of VMs from VMware to Openstack.

More about this feature can be found here.

2. Fixed the issues reported by customers.

Fixed Bugs and issues

  1. Support multi ceph config in same /etc/ceph location.

  2. Encrypted incremental restore fails to diff AZ.

  3. Trilio installation failing for RHOSP17.1 IPV6.

  4. [RHOSP] memcache_servers parameter in triliovault wlm and datamover service conf files fixed for ipv6.

  5. Deployment (with non-root user) failing on kolla with barbican.

  6. T4O 5.1 failing on Kolla Zed rocky

  7. 5.2 deployment failing on Antelope with ansible node on separate server.

  8. WLM service issue with IPV6. Containers keep restarting due to Data too long for column ip_addresses at row 1.

Known Issues

  1. RHOSP16.1/16.2 : Unexpected behavior with OpenStack UI

    • At times, after the overcloud deployment, the OpenStack UI encounters issues, leading to unexpected behavior in certain functionalities.

    • Workaround:

      1. Login to the Horizon container and run the following commands: podman exec -it -u root horizon /bin/bash /usr/bin/python3 /usr/share/openstack-dashboard/manage.py collectstatic --clear --noinput /usr/bin/python3 /usr/share/openstack-dashboard/manage.py compress --force

      2. Restart the Horizon container : podman restart horizon

  2. Horizon pod keeps restarting on RHOSP 16.2.4

    • It has been observed that on a specific RHOSP minor version, i.e. 16.2.4, the horizon pod keeps restarting.

    • Either of the below workarounds can be performed on all the controller nodes where the issue seems to occur.

    • Workaround:

      1. Workaround 1 : Restart the memcached service on the controller using systemctl systemctl restart tripleo_memcached.service

      2. Workaround 2 : Restart the memcached pod podman restart memcached

  3. get-importworkload-list and get-orphaned-workloads-list show incorrect workloads

    • The commands get-importworkload-list and get-orphaned-workloads-list show incorrect workloads in the output.

    • Workaround:

      • Use --project option with get-importworkload-list CLI command to get the list of workloads that can be imported on any particular project of the OpenStack. workloadmgr workload-get-importworkloads-list --project_id <project_id>

  4. workload-importworklaods cli command throws gateway timed out error

    • workload-importworklaods CLI command throws gateway timed out error, however, import actually succeeds.

    • In the background, the import process continues to run in spite of timeout until the operation is complete.

    • Workaround:

      • To avoid the timeout error, the respective timeout server value can be increased inside /var/lib/config-data/puppet-generated/haproxy/etc/haproxy/haproxy.cfg for RHOSP

5.2.0

What's New?

  • New OpenStack additions in Trilio support matrix: With T4O-5.2.0, Trilio now supports backup and DR for RHOSP17.1 and Kolla-Ansible OpenStack 2023.1 Antelope on Rocky Linux & Ubuntu Jammy.

Known Issues

  1. RHOSP16.1/16.2 : Unexpected behavior with OpenStack UI

    • At times, after the overcloud deployment, the OpenStack UI encounters issues, leading to unexpected behavior in certain functionalities.

    • Workaround:

      1. Login to the Horizon container and run the following commands: podman exec -it -u root horizon /bin/bash /usr/bin/python3 /usr/share/openstack-dashboard/manage.py collectstatic --clear --noinput /usr/bin/python3 /usr/share/openstack-dashboard/manage.py compress --force

      2. Restart the Horizon container : podman restart horizon

  2. Horizon pod keeps restarting on RHOSP 16.2.4

    • It has been observed that on a specific RHOSP minor version, i.e. 16.2.4, the horizon pod keeps restarting.

    • Either of the below workarounds can be performed on all the controller nodes where the issue seems to occur.

    • Workaround:

      1. Workaround 1 : Restart the memcached service on the controller using systemctl systemctl restart tripleo_memcached.service

      2. Workaround 2 : Restart the memcached pod podman restart memcached

  3. get-importworkload-list and get-orphaned-workloads-list show incorrect workloads

    • The commands get-importworkload-list and get-orphaned-workloads-list show incorrect workloads in the output.

    • Workaround:

      • Use --project option with get-importworkload-list CLI command to get the list of workloads that can be imported on any particular project of the OpenStack. workloadmgr workload-get-importworkloads-list --project_id <project_id>

  4. workload-importworklaods cli command throws gateway timed out error

    • workload-importworklaods CLI command throws gateway timed out error, however, import actually succeeds.

    • In the background, the import process continues to run in spite of timeout until the operation is complete.

    • Workaround:

      • To avoid the timeout error, the respective timeout server value can be increased inside /var/lib/config-data/puppet-generated/haproxy/etc/haproxy/haproxy.cfg for RHOSP

5.1.0

What's New?

  • True Native and Containerized Deployment: In the T4O-5.1.0 release, Trilio has embraced a transformative shift. Departing from the traditional method of shipping appliance images, T4O has evolved into a comprehensive backup and recovery solution that is fully containerized. Within this iteration, all T4O services have been elegantly encapsulated within containers, seamlessly aligning with OpenStack through its innate deployment process.

  • New OpenStack additions in Trilio support matrix: With T4O-5.1.0, Trilio now supports backup and DR for Kolla-Ansible OpenStack Zed on Rocky Linux and Ubuntu Jammy.

Known Issues

  1. Horizon pod keeps restarting on RHOSP 16.2.4

    • It has been observed that on a specific RHOSP minor version, i.e. 16.2.4, the horizon pod keeps restarting.

    • Either of the below workarounds can be performed on all the controller nodes where the issue seems to occur.

    • Workaround:

      1. Workaround 1 : Restart the memcached service on the controller using systemctl systemctl restart tripleo_memcached.service

      2. Workaround 2 : Restart the memcached pod podman restart memcached

  2. get-importworkload-list and get-orphaned-workloads-list show incorrect workloads

    • The commands get-importworkload-list and get-orphaned-workloads-list show incorrect workloads in the output.

    • Workaround:

      • Use --project option with get-importworkload-list CLI command to get the list of workloads that can be imported on any particular project of the OpenStack. workloadmgr workload-get-importworkloads-list --project_id <project_id>

  3. workload-importworklaods cli command throws gateway timed out error

    • workload-importworklaods CLI command throws gateway timed out error, however, import actually succeeds.

    • In the background, the import process continues to run in spite of timeout until the operation is complete.

    • Workaround:

      • To avoid the timeout error, the respective timeout server value can be increased inside /var/lib/config-data/puppet-generated/haproxy/etc/haproxy/haproxy.cfg for RHOSP

5.0.0

What's New?

  • True Native and Containerized Deployment: In the T4O-5.0.0 release, Trilio has embraced a transformative shift. Departing from the traditional method of shipping appliance images, T4O has evolved into a comprehensive backup and recovery solution that is fully containerized. Within this iteration, all T4O services have been elegantly encapsulated within containers, seamlessly aligning with OpenStack through its innate deployment process.

  • Faster Snapshot operation (Removal of Workload types: Serial and Parallel): In a move to boost Snapshot operation efficiency, we've introduced a streamlined method for creating workloads, eliminating the need for users to select between different workload types. T4O will now intelligently manage workloads in the background, ensuring optimal performance for backup operations.

  • Improved Database Storage: T4O has made significant enhancements to its database management, focusing on efficient data garbage collection. By discarding unnecessary data and optimizing the utilization of DB storage within the task flow, these improvements have led to a leaner and more streamlined storage approach for its DB tables.

  • Better Troubleshooting: Enhanced troubleshooting capabilities come through the implementation of a unified logging format across all T4O services/containers. This improvement grants users the freedom to adjust the format or log levels for individual services/containers as needed.

  • Updated EULA: Trilio has updated the End User License Agreement (EULA) that users must accept before using the product. For user convenience, T4O now prompts users to review and accept the EULA during the licensing step of the T4O installation. The most recent version of the EULA can be found here: https://trilio.io/eula/

Known Issues

  1. Horizon pod keeps restarting on RHOSP 16.2.4

    • It has been observed that on a specific RHOSP minor version, i.e. 16.2.4, the horizon pod keeps restarting.

    • Either of the below workarounds can be performed on all the controller nodes where the issue seems to occur.

    • Workaround:

      1. Workaround 1 : Restart the memcachedservice on the controller using systemctl systemctl restart tripleo_memcached.service

      2. Workaround 2 : Restart the memcached pod podman restart memcached

  2. get-importworkload-list and get-orphaned-workloads-list show incorrect workloads

    • Commands get-importworkload-list and get-orphaned-workloads-list show incorrect workloads in the output.

    • Workaround:

      • Use --project option with get-importworkload-list CLI command to get the list of workloads that can be imported on any particular project of the OpenStack. workloadmgr workload-get-importworkloads-list --project_id <project_id>

  3. workload-importworklaods cli command throws gateway timed out error

    • workload-importworkloads CLI command throws gateway timed out error, however, import succeeds.

    • In the background, the import process continues to run despite of timeout until the operation is complete.

    • Workaround:

      • To avoid the timeout error, the respective timeout server value can be increased inside /var/lib/config-data/puppet-generated/haproxy/etc/haproxy/haproxy.cfg for RHOSP

PreviousT4O ArchitectureNextCompatibility Matrix

Last updated