Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Application droplet can be started with a different stack than the buildpack used to produce the droplet supports

Aperta
  • Qualcosa non va?
#3,239 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
ruby
Ambito
api, backend

Direzione di ricerca

Traccia il flusso delle build v3, la relazione dell’app con current_droplet e l’azione di riavvio dell’app descritta nei passaggi per riprodurre il problema. Verifica come vengono confrontati lo stack del ciclo di vita dell’app e lo stack del droplet, quindi individua il punto di ingresso rilevante per il test di regressione. Il lavoro è completato quando uno stack non corrispondente viene rifiutato prima dell’avvio dell’app, con copertura per il percorso API.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

unscheduled

Issue

Using the CF APIs it is possible to launch an application droplet with a CF stack which is different than the stack supported by the buildpack used to produce the droplet.

Steps to Reproduce

Prerequisite is a CF offering two different stacks. E.g. cflinuxfs3 and cflinuxfs4. For the steps below we want to switch an application from the cflinuxfs3 to cflinuxfs4 stack.

  1. Get the app latest package guid with: cf curl "/v3/packages?app_guids=<app-guid>&order_by=-created_at&states=READY"
  2. Create a new droplet with the cflinuxfs4 stack and the corresponding buildpack supporting the cflinuxfs4 stack:
  curl curl "/v3/builds" \
      -X POST \
      -H "Content-type: application/json" \
      -d '{
        "package": {
          "guid": "[package-guid]"
         },
         lifecycle: {
           type: "buildpack",
           data: { buildpacks: [<cflinuxfs4-buildpack>], stack: cflinuxfs4}
        }
      }'
  1. Wait until the build is done and get the new droplet guid with: cf curl "/v3/builds/<build-guid>"
  2. Stop the app with: cf curl "/v3/apps/<guid>/actions/stop" -X POST"
  3. Set the app's current droplet:
cf curl "/v3/apps/[guid]/relationships/current_droplet" \
  -X PATCH \
  -H "Content-type: application/json" \
  -d '{ "data": { "guid": "[<droplet_guid>]" } }'
  1. Restart the app: cf curl "/v3/apps/[guid]/actions/restart" -X POST"

Expected result

CF restart request fails because the current stack of the application configured in its lifecycle is cflinuxfs3 but the current droplet is built for the cflinuxfs4 stack.

Current result

The application is restarted with its configured stack which is cflinuxfs3 and e.g. node apps are crashing with strange errors like:

 [APP/PROC/WEB/0] STDERR node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by node)
 [APP/PROC/WEB/0] STDERR node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by node)
 [APP/PROC/WEB/0] STDERR node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by node)
 [APP/PROC/WEB/0] STDERR node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)
 [APP/PROC/WEB/0] STDERR node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by node)
 [APP/PROC/WEB/0] STDERR node: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by node)
 [APP/PROC/WEB/0] STDERR node: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by node)
 [APP/PROC/WEB/0] STDERR node: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by node)

This is happening because the droplet has dependencies to the CF stack and they can't be resolved.

Possible Fix

Possible fix could be to reject such a start/restart request when the droplet stack is different than the app lifecycle stack. Such an error is happening when you try to push an app with a buildpack which doesn't support the current lifecycle stack of the app:

 [STG/0] OUT **ERROR** Stack not supported by buildpack: required stack cflinuxfs3 was not found
 [STG/0] ERR Failed to compile droplet: Failed to run all supply scripts: exit status 11
Lingua principale
Ruby
Stelle
207
Fork
374
Merge medio
3g 6h
PR unite (30g)
44

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cloudfoundry/cloud_controller_ng

Tutte le issue di cloudfoundry/cloud_controller_ng

Issue simili

Altre issue su Ruby

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.