Vera 2023.2 Upgrade Tasks

Owned by HB Farris
Last updated: Jan 19, 2024 by John Berek
2 min read

For upgrades from versions prior to 2022.2: a two step upgrade process must be followed. Please upgrade to 2023.1 first, then upgrade to 2023.2. If the two step process is not followed, then the connections will not be properly imported from the Synchronization Policy.

Starting with 2023.2.3, older SSL certificates used by the Web Portal for HTTPS may no longer work with Vera. This is due to Node.js no longer supporting certificates using the RC2 ciphers. When upgrading, make sure to create a new certificate PFX file with a supported cipher.

We introduced new containers to improve performance. The deployment script (e.q. docker-compose-yml) needs to be updated to include the new images. Please see Upgrade the Vera Server Applications for more information.

  1. tricentis/vera-api-connections-testconnection - Internal API to for connection tests

  2. tricentis/vera-api-qtest-routeactions - Public API for Route Actions from qTest

  3. tricentis/vera-api-routes-routeevents - Internal API for Approval Events (Task Approved, Task Rejected, Route Completed)

  4. tricentis/vera-server-legacy - Legacy Vera Server components that have not migrated to microservices (replaces tx3/Vera-server).

  5. tricentis/vera-worker-qtest - Worker to handle qTest actions.

There is a sample docker-compose file on the Vera Deployment with Docker page

Vera 2023.2 introduced new Connection and Policy Managment features. Vera will automatically make the following updates when you upgrade to Vera 2023.2 to support these new features.

  1. The system will mark the current Default Records Management Policy in Policy Managment as the DEFAULT policy

  2. The system will mark the current Default Approval Policy in Policy Managment as the DEFAULT policy

  3. The system will move the Default Synchronization Policy in Policy Managment to Connections under Settings in Vera Administration Web Portal

  4. The system will add the following databases and collections:

    1. New Database: tx3-vera-connections:

      1. Collection: connections

    2. New Database: tx3-vera-webhooks

      1. Collection: webhook-callbacks

    3. New Database: vera-qtest-routeactions-sagas

      1. Collection: job-attempts

      2. Collection: job-types

      3. Collection: jobs

Additional Logging Options

The following logging options are now now available to be added to the logging-settings.yml file.

  • API qTest RouteActions

  • Worker qTest

  • API Routes RouteEvents

  • Webhooks

  • Connections

For more information on logging settings, see Updating the Logging Level for VERA Server

Network Communication Changes

With the introduction of microservices for the qTest module, various network changes will need to be implemented to ensure qTest - Vera connectivity. See this page for more information on the ports that will be required after the upgrade: Required Ports

MongoDB Compatibility Update

Vera now requires a minimum MongoDB version of 5.0. Please ensure your MongoDB is updated prior to upgrading Vera to the latest version.

Current MongoDB Version

Upgrade Path

Current MongoDB Version

Upgrade Path

4.2.x

  1. Upgrade to MongoDB 4.4:  https://www.mongodb.com/docs/v5.0/release-notes/4.4-upgrade-standalone/

  2. Upgrade to MongoDB 5.x: https://www.mongodb.com/docs/manual/release-notes/5.0-upgrade-standalone/

  3. (Optional) Upgrade to MongoDB 6.x: https://www.mongodb.com/docs/manual/release-notes/6.0-upgrade-standalone/

4.4.x

  1. Upgrade to MongoDB 5.x: https://www.mongodb.com/docs/manual/release-notes/5.0-upgrade-standalone/

  2. (Optional) Upgrade to MongoDB 6.x: https://www.mongodb.com/docs/manual/release-notes/6.0-upgrade-standalone/

5.x

  1. (Optional) Upgrade to MongoDB 6.x: https://www.mongodb.com/docs/manual/release-notes/6.0-upgrade-standalone/

6.x

No upgrade necessary.