-
Notifications
You must be signed in to change notification settings - Fork 71
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
incident: prombench can't build Prometheus from main (stuck on react-app npm install) #832
Comments
Trying to bisect and do v3.2.0-rc.1 vs v3.0.0 prombench prometheus/prometheus#15973 EDIT: same failure https://github.com/prometheus/prometheus/actions/runs/13155085596/job/36710311857 |
I found last working prombench run on commit https://github.com/prometheus/prometheus/commits/665d1ba0cc62a6c3bb58274e91a1a62082298100 (used in prometheus/prometheus#15861) |
Commits to check (if #832 (comment) will succed)
|
Ok, it’s not something we did on main I think as the old commit that used to work, now doesn’t prometheus/prometheus#15861 (comment) This is env issue, either GKE, npm or prombench config. |
Handy script to resolve the situation for the PR:
|
This comment has been minimized.
This comment has been minimized.
Signed-off-by: bwplotka <bwplotka@gmail.com>
Debugging https://github.com/prometheus/test-infra/blob/master/tools/prometheus-builder/Dockerfile closer.
Perhaps too old npm and node versions? I noticed that
This is not entirely consistent with how Prometheus is building binaries on main and CI:
Let's see if it will work with 1.23-main: |
If I understand right Prom CI will do this to publish images:
Which means running:
Not sure how it gets UI assets though 🤔 |
prometheus/prometheus#15981 passed, so on GH action |
Signed-off-by: bwplotka <bwplotka@gmail.com>
Ok, no idea what was happenig but node upgrade helped. |
…ch runs This custom image is locally build from prometheus/golang-builder#296 that we agree to pause until Prometheus release. However, Prometheus release needs working prombench. This is a tmp solution until we have an official image. Mitigates #832 Signed-off-by: bwplotka <bwplotka@gmail.com>
…ch runs (#833) This custom image is locally build from prometheus/golang-builder#296 that we agree to pause until Prometheus release. However, Prometheus release needs working prombench. This is a tmp solution until we have an official image. Mitigates #832 Signed-off-by: bwplotka <bwplotka@gmail.com>
Should be mitigated by #833 |
Fixed on master. |
…ch runs (prometheus#833) This custom image is locally build from prometheus/golang-builder#296 that we agree to pause until Prometheus release. However, Prometheus release needs working prombench. This is a tmp solution until we have an official image. Mitigates prometheus#832 Signed-off-by: bwplotka <bwplotka@gmail.com>
Every prombench start or restart will fail with Prometheus stuck in the init container building. prombench cancel will fail due to #831
The only way to unstuck is logging to GKE cluster and manual force delete of prom pod and nodepools.
See the discussion https://cloud-native.slack.com/archives/C01AUBA4PFE/p1738749878969879
Incident investigation: https://cloud-native.slack.com/archives/C07TT6DTQ02/p1738749348012559
The text was updated successfully, but these errors were encountered: