geo-install script fails with "gdk: command not found" error

Problem

The geo-install script fails during fresh installation with the following error:

./support/tool-version-manager-exec: line 26: gdk: command not found

This error occurs right after the first make bootstrap step during the Geo easy installation process.

Steps to reproduce

1. Follow the Geo easy installation guide: https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/doc/howto/geo.md#easy-installation
2. Run the geo-install script on a fresh system
3. Observe the error after make bootstrap completes

Expected behavior

The geo-install script should complete successfully without command not found errors.

Actual behavior

The script fails with gdk: command not found error, preventing successful Geo installation.

Click to expand Slack conversation

https://gitlab.slack.com/archives/C7U95P909/p1761684984572869

Anyone getting this on a fresh geo-install ?
./support/tool-version-manager-exec: line 26: gdk: command not found
Right after the first make bootstrap


mkozono
  Today at 10:58 AM
I assume the failing line is the next one running gdk install, but it seems to work when I cd into gdk and run it manually. (Though I didn't add the options that the script does.)
❯ cd gdk
❯ which gdk
/Users/mkozono/.local/share/mise/installs/ruby/3.3.9/bin/gdk
❯ ./support/tool-version-manager-exec . gdk install
Bundle check passed.

--------------------------------------------------------------------------------
Cloning https://gitlab.com/gitlab-org/gitlab.git
--------------------------------------------------------------------------------
(edited)


Natanael Silva
  Today at 11:59 AM
I don't reinstall my gdk it's been a bit, might need to do it soon
New


douglas
  Today at 12:05 PM
I had this issue last time I reinstalled my GDK. I was lazy at the time, so I manually copied the script's commands into my terminal :see_no_evil:
:stuck_out_tongue:
1



mkozono
  Today at 1:49 PM
I think the last geo-install CI job that passed was 9 Oct https://gitlab.com/gitlab-org/gitlab-development-kit/-/jobs/11666145810
The next one failed with the same error as the latest main failure 13 Oct https://gitlab.com/gitlab-org/gitlab-development-kit/-/jobs/11705083542. Though apparently many merges to master don't run the geo-install CI job. And none of the scheduled jobs run it.
But the failure in main occurs much later than in gdk_install . It occurs during make geo-secondary-setup
/home/gdk/.gitlab-ci-cache/ruby/bundle/ruby/3.3.0/gems/activerecord-7.1.5.2/lib/active_record/connection_adapters/postgresql/database_statements.rb:19:in `exec': PG::UndefinedTable: ERROR:  relation "feature_gates" does not exist (ActiveRecord::StatementInvalid)
LINE 10:  WHERE a.attrelid = '"feature_gates"'::regclass
                             ^
(edited)


mkozono
  19 minutes ago
Probably the job doesn't fail during the gdk_install function because the job is based on the mise-bootstrapped-gdk-installed image. And gdk command is probably already available in the context that the function calls it.

Impact

This prevents users from successfully setting up Geo using the easy installation method, affecting the reliability of the GDK setup process.