Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Deployment fails with "Stack [foo] does not exist" if existing bucket used

Abierto
  • ¿Algo no está bien?
#13,165 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
aws, javascript
Área
cloud, devops

Línea de trabajo

Empieza por rastrear la ruta de despliegue que gestiona deploymentBucket y las llamadas de CloudFormation describeStacks, createStack y updateStack. Reproduce el fallo con un bucket existente y un stack ausente; se considera completado cuando el primer despliegue invoca createStack y tiene éxito en lugar de llamar a updateStack sobre el stack ausente.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
Issue description

I am hitting this problem while trying to deploy a lambda for the first time. The CF stack does not exist, CF config passes validation, lambda package gets uploaded to s3 but sls fails on my foo stack:

✖ ServerlessError2: Stack [foo] does not exist
    at file:///Users/michal.szelag/.serverless/releases/4.25.0/package/dist/sf-core.js:1053:36
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async persistentRequest (file:///Users/michal.szelag/.serverless/releases/4.25.0/package/dist/sf-core.js:1052:1984)

I think the issue is that I am using an existing bucket in my configuration like this:

deploymentBucket:
  name: "devx-infra-serverless-deployments"
  maxPreviousDeploymentArtifacts: 5
  blockPublicAccess: true
  • The bucket exists and the framework does upload the artifacts before failing so permissions aren't the problem.
  • If I remove the bucket configuration, the deployment works.
  • If I run deploy with debug, I can see that it checks for existence of the stack, it fails, as it should:
s:sls:aws:request: request: #2 CloudFormation.describeStacks [ { StackName: 'foo' } ]
s:sls:aws:request: request error: #2 - CloudFormation.describeStacks ValidationError: Stack with id foo does not exist
s: ValidationError: Stack with id foo does not exist
    at constructor.extractError (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/protocol/query.js:50:29)
    at constructor.callListeners (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at constructor.emit (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at constructor.emitEvent (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/request.js:686:14)
    at constructor.transition (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.AcceptorStateMachine.runTo (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at <anonymous> (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/state_machine.js:26:10)
    at constructor.<anonymous> (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/request.js:38:9)
    at constructor.<anonymous> (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/request.js:688:12)
    at constructor.callListeners (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
  • But it never calls createStack and instead calls updateStack on something that doesn't exist.
s:sls:aws:request: request error: #10 - CloudFormation.updateStack ValidationError: Stack [foo] does not exist
s: ValidationError: Stack [foo] does not exist
    at constructor.extractError (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/protocol/query.js:50:29)
    at constructor.callListeners (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at constructor.emit (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at constructor.emitEvent (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/request.js:686:14)
    at constructor.transition (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.AcceptorStateMachine.runTo (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at <anonymous> (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/state_machine.js:26:10)
    at constructor.<anonymous> (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/request.js:38:9)
    at constructor.<anonymous> (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/request.js:688:12)
    at constructor.callListeners (/Users/michal.szelag/.serverless/releases/node_modules/aws-sdk/lib/sequential_executor.js:116:18)

So, there is a bug here where createStack is contingent upon sls managing the bucket..

Lenguaje dominante
JavaScript
Estrellas
46.9k
Forks
5.7k
Merge medio
23 h 13 min
PR fusionados (30 d)
72

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de serverless/serverless

Todos los issues de serverless/serverless

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.