Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#3,239 3 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 3 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
42/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Stack de tecnologia
ruby
Domínio
api, backend

Direção de pesquisa

Rastreie o fluxo dos builds v3, o relacionamento do app com current_droplet e a ação de reinicialização do app descrita nas etapas de reprodução. Verifique como a stack do ciclo de vida do app e a stack do droplet são comparadas e, em seguida, identifique o ponto de entrada relevante do teste de regressão. A tarefa estará concluída quando uma stack incompatível for rejeitada antes de o app iniciar, com cobertura para o caminho da API.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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
Linguagem predominante
Ruby
Estrelas
207
Forks
373
Merge médio
2d 18h
PRs com merge (30d)
82

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de cloudfoundry/cloud_controller_ng

Todas as issues de cloudfoundry/cloud_controller_ng

Issues semelhantes

Mais issues de Ruby

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.