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

Gitpod tries to pull Theia image with a tag that does not exist #4679

Closed
corneliusludmann opened this issue Jul 1, 2021 · 4 comments · Fixed by #4731
Closed

Gitpod tries to pull Theia image with a tag that does not exist #4679

corneliusludmann opened this issue Jul 1, 2021 · 4 comments · Fixed by #4731
Assignees
Labels
operations: past incident This issue arose during a past incident or its post-mortem priority: highest (user impact) Directly user impacting type: needs triage We've seen the issue but need to investigate to decide what type of issue it is

Comments

@corneliusludmann
Copy link
Contributor

  • See Can not open workspaces with Theia editor #4672
  • I tagged eu.gcr.io/gitpod-core-dev/build/ide/theia@sha256:537433f51fc21561d117c65746601eed95a8f9e08d8d31e81b03defdea65e238 by hand with tag commit-f8da2b7b725c2a0949f904ead725763923b653ea, now it works
  • We need to investigate why this missing tag happened in the first place
@corneliusludmann corneliusludmann added the type: needs triage We've seen the issue but need to investigate to decide what type of issue it is label Jul 1, 2021
@meysholdt
Copy link
Member

meysholdt commented Jul 1, 2021

Probably not the cause, but it makes finding stuff a bit harder:
Commit f8da2b7b725c2a0949f904ead725763923b653ea is not on main

The build for commit ...53ea is gitpod-build-jh-track-user-deletion.0 and the Theia image is not part of the build results:

image

@meysholdt
Copy link
Member

docker run eu.gcr.io/gitpod-core-dev/build/versions:jh-track-user-deletion.0 cat /versions.yaml returns

theiaImage:
      version: commit-195a305c297b4989e26d075f65f036f3bbfe34c6

Since that version is different from the one Cornelius posted, I suspect the cause is a config error: The Theia image is being pulled using a tag that was designated for a another image.

@meysholdt
Copy link
Member

From the prod server k8s deployment:

        - name: SERVER_VERSION
          value: commit-f8da2b7b725c2a0949f904ead725763923b653ea
(...)
        - name: THEIA_IMAGE_REPO
          value: eu.gcr.io/gitpod-core-dev/build/ide/theia

It looks like the Theia image is using the server-version.

- name: SERVER_VERSION
value: "{{ template "gitpod.comp.version" $this }}"
- name: SHLVL
value: "1"
- name: THEIA_PORT
value: "{{ .Values.components.workspace.ports.http.containerPort | toString }}"
- name: THEIA_IMAGE_REPO
value: "{{ template "gitpod.comp.imageRepo" (dict "root" . "gp" $.Values "comp" .Values.components.workspace.theiaImage) }}"

The server should obtain+use the Theia-version.

@csweichel csweichel added operations: past incident This issue arose during a past incident or its post-mortem priority: highest (user impact) Directly user impacting labels Jul 2, 2021
@corneliusludmann corneliusludmann self-assigned this Jul 7, 2021
@corneliusludmann
Copy link
Contributor Author

Indeed, it takes the server version as fallback whenthe Theia version is not set:

readonly theiaVersion = process.env.THEIA_VERSION || this.serverVersion;
readonly theiaImageRepo = process.env.THEIA_IMAGE_REPO || 'unknown';
readonly theiaMounted = process.env.THEIA_MOUNTED === "true";
readonly ideDefaultImage = `${this.theiaImageRepo}:${this.theiaVersion}`;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
operations: past incident This issue arose during a past incident or its post-mortem priority: highest (user impact) Directly user impacting type: needs triage We've seen the issue but need to investigate to decide what type of issue it is
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants