Closed Bug 1183368 Opened 10 years ago Closed 10 years ago

Stackato push failing with "bin/compile: line 17: /staging/staged/buildpack/compile-extensions/bin/check_stack_support: No such file or directory"

Categories

(Tree Management :: Bugherder, defect, P1)

Product:
Tree Management
Component:
Bugherder
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

Bugherder's Stackato config uses the cloudfoundry staticfile buildpack: https://github.com/cloudfoundry/staticfile-buildpack Mozilla's Stackato instance uses an old version of Stackato (v2.x) which has more limited support for buildpacks: https://api.paas.mozilla.org/docs/deploy/buildpack.html#deploy-using-buildpacks There doesn't seem to be a way to specify a revision/branch/tag for BUILDPACK_URL and have it still work, so we've just been tracking staticfile-buildpack master until now. Unfortunately deploying Bugherder with staticfile-buildpack master appears to now be broken: [~/src/bugherder]$ stackato push --no-prompt Pushing application 'bugherder'... Framework: buildpack Runtime: <framework-specific default> Application Url: bugherder.paas.mozilla.org Application Url: bugherder.mozilla.org Creating Application [bugherder] ... OK Adding Environment Variable [BUILDPACK_URL=git://github.com/cloudfoundry-incubator/staticfile-buildpack.git] Adding Environment Variable [FORCE_HTTPS=true] Updating environment: OK Uploading Application [bugherder] ... Checking for bad links: OK Copying to temp space: OK Checking for available resources: OK Packing application: OK Uploading (1K): OK Push Status: OK stackato.stager: Staging application 'bugherder' staging: staging: -----> git clone --depth 1 https://github.com/mozilla/Bugherder.git src staging: Cloning into 'src'... staging: -----> Stackato receiving staging request Failed to stage application: staging plugin exited with non-zero exit code. [~/src/bugherder]$ stackato logs 2015-07-13T23:03:33+0100 stackato.stager: Staging application 'bugherder' 2015-07-13T23:03:35+0100 staging: 2015-07-13T23:03:35+0100 staging: -----> git clone --depth 1 https://github.com/mozilla/Bugherder.git src 2015-07-13T23:03:35+0100 staging: Cloning into 'src'... 2015-07-13T23:03:36+0100 staging: -----> Stackato receiving staging request 2015-07-13T23:03:41+0100 stackato.stager: Completed staging application 'bugherder' 2015-07-13T23:03:41+0100 staging: -----> Static file app detected 2015-07-13T23:03:41+0100 staging: bin/compile: line 17: /staging/staged/buildpack/compile-extensions/bin/check_stack_support: No such file or directory 2015-07-13T23:03:41+0100 staging: 2015-07-13T23:03:41+0100 staging: -----> git clone --depth 1 https://github.com/mozilla/Bugherder.git src 2015-07-13T23:03:41+0100 staging: Cloning into 'src'... 2015-07-13T23:03:41+0100 staging: -----> Stackato receiving staging request 2015-07-13T23:03:41+0100 staging: -----> Static file app detected 2015-07-13T23:03:41+0100 staging: bin/compile: line 17: /staging/staged/buildpack/compile-extensions/bin/check_stack_support: No such file or directory
Since we can't specify a branch/ref, the only way to control what revision gets used, is to use a fork and set a custom branch as the default github branch. By bisecting, I found that the error in comment 0 appears to start when staticfile-buildpack began using git submodules. I tried using the v1.0.0 tag release (which doesn't include any submodules), however then got: [~/src/bugherder]$ stackato push --no-prompt Pushing application 'bugherder'... Framework: buildpack Runtime: <framework-specific default> Application Url: bugherder.paas.mozilla.org Application Url: bugherder.mozilla.org Creating Application [bugherder] ... OK Adding Environment Variable [BUILDPACK_URL=git://github.com/edmorley/staticfile-buildpack.git] Adding Environment Variable [FORCE_HTTPS=true] Updating environment: OK Uploading Application [bugherder] ... Checking for bad links: OK Copying to temp space: OK Checking for available resources: OK Packing application: OK Uploading (1K): OK Push Status: OK stackato.stager: Staging application 'bugherder' staging: staging: -----> git clone --depth 1 https://github.com/mozilla/Bugherder.git src staging: Cloning into 'src'... staging: -----> Stackato receiving staging request Failed to stage application: staging plugin exited with non-zero exit code. [~/src/bugherder]$ stackato logs 2015-07-13T23:13:27+0100 stackato.stager: Staging application 'bugherder' 2015-07-13T23:13:30+0100 staging: 2015-07-13T23:13:30+0100 staging: -----> git clone --depth 1 https://github.com/mozilla/Bugherder.git src 2015-07-13T23:13:30+0100 staging: Cloning into 'src'... 2015-07-13T23:13:32+0100 staging: -----> Stackato receiving staging request 2015-07-13T23:13:36+0100 stackato.stager: Completed staging application 'bugherder' 2015-07-13T23:13:36+0100 staging: -----> Static file app detected 2015-07-13T23:13:36+0100 staging: -----> Root folder src 2015-07-13T23:13:36+0100 staging: -----> Copying project files into public/ 2015-07-13T23:13:36+0100 staging: -----> Setting up nginx 2015-07-13T23:13:36+0100 staging: tar (child): /staging/staged/buildpack/vendor/nginx-1.7.4-precise.tar.gz: Cannot open: No such file or directory 2015-07-13T23:13:36+0100 staging: tar (child): Error is not recoverable: exiting now 2015-07-13T23:13:36+0100 staging: tar: Child returned status 2 2015-07-13T23:13:36+0100 staging: tar: Error is not recoverable: exiting now 2015-07-13T23:13:36+0100 staging: 2015-07-13T23:13:36+0100 staging: -----> git clone --depth 1 https://github.com/mozilla/Bugherder.git src 2015-07-13T23:13:36+0100 staging: Cloning into 'src'... 2015-07-13T23:13:36+0100 staging: -----> Stackato receiving staging request 2015-07-13T23:13:36+0100 staging: -----> Static file app detected 2015-07-13T23:13:36+0100 staging: -----> Root folder src 2015-07-13T23:13:36+0100 staging: -----> Copying project files into public/ 2015-07-13T23:13:36+0100 staging: -----> Setting up nginx 2015-07-13T23:13:36+0100 staging: tar (child): /staging/staged/buildpack/vendor/nginx-1.7.4-precise.tar.gz: Cannot open: No such file or directory 2015-07-13T23:13:36+0100 staging: tar (child): Error is not recoverable: exiting now 2015-07-13T23:13:36+0100 staging: tar: Child returned status 2 2015-07-13T23:13:36+0100 staging: tar: Error is not recoverable: exiting now ...which appears to be a regression from: https://github.com/cloudfoundry/staticfile-buildpack/pull/27 However I can't use revisions older than that, since they don't include the few fixes that were in the PRs I provided for that repo. Therefore I've created a custom branch, based on d8550707d704d4119d725a486d66c5c6651dc1ef, but with these commits cherrypicked: https://github.com/edmorley/staticfile-buildpack/commit/ce1bb0b4d41a32290c8e1743234b73e1f8c22fd0 https://github.com/edmorley/staticfile-buildpack/commit/35634b648c9acda58b4cff958858194aa9999d9b (the latter is the important one) After that, the build step completed fine, however visiting the site on bugherder.paas.mozilla.org just gave a "Server not found". However, it works fine if I target paas.allizom.org instead of paas.mozilla.org?!
I've landed the fix for the Stackato config: https://github.com/mozilla/bugherder/commit/5ae54f02243ab1ee33fb6145a27f6c0809146f8c And filed bug 1183404 for figuring out why it doesn't work on paas.mozilla.org, when it does on paas.allizom.org.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.