Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Push SemVer tags to perconalab/pmm-client too

Description

Impact on the User: User who by mistake, or because of some old historical habit use percona*lab* images  as official releases images can get the old version, not the released one 

STR

  1. docker pull percona*lab*/pmm-client:2

Expected results

  • the latest released docker for pmm-client 

Given results

  • as for now, the user will get 2.12 version 

 

:2 was replaced by  2.12.0 image. it  will not be changed automatically until the bug is fixed 

 

Original report:

In PMM-5799, we decided to not push SemVer tags 2, 2.m, 2.m.p to perconalab/pmm-client anymore. But we still have old 2 tag there that is incorrect now: https://hub.docker.com/layers/perconalab/pmm-client/2/images/sha256-950c94c43b785322588c375bd45da941d8b5aeb04efd5828169e5c76e5f2995a?context=explore Let's remove it.

Removing that tag did not help: docker pull perconalab/pmm-client:2 still works. Let's push 2, 2.m, 2.m.p to both perconalab/pmm-client and percona/pmm-client.

How to test

None

How to document

None

Activity

Evgeniy Patlan 
December 3, 2020 at 12:32 PM

 pushed docker image to perconalab with tags 2, 2.12 and 2.12.0

Alexey Palazhchenko 
December 3, 2020 at 12:15 PM

docker pull perconalab/pmm-client:2 still works. There are some mentions on the internets about that problem without any workarounds.

It sounds like we have to push 2, 2.m, 2.m.p release tags to perconalab/pmm-client too.

Alexey Palazhchenko 
December 2, 2020 at 1:01 PM

I will check if docker pull perconalab/pmm-client:2 will start failing tomorrow

Evgeniy Patlan 
December 2, 2020 at 12:56 PM

done

Done

Details

Assignee

Reporter

Priority

Components

Labels

Fix versions

Sprint

Parent

Created December 2, 2020 at 9:08 AM
Updated March 6, 2024 at 3:33 AM
Resolved December 7, 2020 at 10:26 AM