Details
-
Bug
-
Status: Pending Release
-
Medium
-
Resolution: Fixed
-
2.31.0
-
Yes
-
1
-
Yes
-
Yes
-
No
-
Server Integrations
-
Description
https://jira.percona.com/browse/PMM-10361 doesn't work again with dev-latest or RC:
Warning Failed 2m19s (x2 over 2m45s) kubelet Error: ErrImagePull Warning Failed 2m19s (x2 over 2m45s) kubelet Failed to pull image "percona/pmm-client:2.31.0": rpc error: code = Unknown desc = Error response from daemon: manifest for percona/pmm-client:2.31.0 not found: manifest unknown: manifest unknown
**
User impact:
DB cluster creation fails with unreleased versions of pmm-server
Steps to reproduce:
Start dev-latest pmm-server (or a FB which has 2.31.0 version of pmm-server)
Try to create a DB cluster in dbaas
Actual result:
Tries to pull image that doesn't exist yet
Normal Pulling 39m (x3 over 39m) kubelet Pulling image "percona/pmm-client:2.30.0" Warning Failed 39m (x3 over 39m) kubelet Failed to pull image "percona/pmm-client:2.30.0": rpc error: code = Unknown desc = Error response from daemon: manifest for percona/pmm-client:2.30.0 not found: manifest unknown: manifest unknown Warning Failed 39m (x3 over 39m) kubelet Error: ErrImagePull Warning Failed 39m (x3 over 39m) kubelet Error: ImagePullBackOff Normal BackOff 4m51s (x153 over 39m) kubelet Back-off pulling image "percona/pmm-client:2.30.0"
Expected result:
If pmm-server version is unreleased, perconalab/pmm-client:dev-latest should be pulled
Workaround:
Run pmm-server with env var
-e PERCONA_TEST_DBAAS_PMM_CLIENT=percona/pmm-client:2.29.0
Implementation Details:
- If PERCONA_TEST_DBAAS_PMM_CLIENT env variable is set, use the value from there.
- If it’s a released version: use the released version
- If it’s an unreleased version(has some suffix in the version value): use dev-latest
Attachments
Issue Links
- clones
-
-
- Done
-