Migration from previous versions
Migration from 3.6.1 to 3.7.0
PQM deletes all RabbitMQ 0.9.1 classic queues. All data in the queues are deleted. PQM creates RabbitMQ 0.9.1 quorum queues.
Migration from 3.6.0 to 3.6.1
With the latest release, IAS supports authentication for the Deviation Processor (SMDP). When SMDP is enabled, the appropriate service account role needs to be assigned to PQM.
See section Service Account Roles for more information.
Migration from 3.4.0 to 3.5.0
The Ingress controller name changed from tgw-ingress to pqm-ingress. The old tgw-ingress is unused and usually cleaned up by HELM automatically. In case it’s not, the path conflict and the old ingress needs to be deleted manually.
Migration from 3.0.x to 3.1.x
We have renamed a couple of entities in RabbitMQ.
The following entities can be deleted if they are still visible after successful deployment:
Queues
-
q.pqm.mdm-integration-worker.new -
q.pqm.mdm-integration-worker -
q.pqm.mdm-integration-wait -
q.pqm.mdm-integration-wait.new -
q.pqm.contract-created-worker -
q.pqm.contract-created-wait -
q.pqm.tenant-removed-worker -
q.pqm.tenant-removed-worker-new -
q.pqm.tenant-removed-wait -
q.pqm.tenant-removed-wait-new -
q.pqm.dlq.integration-events
Migration from CPM 1.5.x to PQM 3.0.x
This step is relevant if you were a user of the Condition and Process Monitoring Module (CPM).
The migration is not a zero-downtime migration. Before starting the migration:
-
Prepare the new PQM databases with the proper user/schema and access rights
-
Add PQM 3.0.x to inventory and run the HELM deployment
-
Make sure all necessary account roles are applied for all the tenants that should use PQM
-
To check that the service account roles are properly setup:
-
Open the PQM UI and check (for every tenant that should use PQM):
-
that there are devices present - if there are no devices, stop the migration and check the PQM deployment state - check the PQM → MDM service account roles.
-
check that PQM receives data (Processes and Machine data) by looking at a device that should receive data from Connectivity, if there is no data coming in, stop the migration and check the PQM deployment state - check the Connectivity → PQM service account roles.
-
-
Remove CPM from inventory and run the HELM deployment (uninstall it).
-
Execute the Influx database migration steps described in the following sections. No migration of the relational database needed.