Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deb repo inconsistent versions available #8166

Closed
klizhentas opened this issue Sep 7, 2021 · 4 comments
Closed

Deb repo inconsistent versions available #8166

klizhentas opened this issue Sep 7, 2021 · 4 comments
Assignees
Labels
bug c-10 Internal Customer Reference c-gj Internal Customer Reference release-engineering

Comments

@klizhentas
Copy link
Contributor

Description

It seems that with build infrastructure only one version is available at a time, and a build run modifies the version from 7.x to 6.x is back based on what last build has been run.

For example:

teleport 7.x back disappeared from https://deb.releases.teleport.dev/ stable main and now there is only 6.x there

@keenan-v1
Copy link

This is a huge blocker right now as our infrastructure is designed to use apt to install Teleport.

@wadells
Copy link
Contributor

wadells commented Nov 12, 2021

Recommended workaround, until we refactor the apt repositories:

Do not use the repo, instead, download and install your prefered teleport, teleport-ent, or teleport-ent-fips deb directly:

$ curl -O https://get.gravitational.com/teleport_7.3.3_amd64.deb
# snip ...
$ apt install ./teleport_7.3.3_amd64.deb
# snip ...
Setting up teleport (7.3.3) ...
$ teleport version
Teleport v7.3.3 git:v7.3.3-0-g47ccf9e5f go1.16.2

@webvictim
Copy link
Contributor

Got hit by this myself today.

wadells added a commit that referenced this issue Dec 4, 2021
The debian repo is currently broken, and we shouldn't recommend
customers use it until it is fixed.

Contributes to #8166
wadells added a commit that referenced this issue Dec 4, 2021
The debian repo is currently broken, and we shouldn't recommend
customers use it until it is fixed.

Contributes to #8166

(cherry picked from commit df31462)
wadells added a commit that referenced this issue Dec 4, 2021
The debian repo is currently broken, and we shouldn't recommend
customers use it until it is fixed.

Contributes to #8166

(cherry picked from commit df31462)
wadells added a commit that referenced this issue Dec 4, 2021
The debian repo is currently broken, and we shouldn't recommend
customers use it until it is fixed.

Contributes to #8166

(cherry picked from commit df31462)
wadells added a commit that referenced this issue Dec 4, 2021
The debian repo is currently broken, and we shouldn't recommend
customers use it until it is fixed.

Contributes to #8166

(cherry picked from commit df31462)
(cherry picked from commit 35e5c5f)
wadells added a commit that referenced this issue Dec 4, 2021
The debian repo is currently broken, and we shouldn't recommend
customers use it until it is fixed.

Contributes to #8166

(cherry picked from commit df31462)
(cherry picked from commit aba4876)
wadells added a commit that referenced this issue Dec 4, 2021
The debian repo is currently broken, and we shouldn't recommend
customers use it until it is fixed.

Contributes to #8166

(cherry picked from commit df31462)
(cherry picked from commit aba4876)
wadells added a commit that referenced this issue Dec 4, 2021
With 8.0 released and a long term fix to
#8166 outstanding, we do
not want to publish 7.0 debs to deb.releases.teleport.dev until we've
moved off reprepo.
wadells added a commit that referenced this issue Dec 4, 2021
With 7.0 released and a long term fix to
#8166 outstanding, we do
not want to publish 6.X debs to deb.releases.teleport.dev until we've
moved off reprepo.

(cherry picked from commit 377b1929633ca42e6b54914d3082198cace65bc6)
wadells added a commit that referenced this issue Dec 4, 2021
With 6.0 released and a long term fix to
#8166 outstanding, we do
not want to publish 5.0 debs to deb.releases.teleport.dev until we've
moved off reprepo.

(cherry picked from commit 377b1929633ca42e6b54914d3082198cace65bc6)
russjones pushed a commit that referenced this issue Dec 5, 2021
With 7.0 released and a long term fix to
#8166 outstanding, we do
not want to publish 6.X debs to deb.releases.teleport.dev until we've
moved off reprepo.

(cherry picked from commit 377b1929633ca42e6b54914d3082198cace65bc6)
russjones pushed a commit that referenced this issue Dec 5, 2021
With 8.0 released and a long term fix to
#8166 outstanding, we do
not want to publish 7.0 debs to deb.releases.teleport.dev until we've
moved off reprepo.
russjones pushed a commit that referenced this issue Dec 15, 2021
With 6.0 released and a long term fix to
#8166 outstanding, we do
not want to publish 5.0 debs to deb.releases.teleport.dev until we've
moved off reprepo.

(cherry picked from commit 377b1929633ca42e6b54914d3082198cace65bc6)
wadells added a commit that referenced this issue Dec 20, 2021
The debian repo is currently broken, and we shouldn't recommend
customers use it until it is fixed.

Contributes to #8166

(cherry picked from commit df31462)
wadells added a commit that referenced this issue Dec 20, 2021
This patch makes a couple changes:

  1. deb archives are not published to apt if they're not the latest
     release ever
  2. both rpm and deb archives are no longer published to yum / apt if
     they contain any pre-release indicator or build metadata
  3. nothing is published if the commit isn't tagged.

Contributes to #8166
wadells added a commit that referenced this issue Dec 20, 2021
This patch makes a couple changes:

  1. deb archives are not published to apt if they're not the latest
     release ever
  2. both rpm and deb archives are no longer published to yum / apt if
     they contain any pre-release indicator or build metadata
  3. nothing is published if the commit isn't tagged.

Contributes to #8166
@pschisa pschisa added the c-gj Internal Customer Reference label Dec 21, 2021
wadells added a commit that referenced this issue Jan 7, 2022
This patch makes a couple changes:

  1. deb archives are not published to apt if they're not the latest
     release ever
  2. both rpm and deb archives are no longer published to yum / apt if
     they contain any pre-release indicator or build metadata
  3. nothing is published if the commit isn't tagged.

Contributes to #8166
wadells added a commit that referenced this issue Jan 12, 2022
This patch makes a couple changes:

  1. deb archives are not published to apt if they're not the latest
     release ever
  2. both rpm and deb archives are no longer published to yum / apt if
     they contain any pre-release indicator or build metadata
  3. nothing is published if the commit isn't tagged.

Contributes to #8166
wadells added a commit that referenced this issue Jan 14, 2022
This patch makes a couple changes:

  1. deb archives are not published to apt if they're not the latest
     release ever
  2. both rpm and deb archives are no longer published to yum / apt if
     they contain any pre-release indicator or build metadata
  3. nothing is published if the commit isn't tagged.

Contributes to #8166
wadells added a commit that referenced this issue Jan 14, 2022
This patch makes a couple changes:

  1. deb archives are not published to apt if they're not the latest
     release ever
  2. both rpm and deb archives are no longer published to yum / apt if
     they contain any pre-release indicator or build metadata
  3. nothing is published if the commit isn't tagged.

Contributes to #8166

(cherry picked from commit 8540533)
wadells added a commit that referenced this issue Jan 20, 2022
This patch makes a couple changes:

  1. deb archives are not published to apt if they're not the latest
     release ever
  2. both rpm and deb archives are no longer published to yum / apt if
     they contain any pre-release indicator or build metadata
  3. nothing is published if the commit isn't tagged.

Contributes to #8166

(cherry picked from commit 8540533)
wadells added a commit that referenced this issue Jan 21, 2022
This patch makes a couple changes:

  1. deb archives are not published to apt if they're not the latest
     release ever
  2. both rpm and deb archives are no longer published to yum / apt if
     they contain any pre-release indicator or build metadata
  3. nothing is published if the commit isn't tagged.

Contributes to #8166

(cherry picked from commit 8540533)
@wadells
Copy link
Contributor

wadells commented Feb 10, 2022

Current status: We're no longer seeing any regressions occuring (e.g. a teleport 7 in the repo after teleport 8 was already out) thanks to:

However, we don't yet have a way to track a specific major or minor version in apt. The future of this work is being tracked in #9770.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug c-10 Internal Customer Reference c-gj Internal Customer Reference release-engineering
Projects
None yet
Development

No branches or pull requests

7 participants