Version 19.0

July 7, 2023

Release Overview

The new features:

Epic/Module

Story/Task

Description

Security

https://accelario.atlassian.net/browse/LOKI-1838

Enable HTTPS protocol for GUI of virtualization app

Self-service deploy

https://accelario.atlassian.net/browse/LOKI-2031

Self-service deployment for Native SQL Server Backup GI

User management

https://accelario.atlassian.net/browse/LOKI-2034

Change login password for both "Admin" and "Data users"

Self-service deploy

https://accelario.atlassian.net/browse/LOKI-2030

Install source and target Windows agents as executable

Self-service deploy

https://accelario.atlassian.net/browse/LOKI-2081

Install source and target Linux agents as self-contained executable

Self-service deploy

https://accelario.atlassian.net/browse/LOKI-2035

Use the self-service wizard to configure additional test data environments for both Oracle and SQL Server

PostgreSQL

https://accelario.atlassian.net/browse/LOKI-2037

Create a PostgreSQL Live GI Read Write database

 

The list of known issues found during the last code freeze:

Issue key

Summary

LOKI-2184

Change password. Menu is available for AD users

LOKI-2181

MSSQL Self-service. Incorrect text on step Select target database

LOKI-2180

Source Management. Incorrect error message

LOKI-2173

Remove subscriptions from VDB after it starts

LOKI-2171

Wrong port is displayed in VDB info

LOKI-2170

Self-service deployment for Native SQL. The button “Rerun” does not work

LOKI-2166

Self-service deployment for Native SQL. There is no way to change the port

LOKI-2164

Self-service deployment for Native SQL. Validation fails same instanceName that already exists on this agent

LOKI-2158

Self-service deployment for Native SQL. The script returns an invalid value(floating bug)

LOKI-2128

Always show correct error details in the log , when SQL Server auto sync is failing

LOKI-2127

Backup folder located on the same machine as the GI-Agent might cause an access issue

LOKI-2125

Special characters in native backup shared folder cause MSSQL autosync to fail

LOKI-2073

System Setup. The Host Name/IP field becomes empty after a page refresh

LOKI-2070

IM/LOKI Integration. Linked data isn't removed after rollback to non-masked snapshot

LOKI-2068

IM/LOKI Integration. DS and env isn't removed after remove VDB

LOKI-2066

VDB management. Remove masking button is shown for VDB after remove related Datasource and Environment in masking

LOKI-2065

Only on loki_for_pm env. VDB management.Error "Client failed to createMaskingDataSource. Response code: 400, response message: Impossible to create the DataSource with existed name Virtualization VDB Clone1"

 

Testing status:

  • The manual regression tests -  completed 

https://docs.google.com/spreadsheets/d/18JXYqfgl0T6KtpWdrR6W9JAlS5I9jA1Z/edit?pli=1#gid=1742277043

  • The automated smoke tests -  completed 

 

  • The automated regression tests -  completed 

 

No critical bugs were found during the regression testing.

  • All supported versions have been tested and work as expected:

    • ORACLE

      • RMAN v11

      • RMAN v12

      • LIVE v12

      • RMAN v19 nonDG

      • RMAN v19 StandBy + same host

      • RMAN v19 RAC-to-single

      • RMAN v19 RAC-to-RAC

      • LIVE v19

    • PostgreSQL

      • LIVE v13 ubuntu 20

      • LIVE v13 RHEL/CentOS 7

      • LIVE v13 RHEL/CentOS 8

      • LIVE v14 ubuntu 20

      • LIVE v14 RHEL/CentOS 7

      • LIVE v14 RHEL/CentOS 8

    • MSSQL

      • LIVE v2016 (NFS, ISCSI)

      • Native Backup v2016 (NFS, ISCSI)

      • LIVE v2019 (NFS, ISCSI)

      • Native Backup v2019 (NFS, ISCSI)