Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This Hotfix extends the Support Matrix of T4O 4.2 as follows:
Canonical Openstack Wallaby based on Focal (20.04) Support
Kolla Ansible Openstack Wallaby on Ubuntu 20.04 and CentOS Stream
Openstack Ansible Wallaby on Ubuntu 20.04 and CentOS Stream
Rebase permission error
An issue has been fixed which prevented the correct rebase of T4O incremental backups in the case that root didn't have the required permissions on the backup target.
Name | Type | Version |
---|---|---|
Name | Tag |
---|---|
s3fuse
python package
4.2.64
tvault-configurator
python package
4.2.64.1
workloadmgr
python package
4.2.64.1
workloadmgrclient
python package
4.2.64
dmapi
deb package
4.2.64
python3-dmapi
deb package
4.2.64
tvault-contego
deb package
4.2.64.1
python3-tvault-contego
deb package
4.2.64.1
tvault-horizon-plugin
deb package
4.2.64
python3-tvault-horizon-plugin
deb package
4.2.64
s3-fuse-plugin
deb package
4.2.64
python3-s3-fuse-plugin
deb package
4.2.64
workloadmgr
deb package
4.2.64.1
workloadmgrclient
deb package
4.2.64
dmapi
rpm package
4.2.64-4.2
python3-dmapi
rpm package
4.2.64-4.2
puppet-triliovault
rpm package
4.2.64-4.2
python3-contegoclient-el8
rpm package
4.2.64-4.2
tvault-contego
rpm package
4.2.64.1-4.2
python3-tvault-contego
rpm package
4.2.64.1-4.2
tvault-horizon-plugin
rpm package
4.2.64-4.2
python3-tvault-horizon plugin-el8
rpm package
4.2.64-4.2
python-s3fuse-plugin-cent7
rpm package
4.2.64-4.2
python3-s3fuse-plugin
rpm package
4.2.64-4.2
python3-trilio-fusepy
rpm package
3.0.1-1
trilio-fusepy
rpm package
3.0.1-1
workloadmgrclient
rpm package
4.2.64-4.2
python3-workloadmgrclient-el8
rpm package
4.2.64-4.2
Gitbranch
hotfix-1-TVO/4.2
RHOSP13 containers
4.2.64-hotfix-1-rhosp13
RHOSP16.1 containers
4.2.64-hotfix-1-rhosp16.1
RHOSP16.2 containers
4.2.64-hotfix-1-rhosp16.2
Kolla Ansible Victoria containers
4.2.64-hotfix-1-victoria
Kolla Ansible Wallaby containers
4.2.64-hotfix-1-wallaby
TripleO Train containers
4.2.64-hotfix-1-tripleo
This Hotfix extends the Support Matrix of T4O 4.2 as follows:
Fresh 4.2HF4 Trilio appliance build with wlm services on Python3.8 and multiple vulnerability fixes
Kolla Ansible Openstack Yoga CentOS Stream 8, Ubuntu 20.04
Canonical Yoga Ubuntu 20.04, Ubuntu 22.04
Irods nfs T4O not compatible
Backups failing with "Unable to call vast_instance"
Backup/restore does not work when NFS has access to Nova user just NOVA
Failed ansible-tvault-contego-extension : create trilio.filters for mount and unmount task
lxc packages not installed when using bare metal install
dmapi_all also includes bare metal hosts on non LXC deployments
Config failed with "iptables: Nothing to save" when TVM utilizing IPv6 | Tmobile/Red Hat | SFDC#2881
Trilio 4.2 introduces new features and capabilities:
Backup and Recovery of encrypted Cinder volumes (Barbican support)
Encryption of Workloads (Barbican support)
Support for multi-IP NFS backup targets
Database clean up utility
Backup rebase utility
Trilio 4.2.64
This functionality is not yet available for Canonical OpenStack. An update will be provided once it is available for Canonical OpenStack too.
This functionality is not available for RHOSP13 or TripleO Train on CentOS7. The reason is a dependency package, which is not available in RHEL7 or CentOS7.
The OpenStack Barbican service enables the OpenStack Cinder service to provide encrypted Volumes. These volumes are software encrypted by the Cinder service with the secret used for the encryption being managed by the Barbican service.
Trilio for OpenStack 4.2 is integrating into OpenStack Barbican to enable T4O to provide native backup and recovery of the encrypted Cinder volume.
Any workload containing an encrypted Cinder volume has to create encrypted backups too. It is not possible to create unencrypted Workloads for encrypted Cinder Volumes.
T4O 4.2 is providing encryption on the Workload level. All VMs that are part of an encrypted Workload will have their Cinder Volume data encrypted.
This functionality is not available for encrypted Nova boot volumes. Encrypted Nova boot volumes can not be backed up. Unencrypted Nova boot volumes can be backed up and put into an encrypted Workload.
Activating this feature and using encrypted Workload will lead to longer backup times. The following timings have been seen in Trilio labs:
Snapshot time for LVM Volume Booted CentOS VM. Disk size 200 GB; total data including OS : ~108GB
For unencrypted WL : 62 min
For encrypted WL : 82 min
Snapshot time for Windows Image booted VM. No additional data except OS. : ~12 GB
For unencrypted WL : 10 min
For encrypted WL : 18 min
This functionality is not yet available for Canonical OpenStack. An update will be provided once it is available for Canonical OpenStack too.
This functionality is not available for RHOSP13 or TripleO Train on CentOS7. The reason is a dependency package, which is not available in RHEL7 or CentOS7.
The integration of Trilio for OpenStack 4.2 into Barbican enables T4O to provide encryption for the qcow2-data component of the Trilio backups. The json files containing the backed-up OpenStack metadata stays unencrypted.
This functionality requires the OpenStack Barbican service to be present. Without the Barbican service, the possibilities to encrypt Workloads will not be shown inside Horizon.
T4O 4.2 is only consuming secrets from Barbican. It is not creating, editing, or deleting any secret inside Barbican.
Barbican secrets are required to run backups or restores in encryption-enabled Workloads. It is the OpenStack project user's responsibility to provide secrets and to ensure that the correct secrets are available.
To utilize encrypted Workloads the Trilio trustee role needs to be able to engage with the Barbican service to read and fetch secrets from Barbican. The only default roles enabled with these permissions are the admin and the creator roles.
The possibility to encrypt a Workload is only provided during Workload creation. Once a workload has been created it is no longer possible to change, whether the Workload is encrypted or not.
Every encrypted Workload is consuming a unique Barbican secret. It is not possible to assign the same secret to two Workloads.
The following secret configurations are supported.
A default Barbican installation will generate secrets of the following type:
Alghorithm: AES-256
Mode: cbc
content type: application/octet-stream
payload-content-encoding: base64
secret type: opaque
payload: plaintext
Barbican can be configured to use other secret vaults as a backend. Trilio has not tested other than the default secret vault provided by the Barbican service.
Other secret vaults are supported under best-effort support.
Encrypted Workloads can be migrated to different projects or clouds just like normal Workloads. The Barbican secrets used for the encryption need to be made available inside the target environment. This already applies when the Workload gets assigned to a different owner.
This functionality is not yet available for Canonical OpenStack. An update will be provided once it is available for Canonical OpenStack too.
Many Trilio customers are using software-defined storage solutions for a scalable backup target. These software-defined storage solutions often provide the capability to spread read and write operations over multiple nodes of the storage cluster. Each of these nodes has its own access IP to interact with. All nodes are still writing to the same logical volume, which is available through the NFS protocol.
Trilio for Openstack 4.2 is supporting such solutions by enabling the have different IPs for the same backup target for each Datamover.
Every Datamover and the Trilio appliance are still consuming one NFS path per Volume.
The requirement for this functionality is that all NFS paths spread across the Trilio solution are accessing the same NFS Volume. Using this functionality to provide the Trilio solution with different backup targets to different Datamovers will lead to backup and restore failures.
This is achieved by changing the method to calculate the T4O mount point. It is now only considering the volume path instead of the complete NFS path. Example below.
Trilio for OpenStack is following an older OpenStack database schema and model. This model contains, that no data inside the database ever gets truly deleted. Only a flag is set to showcase that the dataset is no longer considered active.
This has the advantage that it is always possible to trace back any objects and their existence timeline inside the database for analytical purposes.
The big disadvantage of this model is that the database itself is ever-growing with every activity that T4O is doing.
Over time it is possible for the database to reach sizes, that normal activities like listing Workloads are taking so long, that other tasks like taking backups are impacted.
To counter this issue does Trilio provide a new utility, which will delete all no longer required database entries to reduce the load of the work when the T4O solution needs to access the database.
Running this utility will completely delete all elements that are not required for active Workloads or Snapshots. It is recommended to create a database dump first when the possibility to analyze past data is required.
Trilio will revamp its Database schema and usage in a future T4O release.
Trilio for OpenStack is providing full synthetic backups utilizing the backing-file functionality of qcow2 images.
This functionality enables Trilio backups to run incremental forever, without having to restore every incremental backup. Instead only the latest backup needs to be restored as all missing blocks are fetched through the backing file chain from older backups.
The backing file of a particular backup is hardcoded inside the qcow2 image itself. These backing files need to consist of the full path and can't use relative paths. An example is provided below.
T4O is using a base64 hash value inside this path for NFS backup targets. This backup target path needs to be resolvable for the qcow2 image to find its backing file.
The hash value of the mount path can change when the backup is moved to a different backup target or when the T4O calculation method is changed like it is for T4O 4.2.
Trilio is now providing a utility that will change the backing file path for a given workload.
The runtime of this utility is increasing exponentially with increasing backing file chain.
[Canonical OpenStack] Selective restore fails for migrated workloads
Observation:
after migrating workloads to a different Canonical OpenStack environments restore fails with permission denied error in tmp directory
Workaround:
Run the {{sudo sysctl fs.protected_regular=0}} command on wlm units.
[Intermittent Canonical OpenStack Queens] In-Place restore doesn't work with ext3/ext4 file systems
Observation:
In-Place restore succeeds logically
Data is not getting replaced
Workaround:
Running the In-Place restore a second time
Running a selective restore and reattaching the restored Volume
[intermittent] [Canonical OpenStack] Retention not honored after mount/unmount operation
Observation:
After a mount or unmount operation the ownership of the backup stays qemu:qemu which leads to T4O no longer being able to run required merge commands
Workaround:
identify the workload with failed retention policy
run: chown -R nova:nova <WL_DIR>
verify next backup applies the retention policy
CLI commands get-importworkload-list and get-orphaned-workloads-list show wrong list of workloads
Observation:
independent of the command all workloads located on the backup target are listed
Workaround:
use project id in command to show only workloads that can be imported for that project
workloadmgr workload-get-importworkloads-list --project_id <project_id>
File-search not displaying files in lvm created logical volumes
Observation:
File search returns an empty list for lvm controlled logical volumes
fdisk created logical volumes work as desired
File-search not displaying files when root directory doesn't contain read permissions for group
Observation:
File search returns an empty list when root doesn't have read permissions for groups
File search is run as user nova
Unable to create encrypted Workload if T4O gets reconfigured with creator trustee role
Observation:
T4O initially configured with trustee role member (not able to create encrypted workloads)
After reconfiguration to trustee role creator encrypted workloads are still not creatable
Workaround:
After reconfiguration create one unencrypted workload
Then create encrypted workloads as required
Post restore of encrypted incremental snapshots CentOS instance is not getting booted
Observation:
Restoring of a CentOS-based instance fails to start the instance in the case of restoring from an encrypted incremental snapshot
Workaround:
Use only full backups for CentOS-based instances in combination with encrypted Workloads
Snapshot getting hung in upload phase for multipath environments
An issue has been fixed, which lead to Snapshots being stuck in the upload phase in the case of using an FC multipath connected Cinder Storage.
Backups fail due to an old Trilio Cinder Snapshot not being in available state
An issue has been fixed, which lead to Trilio-created Cinder Snapshots, which are not in the state available, blocking the creation of new Cinder Snapshots.
Latin characters in restore names lead to failed restores
The support for Latin characters has been enhanced to no longer impact restores.
End of support for Openstack Ansible from 4.2.HF5
Bug fixes targeted for 4.2.HF5 release
Kolla openstack source based container for wallaby
Cinder volumes NFS folder not mounted to datamover container
Cinder has IBM GPFS mounted as NFS
RHOSP16.1 breaks horizon 4.2hf4
Backup/restore does not work when NFS has access to Nova user just NOVA
Snapshot for encrypted volume is failing with error
Cinder attached volume backup is taking time and also created 4 temporary volumes
Cinder booted VM backup failing
To use this hotfix (4.2.HF3).
Customers (except Canonical Openstack) and having Openstack Ussuri OR Openstack Victoria need to have an already deployed and working TVO-4.2 GA.
Customers (except Canonical Openstack) and having Openstack Wallaby need to follow the T4O-4.2 GA deployment process and directly upgrade to 4.2.HF3 containers/packages. The high-level flow below:
Deplo T4O-4.2 GA appliance.
Upgrade to 4.2.HF3 packages on the appliance.
Kolla
Deploy Trilio components via 4.2.HF3 containers/packages on Openstack Wallaby.
Openstack Ansible
Deploy Trilio components Openstack Wallaby [This will deploy 4.2 GA packages]
Upgrade TrilioVault packages to 4.2.HF3 on Openstack Wallaby.
Configure the Trilio appliance.
Canonical users having Openstack Ussuri Or Openstack Victoria can either upgrade (on top of 4.2 GA) using Trilio upgrade documents OR do a new deployment using 4.2 Deployment documents.
Canonical users having Openstack Wallaby need to do a new deployment using 4.2 Deployment documents.
Current Hotfix release targets the following:
High-level Qualification (via Sanity & Functional suites' execution) of T4O with Ussuri, Victoria & Wallaby Openstack.
Verification of Jira issues targeted for 4.2. release.
As part of the new process, the delivery will be via packages; end users would need to do the rolling upgrade on top of 4.2 GA.
Note : Container images with tag 4.2.64-hotfix-3-rhosp16.1 are not available for download from RedHat registry due to technical issues. Hence, it is recommended to use the latest tag, i.e. 4.2.64-hotfix-4-rhosp16.1.
Name | Type | Version |
---|---|---|
Name | Tag |
---|---|
Algorithm | mode | content types | payload-content-encoding | secret type | payload | secretfile |
---|---|---|---|---|---|---|
Name | Type | Version |
---|
Name | Tag |
---|
Ref link for 4.2.64-hotfix-4-rhosp16.1 : __
Package/Container Names
Package Kind
Package Version/Container Tags
contego
deb
4.2.64
contegoclient
rpm
4.2.64-4.2
contegoclient
deb
4.2.64
contegoclient
python
4.2.64
puppet-triliovault
rpm
4.2.64-4.2
python3-contegoclient
deb
4.2.64
python3-contegoclient-el8
rpm
4.2.64-4.2
python3-s3-fuse-plugin
deb
4.2.64
python3-s3fuse-plugin
rpm
4.2.64-4.2
python3-trilio-fusepy
rpm
3.0.1-1
python-s3fuse-plugin-cent7
rpm
4.2.64-4.2
s3-fuse-plugin
deb
4.2.64
trilio-fusepy
rpm
3.0.1-1
python3-workloadmgrclient
deb
4.2.64.1
python3-workloadmgrclient-el8
rpm
4.2.64.1-4.2
python-workloadmgrclient
deb
4.2.64.1
workloadmgrclient
python
4.2.64.1
workloadmgrclient
rpm
4.2.64.1-4.2
Package/Container Names
Package Kind
Package/Container Version/Tags
python3-tvault-contego
deb
4.2.64.8
tvault-contego
deb
4.2.64.8
python3-tvault-contego
rpm
4.2.64.8-4.2
tvault-contego
rpm
4.2.64.8-4.2
tvault-contego
python
4.2.64.1
workloadmgr
deb
4.2.64.10
workloadmgr
python
4.2.64.10
tvault_configurator
python
4.2.64.10
tvault-horizon-plugin
deb
4.2.64.2
tvault-horizon-plugin
rpm
4.2.64.2-4.2
tvault-horizon-plugin
python
4.2.64.1
python3-tvault-horizon-plugin
deb
4.2.64.2
python3-tvault-horizon-plugin-el8
rpm
4.2.64.2-4.2
dmapi
python
4.2.64.1
dmapi
rpm
4.2.64.1-4.2
dmapi
deb
4.2.64.1
python3-dmapi
deb
4.2.64.1
python3-dmapi
rpm
4.2.64.1-4.2
s3fuse
python
4.2.64.1
Charm name
Channel
Supported release
trilio-charmers-trilio-wlm-jammy
latest/edge
Jammy (Ubuntu 22.04)
trilio-charmers-trilio-dm-api-jammy
latest/edge
Jammy (Ubuntu 22.04)
trilio-charmers-trilio-data-mover-jammy
latest/edge
Jammy (Ubuntu 22.04)
trilio-charmers-trilio-horizon-plugin-jammy
latest/edge
Jammy (Ubuntu 22.04)
trilio-charmers-trilio-wlm-focal
latest/edge
Focal (Ubuntu 20.04)
trilio-charmers-trilio-dm-api-focal
latest/edge
Focal (Ubuntu 20.04)
trilio-charmers-trilio-data-mover-focal
latest/edge
Focal (Ubuntu 20.04)
trilio-charmers-trilio-horizon-plugin-focal
latest/edge
Focal (Ubuntu 20.04)
Name
Tag
Gitbranch
hotfix-4-TVO/4.2
RHOSP13 containers
4.2.64-hotfix-4-rhosp13
RHOSP16.1 containers
4.2.64-hotfix-4-rhosp16.1
RHOSP16.2 containers
4.2.64-hotfix-4-rhosp16.2
Kolla Ansible Victoria containers
4.2.64-hotfix-4-victoria
Kolla Ansible Wallaby containers
4.2.64-hotfix-4-wallaby
Kolla Yoga Containers
4.2.64-hotfix-4-yoga
TripleO Containers
4.2.63-hotfix-4-tripleo
s3fuse
python package
4.2.64
tvault-configurator
python package
4.2.64
workloadmgr
python package
4.2.64
workloadmgrclient
python package
4.2.64
dmapi
deb package
4.2.64
python3-dmapi
deb package
4.2.64
tvault-contego
deb package
4.2.64
python3-tvault-contego
deb package
4.2.64
tvault-horizon-plugin
deb package
4.2.64
python3-tvault-horizon-plugin
deb package
4.2.64
s3-fuse-plugin
deb package
4.2.64
python3-s3-fuse-plugin
deb package
4.2.64
workloadmgr
deb package
4.2.64
workloadmgrclient
deb package
4.2.64
python3-namedatomiclock
deb package
1.1.3
dmapi
rpm package
4.2.64-4.2
python3-dmapi
rpm package
4.2.64-4.2
tvault-contego
rpm package
4.2.64-4.2
python3-tvault-contego
rpm package
4.2.64-4.2
tvault-horizon-plugin
rpm package
4.2.64-4.2
python3-tvault-horizon plugin-el8
rpm package
4.2.64-4.2
python-s3fuse-plugin-cent7
rpm package
3.0.1-1
python3-s3fuse-plugin
rpm package
3.0.1-1
workloadmgrclient
rpm package
4.2.64-4.2
Gitbranch
stable/4.2
RHOSP13 containers
4.2.64-rhosp13
RHOSP16.1 containers
4.2.64-rhosp16.1
RHOSP16.2 containers
4.2.64-rhosp16.2
Kolla Ansible Victoria containers
4.2.64-victoria
TripleO Train containers
4.2.64-tripleo
AES-256
ctr
text/plain
None
passphrase
plaintext
plaintext
xts
application/octet-stream
base64
symmetric keys
encoded with base64
cbc
opaque
s3fuse | python package | 4.2.64 |
tvault-configurator | python package | 4.2.64.5 |
workloadmgr | python package | 4.2.64.5 |
workloadmgrclient | python package | 4.2.64 |
contegoclient | python package | 4.2.64 |
dmapi | deb package | 4.2.64 |
python3-dmapi | deb package | 4.2.64 |
tvault-contego | deb package | 4.2.64.5 |
python3-tvault-contego | deb package | 4.2.64.5 |
tvault-horizon-plugin | deb package | 4.2.64 |
python3-tvault-horizon-plugin | deb package | 4.2.64 |
s3-fuse-plugin | deb package | 4.2.64 |
python3-s3-fuse-plugin | deb package | 4.2.64 |
workloadmgr | deb package | 4.2.64.5 |
workloadmgrclient | deb package | 4.2.64 |
dmapi | rpm package | 4.2.64-4.2 |
python3-dmapi | rpm package | 4.2.64-4.2 |
puppet-triliovault | rpm package | 4.2.64-4.2 |
python3-contegoclient-el8 | rpm package | 4.2.64-4.2 |
tvault-contego | rpm package | 4.2.64.5-4.2 |
python3-tvault-contego | rpm package | 4.2.64.5-4.2 |
tvault-horizon-plugin | rpm package | 4.2.64-4.2 |
python3-tvault-horizon plugin-el8 | rpm package | 4.2.64-4.2 |
python-s3fuse-plugin-cent7 | rpm package | 4.2.64-4.2 |
python3-s3fuse-plugin | rpm package | 4.2.64-4.2 |
python3-trilio-fusepy | rpm package | 3.0.1-1 |
trilio-fusepy | rpm package | 3.0.1-1 |
workloadmgrclient | rpm package | 4.2.64-4.2 |
python3-workloadmgrclient-el8 | rpm package | 4.2.64-4.2 |
Gitbranch | hotfix-2-TVO/4.2 |
RHOSP13 containers | 4.2.64-hotfix-2-rhosp13 |
RHOSP16.1 containers | 4.2.64-hotfix-2-rhosp16.1 |
RHOSP16.2 containers | 4.2.64-hotfix-2-rhosp16.2 |
Kolla Ansible Victoria containers | 4.2.64-hotfix-2-victoria |
Kolla Ansible Wallaby containers | 4.2.64-hotfix-2-wallaby |
TripleO Train containers | 4.2.64-hotfix-2-tripleo |
Package/Container Names | Package Kind | Package Version/Container Tags |
contego | deb | 4.2.64 |
contegoclient | rpm | 4.2.64-4.2 |
contegoclient | deb | 4.2.64 |
contegoclient | python | 4.2.64 |
puppet-triliovault | rpm | 4.2.64-4.2 |
python3-contegoclient | deb | 4.2.64 |
python3-contegoclient-el8 | rpm | 4.2.64-4.2 |
python3-trilio-fusepy | rpm | 3.0.1-1 |
trilio-fusepy | rpm | 3.0.1-1 |
python3-workloadmgrclient | deb | 4.2.64.1 |
python3-workloadmgrclient-el8 | rpm | 4.2.64.1-4.2 |
python-workloadmgrclient | deb | 4.2.64.1 |
workloadmgrclient | python | 4.2.64.1 |
workloadmgrclient | rpm | 4.2.64.1-4.2 |
dmapi | python | 4.2.64.1 |
dmapi | rpm | 4.2.64.1-4.2 |
dmapi | deb | 4.2.64.1 |
python3-dmapi | deb | 4.2.64.1 |
python3-dmapi | rpm | 4.2.64.1-4.2 |
workloadmgr | deb | 4.2.64.10 |
workloadmgr | python | 4.2.64.10 |
tvault_configurator | python | 4.2.64.10 |
Package/Container Names | Package Kind | Package/Container Version/Tags |
python3-s3-fuse-plugin | deb | 4.2.64.1 |
python3-tvault-contego | deb | 4.2.64.10 |
s3-fuse-plugin | deb | 4.2.64.1 |
tvault-contego | deb | 4.2.64.10 |
python3-tvault-contego | rpm | 4.2.64.10-4.2 |
tvault-contego | rpm | 4.2.64.10-4.2 |
tvault-contego | python | 4.2.64.3 |
tvault-horizon-plugin | deb | 4.2.64.3 |
tvault-horizon-plugin | rpm | 4.2.64.3-4.2 |
tvault-horizon-plugin | python | 4.2.64.2 |
python3-tvault-horizon-plugin | deb | 4.2.64.3 |
python3-tvault-horizon-plugin-el8 | rpm | 4.2.64.3-4.2 |
python-s3fuse-plugin-cent7 | rpm | 4.2.64.1-4.2 |
python3-s3fuse-plugin | rpm | 4.2.64.1-4.2 |
s3fuse | python | 4.2.64.2 |
Name | Tag |
Gitbranch | hotfix-5-TVO/4.2 |
RHOSP13 containers | 4.2.64-hotfix-5-rhosp13 |
RHOSP16.1 containers | 4.2.64-hotfix-5-rhosp16.1 |
RHOSP16.2 containers | 4.2.64-hotfix-5-rhosp16.2 |
Kolla Ansible Victoria containers | 4.2.64-hotfix-5-victoria |
Kolla Ansible Wallaby containers | 4.2.64-hotfix-5-wallaby |
Kolla Yoga Containers | 4.2.64-hotfix-5-yoga |
TripleO Containers | 4.2.63-hotfix-5-tripleo |
**** | Tag Reference in Install/Upgrade Docs | Value | Comments |
1 | 4.2 Hotfix triliovault-cfg-scripts branch name | hotfix-3-TVO/4.2 | Label against the Trilio repositories from where required code to be pulled for upgrades. |
2 | 4.2 Hotfix RHOSP13 Container tag | 4.2.64-hotfix-3-rhosp13 | RHOSP13 Container tag for 4.2.HF3 |
3 | 4.2 Hotfix RHOSP16.1 Container tag | 4.2.64-hotfix-3-rhosp16.1 | RHOSP16.1 Container tag for 4.2.HF3 |
4 | 4.2 Hotfix RHOSP16.2 Container tag | 4.2.64-hotfix-3-rhosp16.2 | RHOSP16.2 Container tag for 4.2.HF3 |
5 | 4.2 Hotfix Kolla Victoria Container tag | 4.2.64-hotfix-3-victoria | Kolla Container tag against 4.2.HF3 |
6 | 4.2 Hotfix Kolla Wallaby Container tag | 4.2.64-hotfix-3-wallaby | Kolla Container tag against 4.2.HF3 |
7 | 4.2 Hotfix TripleO Container tag | 4.2.63-hotfix-3-tripleo | TripleO Train CentOS 7 Container tag for 4.2.HF3 |
Summary |
Restore failing while creating security group |
Tvault configuration failing with build 4.1.19 |
Configuration fails with pcs auth |
privsep Unhandled error: ConnectionRefusedError |
Tvault configuration failing with build 4.1.19 |
Datamover container restarting |
While deploying trilio-wlm 4.2 directly on the machine is getting stuck at workloadmgr package installation. |
trilio data mover pods stuck in reboot loop post stack update on RHOSP 13 |
Reassigning a workload from a deleted project fails |
Reassign of Workload from Deleted Project Fails SFDC #2821 |
default_tvault_dashboard_tvo-tvm not available after yum update |
workload policy shows incorrect start time |
tvault-config service is in the crash loop on 2 out of 3 nodes T4O cluster |
Trilio core functionality operations do not perform as expected when the master T4O node is powered off. |
backup stuck in uploading phase |
Backup failed at snapshot_network_topology |
| Package/Container Names | Package Kind | Package Version/Container Tags |
1 | contego | deb | 4.2.64 |
2 | contegoclient | rpm | 4.2.64-4.2 |
3 | contegoclient | deb | 4.2.64 |
4 | contegoclient | python | 4.2.64 |
5 | dmapi | rpm | 4.2.64-4.2 |
6 | dmapi | deb | 4.2.64 |
7 | puppet-triliovault | rpm | 4.2.64-4.2 |
8 | python3-contegoclient | deb | 4.2.64 |
9 | python3-contegoclient-el8 | rpm | 4.2.64-4.2 |
10 | python3-dmapi | deb | 4.2.64 |
11 | python3-dmapi | rpm | 4.2.64-4.2 |
12 | python3-s3-fuse-plugin | deb | 4.2.64 |
13 | python3-s3fuse-plugin | rpm | 4.2.64-4.2 |
14 | python3-trilio-fusepy | rpm | 3.0.1-1 |
15 | python-s3fuse-plugin-cent7 | rpm | 4.2.64-4.2 |
16 | s3fuse | python | 4.2.64 |
17 | s3-fuse-plugin | deb | 4.2.64 |
18 | trilio-fusepy | rpm | 3.0.1-1 |
19 | 4.2-RHOSP13-CONTAINER | Containers | 4.2.64-hotfix-3-rhosp13 |
20 | 4.2-RHOSP16.1-CONTAINER | Containers | 4.2.64-hotfix-3-rhosp16.1 |
21 | 4.2-RHOSP16.2-CONTAINER | Containers | 4.2.64-hotfix-3-rhosp16.2 |
22 | 4.2-KOLLA-CONTAINER Victoria | Containers | 4.2.64-hotfix-3-victoria |
23 | 4.2-KOLLA-CONTAINER Wallaby | Containers | 4.2.64-hotfix-3-wallaby |
24 | 4.2-TRIPLEO-CONTAINER | Containers | 4.2.64-hotfix-3-tripleo |
Package/Container Names | Package Kind | Package/Container Version/Tags |
1 | python3-tvault-contego | deb | 4.2.64.7 |
2 | tvault-contego | deb | 4.2.64.7 |
3 | python3-tvault-contego | rpm | 4.2.64.7-4.2 |
4 | tvault-contego | rpm | 4.2.64.7-4.2 |
5 | workloadmgr | deb | 4.2.64.6 |
6 | workloadmgr | python | 4.2.64.6 |
7 | tvault_configurator | python | 4.2.64.6 |
8 | tvault-horizon-plugin | deb | 4.2.64.1 |
9 | tvault-horizon-plugin | rpm | 4.2.64.1-4.2 |
10 | python3-tvault-horizon-plugin | deb | 4.2.64.1 |
11 | python3-tvault-horizon-plugin-el8 | rpm | 4.2.64.1-4.2 |
12 | python3-workloadmgrclient | deb | 4.2.64.1 |
13 | python3-workloadmgrclient-el8 | rpm | 4.2.64.1-4.2 |
14 | python-workloadmgrclient | deb | 4.2.64.1 |
15 | workloadmgrclient | python | 4.2.64.1 |
16 | workloadmgrclient | rpm | 4.2.64.1-4.2 |
| Artifacts | Reference |
1 | Release Date | Aug 25, 2022 |
2 | Debian URL |
3 | RPM URL |
4 | PIP URL |
| Summary | Workaround/Comments (if any) |
1 | encrypted volume backup fails with SSO user | Follow below steps if T4O is reconfigured with ‘creator’ role
workloadmgr trust-list 4. In order to create encrypted workload user needs to delete the existing trust which is created using other than ‘creator’ role workloadmgr trust-delete <TrustID> 5.create a new trust with ‘creator’ role workloadmgr trust-create creator 6.now create encrypted workload |
2 | additional security rule is getting added in shared security group after restore | It will go as known issue in 4.2HF3 and will be targeted in 4.2HF4 |
3 |
4 | [encrypted] Post restore of incremental snapshots centos instance is not getting booted | There is no workaround as such. But customer can only restore the already taken full snapshot |
5 | [Intermittent] In-place restore doesn't work for ext3 & ext4 file system in canonical bionic-queens | In-place restore doesn't work well for ext3 & ext4 file system in canonical bionic-queens. After in-place restore instance has data from the latest snapshot for ext3 & ext4 file system, however In-place restore was done for previous full/incremental snapshot. |
6 | Performance difference between encrypted & unencrypted WL/snapshot | With encryption in place, user would see some performance degradation against all operations done by Trilio. Stats below as per trials in Trilio Lab Snapshot time for LVM Volume Booted CentOS VM. Disk size 200 GB; total data including OS : ~108GB
Snapshot time for Windows Image booted VM. No additional data except OS. : ~12 GB
|
7 | get-importworkload-list and get-orphaned-workloads-list are showing the wrong list of WLs | Customer need to use --project option with importworkload-lists cli to get the list WLs that can be imported with particular openstack. workloadmgr workload-get-importworkloads-list --project_id <project_id> |
8 | File-search not displaying files present in logical vol on volume group (LVM) | If we create lvm partition using fdisk utility, then the file search will work. |
9 | Retention not working post snapshot mount/unmount operation | # List the Workload id for which Retention failing due to ownership change issue. # Fire the cmd chown -R nova:nova <WL_DIR> # After firing above cmd, now one should able to see the snapshot ownership as nova:nova. |
10 | [Barbican]File search on encrypted workload returns empty data | By default, if root directory is not having read permissions for group, then file search will also fail as it runs from nova user. |
11 | Single corrupted snapshot impacts import of all other valid snapshots causing file search failure | As per the current import design flow, if any single WL is corrupted (in current case few DB files were missing), then other good workloads get impacted during import, but import operation doesn’t stop OR fails. Respective wlm-api logs should show the error. To mitigate the impact, the identified corrupted WL should be manually removed from target backend followed by reinitialize and import. |
12 | Test email error message should be in readable and understandable format | NA |
13 | File search will not work on Canonical if wlm is running on container (lxc container in this case) | NA |
14 | Unable to create encrypted workload if T4O reconfigured with creator trustee role. | If T4O is initially configured with member as trustee role and then user reconfigures the same with creator as a trustee role, then this failure would occur. Workaround : Follow below steps if T4O is reconfigured with ‘creator’ role
|
Support for RHOSP17
Support for Canonical zed Openstack
Support for physical delete from DB against all delete operations
Verification of Jira issues targeted for 4.2.7 release
workloadmgr trust-create command is failing with error - There are multiple role entities named 'admin'
Selective restore failing: Invalid volume
Backport DB cleanup code from 5.0 to 4.2
Deleting snapshots show status as available in horizon UI
Observation : Snapshot for which delete operation is in-progress from UI , its status is showing as available instead deleting.
Workaround:
Wait for sometime to complete all the delete operations.Eventually all the snapshots will be deleted successfully.
Verification of Jira issues targeted for 4.2.6 release
Cohesity NFS/S3 storage backend support
Mounting a snapshot fails if the first disk of the File Recovery Manager VM is a CDROM
TVM HA configuration fails when one of the chosen Controller's hostname is part of any other TVM's hostname
Validation of keystone and s3 endpoint is stuck on the TVM UI
Temp volume creation taking too long
The httpd service is in a failed state on a freshly deployed T4O
The sshd option UseDNS should be set to "no" to avoid issues
[RHOSP 16.1.8 and RHOSP 16.2.4] Trilio Horizon container in reboot loop
Observation : Post upgrade from a previous release/hotfix or on fresh deployment, the Trilio Horizon container is in a reboot loop
Workaround:
Either of the below workarounds should be performed on the controller where the issue occurs for the horizon pod.
option-1: Restart the memcached service on controller using systemctl (command: systemctl restart tripleo_memcached.service).
option-2: Restart the memcached pod (command: podman restart memcached).
[Snapshot mount] Unable to see correct content after mounting snapshot
Observation : Snapshot mount using RHEL8 File recovery manager image is not showing any mounted device
Workaround:
Use RHEL7 image for File recovery manager vm instead RHEL8.
[Backup failure for HPE nimble storage volumes with timeout receiving packet error
Observation : Snapshot is failing for VM's that have volumes backed by a Nimble iSCSI SAN with a "timeout receiving packet" error
Workaround: add uxsock_timeout parameter
log into respective datamover container and add uxsock_timeout with value as 60000 (i.e. 60 sec) in /etc/multipath.conf. Restart datamover container
[Input/Output error while writing to Cohesity NFS share]
Observation : Input/Output error during qemu-img convert operation while writing to Cohesity NFS share
Workaround: For cohesity NFS use below nfs options during Trilio configuration and datamover deployment and if issue still persists then increase timeo and retrans parameter values in nfs options
nfs_options = nolock,soft,timeo=600,intr,lookupcache=none,nfsvers=3,retrans=10
Support for Kolla Zed (Ubuntu & Rocky) OpenStack
Verification of Jira issues targeted for 4.2.8 release
Backup failing on cinder backend Fiber Channel.
Single VM backup (configurable) at a time out of workload having multiple VMs.
Snapshot and Selective/One Click Restore failing on quobyte.
Inplace restore fails saying no space left on device.
Specific workload fails to be restored; says VMDiskResourceSnap could not be found.
Restores are failing; error says security group rules already exist.
Snapshot intermittently fails with IO error while backup uploading.
Stopping multipath volumes is taking huge time.
Upgrading or deploying RHOSP 16.2.5 results in TrilioVaultWLM service and respective endpoints disappearing.
Deleting snapshots show status as available in horizon UI
Observation : Snapshot for which delete operation is in-progress from UI , its status is showing as available instead deleting.
Workaround:
Wait for sometime to complete all the delete operations.Eventually all the snapshots will be deleted successfully.
deb [trusted=yes] /
LP Bug : [
Package/Container Names
Package Kind
Package Version/Container Tags
contego
deb
4.2.64
contegoclient
rpm
4.2.64-4.2
contegoclient
deb
4.2.64
contegoclient
python
4.2.64
puppet-triliovault
rpm
4.2.64-4.2
python3-contegoclient
deb
4.2.64
python3-contegoclient-el8
rpm
4.2.64-4.2
python3-trilio-fusepy
rpm
3.0.1-1
trilio-fusepy
rpm
3.0.1-1
Package/Container Names
Package Kind
Package/Container Version/Tags
tvault-contego
deb
4.2.64.20
python3-tvault-contego
rpm
4.2.64.20-4.2
tvault-contego
rpm
4.2.64.20-4.2
tvault-contego
python
4.2.64.12
tvault_configurator
python
4.2.64.16
workloadmgr
python
4.2.64.15
workloadmgr
deb
4.2.64.15
python3-tvault-contego
deb
4.2.64.20
python3-workloadmgrclient
deb
4.2.64.2
python3-workloadmgrclient-el8
rpm
4.2.64.2-4.2
python-workloadmgrclient
deb
4.2.64.2
workloadmgrclient
python
4.2.64.2
workloadmgrclient
rpm
4.2.64.2-4.2
dmapi
python
4.2.64.2
dmapi
rpm
4.2.64.2-4.2
dmapi
deb
4.2.64.2
python3-dmapi
deb
4.2.64.2
python3-dmapi
rpm
4.2.64.2-4.2
python3-s3-fuse-plugin
deb
4.2.64.3
python3-tvault-horizon-plugin
deb
4.2.64.4
s3-fuse-plugin
deb
4.2.64.3
tvault-horizon-plugin
deb
4.2.64.4
s3fuse
python
4.2.64.4
tvault-horizon-plugin
python
4.2.64.3
python-s3fuse-plugin-cent7
rpm
4.2.64.3-4.2
python3-s3fuse-plugin
rpm
4.2.64.3-4.2
python3-tvault-horizon-plugin-el8
rpm
4.2.64.4-4.2
tvault-horizon-plugin
rpm
4.2.64.4-4.2
python3-s3fuse-plugin-el9
rpm
4.2.64.3-4.2
python3-contegoclient-el9
rpm
4.2.64.1-4.2
python3-trilio-fusepy-el9
rpm
3.0.1-1
python3-tvault-horizon-plugin-el9
rpm
4.2.64.2-4.2
python3-workloadmgrclient-el9
rpm
4.2.64.2-4.2
python3-dmapi-el9
rpm
4.2.64.2-4.2
python3-tvault-contego-el9
rpm
4.2.64.8-4.2
Name
Tag
Gitbranch
TVO/4.2.7
RHOSP13 containers
4.2.7-rhosp13
RHOSP16.1 containers
4.2.7-rhosp16.1
RHOSP16.2 containers
4.2.7-rhosp16.2
Kolla Ansible Victoria containers
4.2.7-victoria
Kolla Ansible Wallaby containers
4.2.7-wallaby
Kolla Yoga Containers
4.2.7-yoga
TripleO Containers
4.2.7-tripleo
Package/Container Names
Package Kind
Package Version/Container Tags
contego
deb
4.2.64
contegoclient
rpm
4.2.64-4.2
contegoclient
deb
4.2.64
contegoclient
python
4.2.64
puppet-triliovault
rpm
4.2.64-4.2
python3-contegoclient
deb
4.2.64
python3-contegoclient-el8
rpm
4.2.64-4.2
python3-trilio-fusepy
rpm
3.0.1-1
trilio-fusepy
rpm
3.0.1-1
python3-workloadmgrclient
deb
4.2.64.1
python3-workloadmgrclient-el8
rpm
4.2.64.1-4.2
python-workloadmgrclient
deb
4.2.64.1
workloadmgrclient
python
4.2.64.1
workloadmgrclient
rpm
4.2.64.1-4.2
dmapi
python
4.2.64.1
dmapi
rpm
4.2.64.1-4.2
dmapi
deb
4.2.64.1
python3-dmapi
deb
4.2.64.1
python3-dmapi
rpm
4.2.64.1-4.2
python3-s3-fuse-plugin
deb
4.2.64.1
python3-tvault-horizon-plugin
deb
4.2.64.3
s3-fuse-plugin
deb
4.2.64.1
tvault-horizon-plugin
deb
4.2.64.3
s3fuse
python
4.2.64.2
tvault-horizon-plugin
python
4.2.64.2
python-s3fuse-plugin-cent7
rpm
4.2.64.1-4.2
python3-s3fuse-plugin
rpm
4.2.64.1-4.2
python3-tvault-horizon-plugin-el8
rpm
4.2.64.3-4.2
tvault-horizon-plugin
rpm
4.2.64.3-4.2
Package/Container Names
Package Kind
Package/Container Version/Tags
tvault-contego
deb
4.2.64.13
python3-tvault-contego
rpm
4.2.64.13-4.2
tvault-contego
rpm
4.2.64.13-4.2
tvault-contego
python
4.2.64.6
tvault_configurator
python
4.2.64.15
workloadmgr
python
4.2.64.11
workloadmgr
deb
4.2.64.11
python3-tvault-contego
deb
4.2.64.13
Name
Tag
Gitbranch
TVO/4.2.6
RHOSP13 containers
4.2.6-rhosp13
RHOSP16.1 containers
4.2.6-rhosp16.1
RHOSP16.2 containers
4.2.6-rhosp16.2
Kolla Ansible Victoria containers
4.2.6-victoria
Kolla Ansible Wallaby containers
4.2.6-wallaby
Kolla Yoga Containers
4.2.6-yoga
TripleO Containers
4.2.6-tripleo
Package/Container Names
Package Kind
Package Version/Container Tags
contegoclient
python
4.2.64
s3fuse
python
4.2.64.4
dmapi
python
4.2.64.2
workloadmgr
python
4.2.64.15
contego
deb
4.2.64
contegoclient
deb
4.2.64
python3-contegoclient
deb
4.2.64
dmapi
deb
4.2.64.2
python-workloadmgrclient
deb
4.2.64.2
python3-dmapi
deb
4.2.64.2
python3-workloadmgrclient
deb
4.2.64.2
python3-s3-fuse-plugin
deb
4.2.64.3
s3-fuse-plugin
deb
4.2.64.3
contegoclient
rpm
4.2.64-4.2
puppet-triliovault
rpm
4.2.64-4.2
python3-contegoclient-el8
rpm
4.2.64-4.2
python3-trilio-fusepy
rpm
3.0.1-1
trilio-fusepy
rpm
3.0.1-1
dmapi
rpm
4.2.64.2-4.2
python3-dmapi
rpm
4.2.64.2-4.2
python3-workloadmgrclient-el8
rpm
4.2.64.2-4.2
workloadmgrclient
rpm
4.2.64.2-4.2
python-s3fuse-plugin-cent7
rpm
4.2.64.3-4.2
python3-s3fuse-plugin
rpm
4.2.64.3-4.2
Package Names
Package Kind
Package/Container Version/Tags
tvault_configurator
python
4.2.64.22
tvault-contego
python
4.2.64.18
tvault-horizon-plugin
python
4.2.64.4
workloadmgr
python
4.2.64.22
python3-tvault-contego
deb
4.2.64.26
python3-tvault-horizon-plugin
deb
4.2.64.5
tvault-contego
deb
4.2.64.26
tvault-horizon-plugin
deb
4.2.64.5
workloadmgr
deb
4.2.64.21
python3-tvault-contego
rpm
4.2.64.26-4.2
python3-tvault-contego-el9
rpm
4.2.64.14-4.2
python3-tvault-horizon-plugin-el8
rpm
4.2.64.5-4.2
tvault-contego
rpm
4.2.64.26-4.2
tvault-horizon-plugin
rpm
4.2.64.5-4.2
Name
Tag
Gitbranch
TVO/4.2.8
RHOSP13 containers
4.2.8-rhosp13
RHOSP16.1 containers
4.2.8-rhosp16.1
RHOSP16.2 containers
4.2.8-rhosp16.2
Kolla Ansible Victoria containers
4.2.8-victoria
Kolla Ansible Wallaby containers
4.2.8-wallaby
Kolla Yoga Containers
4.2.8-yoga
Kolla Zed Containers
4.2.8-zed
TripleO Containers
4.2.8-tripleo