PMM 2 Client repository is present in PMM v3 docker images
General
Escalation
General
Escalation
Description
When building PMM Server docker images, our build scripts install the Client using tarballs which are made available on the same machine. However, not only percona-pmm2-client.repo is present in /etc/yum.repos.d directory, but it is also enabled by default. It seems like percona-release is responsible for this behavior.
It causes a certain inconvenience (like having to disable it explicitly in v3) and makes no sense since the release of PMM v3.
Moreover, we suspect that percona-release will install this repo and enable it by default on any environment, not only in PMM Server.
Solution
Make sure percona-release does NOT enable any PMM Client repository at all.
Medium
When building PMM Server docker images, our build scripts install the Client using tarballs which are made available on the same machine. However, not only
percona-pmm2-client.repois present in/etc/yum.repos.ddirectory, but it is also enabled by default. It seems likepercona-releaseis responsible for this behavior.It causes a certain inconvenience (like having to disable it explicitly in v3) and makes no sense since the release of PMM v3.
Moreover, we suspect that
percona-releasewill install this repo and enable it by default on any environment, not only in PMM Server.Solution
Make sure
percona-releasedoes NOT enable any PMM Client repository at all.