Release notes


July 19, 2022

New Features

Availability of Redis

PDS now includes Redis version 7.0.2 as a data service.

Data service version and image selection

You can now deploy more than one data service version in PDS, and the corresponding image for that version.
For more information about:

Restrictions for selecting nodes per target cluster

PDS now allows you to select only a specific number of nodes to deploy each data service on a target cluster. You can select the nodes from the Deploy a data service dialog box → No. of Nodes dropdown.
For more information about the available number of nodes for each data service, refer to the Node restrictions section.

Add an empty application configuration template

You can now add an empty Application Configuration Template, and specify the application configuration parameters later when you deploy a data service.
For more information about adding an empty template, refer to the Add or manage an application configuration template topic.

Known issue

Issue Number Issue Description

DS-2399

The Redis data service does not include the default, empty application configuration and resource settings templates, in this release.

Workaround: Before deploying the Redis data service in PDS, the Admin must add an empty application configuration template and a resource settings template.

June 30, 2022

This release provides a seamless experience with a reduced number of vulnerabilities reported in the earlier versions.

New Feature

You can now view the status of your deployments. To view real-time events:

  1. In the Deployments page, select a deployed data service.

  2. In the deployment details page, select the vertical ellipsis button next to Edit. From the options, select View Deployment Health.

  3. In the Deployment Health window, select the Events tab.

Tip
You can also click the node hexagons, in the deployment details page, to view the Deployment Health window.

The status descriptions help you know the following information about your deployment:

  • whether it is failed or created successfully

  • reasons for the failure

  • timestamp

Known issue

Issue Number Issue Description

DS-2334

If your backup does not complete within the timeout value of 24 hours, then the backup eventually fails on the target cluster.

Workaround: Since the backup process will keep running inside the data service pod(s), you can terminate the backup process.

Jun 20, 2022

Known issues

Issue Number Issue Description

DS-2181

In the Metrics of a PostgreSQL deployment, under Application Details, the Server Session Count chart shows wrong Total count.

DS-2219

As an Admin, after adding a backup target, you can only edit the Name of the backup target but cannot change the Cloud account, Bucket name, Container name and Region of the backup target.

To change the fields, Pure Storage recommends to delete the backup target and a new backup target with the desired options in the fields.

May 25, 2022

Known issues

Issue Number Issue Description

DS-2078

When multiple PDS data services are deployed on the Portworx cluster, deployments may fail due to a lack of free space on Portworx volumes. The mounting file system enters read-only mode when the storage reaches 90% of its capacity, and it may be unavailable if some Portworx node pools go offline.

As PDS deployments depend on Portworx volumes, ensure that Portworx clusters are running without errors to avoid a data service deployment failure.

Apr 28, 2022

Announcing general availability for Portworx Data Services!

Known issues

Issue Number Issue Description

DS-1113

If you delete backup credentials manually using the pxctl credentials delete command, PDS fails to detect and recreate the credentials on the target cluster.

DS-1607

In some edge cases when all RabbitMQ pods are terminated at once, the first pod fails to start and the pod’s log contains the following messages: Waiting for Mnesia tables for 30000 ms, X retries left.

Resolution: Run kubectl exec -n <namespace> <pod_name> /srv/pds/pds-utils/rabbitmq_force_boot.sh to fix the issue.

DS-1927

Due to a bug in PostgreSQL exporter, an extra stale database connection does not allow deletion of a PostgreSQL database and shows the following error.
DROP DATABASE "database name"; ERROR: database "database name" is being accessed by other users DETAIL: There is 1 other session using the database.

Workaround:
Force drop: Use DROP DATABASE <database-name> WITH (FORCE); instead of DROP DATABASE <database-name>; It may fail if the database user does not have permissions to terminate existing database connections.

Exclude database from metrics collection: You can temporarily or permanently exclude a database from metrics collection which will not allow the postgresql exporter to connect to the database.

  1. Create new application configuration template called Exclude database metrics.

  2. Add deployment time variable called PG_EXPORTER_EXCLUDE_DATABASES.

  3. Set PG_EXPORTER_EXCLUDE_DATABASES to <database-name> when creating or editing a PostgreSQL data service deployment.

  4. Use DROP DATABASE <database-name>, to remove the database.


Last edited: Thursday, Apr 28, 2022