[PMM-10391] External clickhouse using version > 22.5.2, not working in PMM - Percona JIRA

XML

Word

Printable

Regression Issue:

Yes
Found by Automation:

Yes
Story Points:
3
Epic Link:
High Availability in PMM - Stage 2 - Extract Data Sources
Needs Review:
Yes
Needs QA:
Yes
Needs Doc:
Yes
Platform Team:
C/S Core
How to test:
Hide

Setup external ClickHouse server

Run PMM Server configured to use external clickhouse with older version and mounted volume. Gather queries.

Move to latest clickhouse image and mount that volume with already gathered metrics.

Run latest clickhouse without mounted volume.

Test setup repository
git checkout to clickhouse tag before use with:

git checkout tags/clickhouse
Show
Setup external ClickHouse server Run PMM Server configured to use external clickhouse with older version and mounted volume. Gather queries. Move to latest clickhouse image and mount that volume with already gathered metrics. Run latest clickhouse without mounted volume. Test setup repository git checkout to clickhouse tag before use with: git checkout tags/clickhouse

Preconditions:

STR.

Expected result:
Query Analytics displayed

Actual Result:
Error displayed and no queries are available.{}

How to test:

Setup external ClickHouse server
Run PMM Server configured to use external clickhouse with older version like for example clickhouse/clickhouse-server:22.6.9.11-alpine and with mounted volume to check that users with old data will not suffer from moving to new clickhouse.
Then wait for around 5 minutes when queries is saved and showed up. Then change clickhouse to newer version for example clickhouse/clickhouse-server:22.8.14.53-alpine and use that old volume. There shouldn't be any errors.
Second case is to check that on newly created environment. Run same latest clickhouse without mounted volume. There are also shouldn't be any errors.

clones

PMM-10165 Contacts: When free user who is part of SN organization uses deep links he can access contacts

is cloned by

PMM-10547 Force diconnect from portal is returning an error, but disconnect is successful