Serverless Error ---- No .serverless/*.zip file found in the package path you provided #4720

ryub3n · 2018-02-05T11:31:18Z

This is a (Bug Report / Feature Proposal)

Description

For bug reports:

What went wrong?
Serverless deploy on AWS CodeBuild using an artifact from s3 caused a Serverless Error No .serverless/*.zip found
What did you expect should have happened?
The CF stack should've been created.
What was the config you used?
My config is big and it deployed the package correctly when I ran serverless deploy from my laptop using AWS profile.
What stacktrace or error message from your provider did you see?
log.txt
I'm calling serverless deploy in the build phase and it copies my package contents to the .serverless folder and then says it can't find it. I've even listed the contents of the folder and can see it.

My artifact comes from s3 and it's a zip file with the below contents:

employee-service-sls-dev
employee-service-sls-stg
buildspec.yml
package.json
serverless.config.dev.yml
serverless.config.stg.yml
serverless.yml
sls

I even tried invoking it from post_build with no luck.

Additional Data

Serverless Framework Version you're using: 1.26.0
Operating System: Ubuntu container with nodejs6.3.1 but the project uses nodejs6.10
Stack Trace:
Provider Error messages:

ryub3n · 2018-02-06T09:41:28Z

Seems to be an issue with "package individually: true" which I set only at service level. When I removed it the deployment works fine using CodeBuild but my functions are not packed individually which I need.

kkesley · 2018-04-17T23:30:26Z

Hi @ryub3n ! I recently stuck with the same problem as you! As a work around, I can use package:individually in the service level and use include/exclude in the function level.

AhiVT · 2018-11-02T02:17:24Z

Just had this happen to me using the latest version of serveless while using the serverless lambda@edge plugin. Setting package:individually at the service level fixed my issue! Thanks @kkesley

dennisjade · 2018-11-12T11:30:00Z

After I upgrade to the latest(1.32) I got this same issue and removing the individually: true somewhat fixes the issue. But then I have to specify that in every function

nkhine · 2019-03-16T10:00:38Z

serverless@1.39.0 also breaks this, here is part of my serverless.yml

service: apis

plugins:
  - serverless-parameters
  - serverless-pseudo-parameters
  - serverless-plugin-tracing
  - serverless-iam-roles-per-function
provider:
  name: aws
  runtime: go1.x
  iamRoleStatements:
    - Effect: Allow
      Action:
        - s3:getObject
        - s3:putObject
        - s3:GetObjectVersion
        - s3:ListBucketVersions
        - s3:putBucketPolicy
        - states:startExecution
      Resource: "*"
    - Effect: "Allow" # xray permissions (required)
      Action:
        - "xray:PutTraceSegments"
        - "xray:PutTelemetryRecords"
      Resource:
        - "*"
  stage: ${opt:stage}
  region: ${file(./config.yml):${opt:stage}.REGION}
  tracing: true # enable tracing

package:
  individually: true
  exclude:
    - ./**

functions:
  status:
    handler: bin/status
    description: Status/healthcheck function for API
    memorySize: 128
    package:
      individually: true
      include:
        - ./bin/status
    events:
      - http:
          path: status
          method: get
    timeout: 30

on serverless@1.39.0 i get:

  Serverless Error ---------------------------------------
 
  No status.zip file found in the package path you provided.
 
  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Issues:        forum.serverless.com
 
  Your Environment Information -----------------------------
     OS:                     linux
     Node Version:           8.11.2
     Serverless Version:     1.39.0
 
Makefile:23: recipe for target 'deploy' failed
make: *** [deploy] Error 1

downgrading to serverless@1.38.0 works

cs17 · 2019-03-17T01:57:09Z

serverless@1.39.0 also breaks this, here is part of my serverless.yml

service: apis

plugins:
  - serverless-parameters
  - serverless-pseudo-parameters
  - serverless-plugin-tracing
  - serverless-iam-roles-per-function
provider:
  name: aws
  runtime: go1.x
  iamRoleStatements:
    - Effect: Allow
      Action:
        - s3:getObject
        - s3:putObject
        - s3:GetObjectVersion
        - s3:ListBucketVersions
        - s3:putBucketPolicy
        - states:startExecution
      Resource: "*"
    - Effect: "Allow" # xray permissions (required)
      Action:
        - "xray:PutTraceSegments"
        - "xray:PutTelemetryRecords"
      Resource:
        - "*"
  stage: ${opt:stage}
  region: ${file(./config.yml):${opt:stage}.REGION}
  tracing: true # enable tracing

package:
  individually: true
  exclude:
    - ./**

functions:
  status:
    handler: bin/status
    description: Status/healthcheck function for API
    memorySize: 128
    package:
      individually: true
      include:
        - ./bin/status
    events:
      - http:
          path: status
          method: get
    timeout: 30

on serverless@1.39.0 i get:

  Serverless Error ---------------------------------------
 
  No status.zip file found in the package path you provided.
 
  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Issues:        forum.serverless.com
 
  Your Environment Information -----------------------------
     OS:                     linux
     Node Version:           8.11.2
     Serverless Version:     1.39.0
 
Makefile:23: recipe for target 'deploy' failed
make: *** [deploy] Error 1

downgrading to serverless@1.38.0 works

Encountered the same problem after v1.39...
Downgrading to v1.38 works for now..

#5931

brainstorm · 2019-03-17T03:20:11Z

I can confirm this bug, works fine with 1.38.x and breaks on 1.39.x (see referenced commit/issue right above) :/

brainstorm · 2019-03-17T03:59:08Z

Related with #5931

joshtrotter · 2019-03-17T22:11:10Z

Same here - encountering this on 1.39.0, works fine on 1.38.0

aidinkhosrowshahi · 2019-03-17T22:56:18Z

I have same issue too, it was working before but started failing

Serverless: [AWS s3 200 0.058s 0 retries] getBucketLocation({ Bucket: '*******-artifacts-us-east-1' })
Serverless Error ---------------------------------------
No *****.zip file found in the package path you provided.

Serverless Version: 1.39.0

shierro · 2019-03-18T15:05:30Z

same issue with previous 2 comments. it's weird since when I check the .serverless.zip file, it contains the missing zip file mentioned by the error stack trace

calexandrepcjr · 2019-04-01T00:14:19Z

Only happens on >1.39.0

nikita-sheremet-clearscale · 2019-10-05T11:10:03Z

Any news? Any workariunds? I have downgraded to 1.38.0 and got same issue :(

aniljaiswal · 2019-10-15T04:52:45Z

It's happening in the version 1.54.0 as well. I am using CodeBuild to package and deploy the functions individually on a service level rather than function level. I can do ls -l in the CodeBuild logs to see the contents but the deployment fails with the error that No function.zip is found in the path package you provided.

Any help is appreciated.

warapitiya · 2019-11-07T07:38:26Z

Any workarounds?

MichaelGoberling · 2020-03-30T01:23:28Z

This is STILL happening in 1.67.0. I am using Azure Pipelines to try to deploy the functions individually on a service level. I can see the zip files in the .serverless directory in the logs, but the deployment fails with No function.zip is found in the path package you provided.

This is a total deal breaker if you're trying to implement a workflow to pull down the latest staging artifacts and deploy them to production. I can't believe this has zero visibility or responses.

sschulze · 2020-04-30T10:42:22Z

Looks like the absolute path to the packaged artifacts is written in the serverless-state.json. Due to this the package isn't portable anymore.
I think the fix should be to write the artifact paths relative to the package-root into the serverless-state.json.
In the case that the user provided an explicit artifact path in serverless.yml I guess it should be copied into the package directory. This way the artifact stays portable and archivable.

As a workaround I'll try to rewrite the serverless-state.json during deployment. But it's rather ugly.... :-(

jack-morrissey-calabrio · 2020-06-01T23:06:36Z

Having the exact same problems as @MichaelGoberling and would prefer not to go down the route @sschulze. Any updates now?

medikoo · 2020-06-02T07:32:57Z

@MichaelGoberling @jack-morrissey-calabrio please report at https://github.com/serverless/serverless-azure-functions

aychtang · 2020-08-27T08:05:42Z

@medikoo This happens also on my jenkins environment targeting lambda and the original user was using codebuild, I'm not sure if such issue should be pushed to azure specific issues.

aychtang · 2020-08-27T08:10:20Z

In other news I moved my service level package properties into the function level and now it works. Not sure what is happening there...

Before (throws missing zip error):

package:
  individually: true
  exclude: - "*/**"

fn:
  package:
    include: []
..

After (now working):

fn:
  package:
    individually: true
    exclude: - "*/**"
    include: []
..

medikoo · 2020-08-27T10:58:50Z

@aychtang It's possible that #8130 fixes your case

VincentHuysmans1 · 2021-02-23T21:53:37Z

Are there any updates on this ?

Currently facing the same error when deploying individual functions using CodeBuild. Tried above suggestions with no success. Setting package: individually: true on:

service level
function level
service & function level

Your Environment Information -----------------------------
Operating System:          linux
Node Version:              12.16.1
Framework Version:         2.25.2
Plugin Version:            4.4.3
SDK Version:               2.3.2
Components Version:        3.7.0

medikoo · 2021-02-24T13:29:46Z

I'm going to close it, as (1) it's a very old issue, reported to very outdated version of a Framework, and many issues have been fixed since then (2) Report is vague, doesn't provide any details on configuration used, from following comments it appears that many plugins are involved, and they can influence the error (in such case bug report should go to problematic plugin repository)

However if you have similar issue, and feel it's a bug in a framework, please open a new bug report respecting all it's remarks. Having all requested information we should be able to coin issue promptly.

jplandry908 · 2021-05-02T15:40:51Z

For anyone else experiencing this issue, I finally identified the root cause and a simple workaround.

In summary, the "artifact" incorrectly has "$CODEBUILD_SRC_DIR" in the value. Also, the srcxxxxxxxxxx number changes between deploy and build, so you can't just do a find/replace for the exact string in DEPLOY since the value is the $CODEBUILD_SRC_DIR that was in BUILD.

For each function in the serverless-state.json, you will see an artifact property that looks similar to:
"artifact": "/codebuild/output/src887072543/src/.serverless/function.zip"
while it should actually look like this:
"artifact": ".serverless/function.zip"

To work around this issue, I simply added the following two lines in my BUILD commands, immediately above the 'serverless deploy ...' statement.

- sed -i 's/\/codebuild\/output//g' artifacts/${!stage}/serverless-state.json
- sed -i 's/\/src.*\//.serverless\//g' artifacts/${!stage}/serverless-state.json

Note: I am using the '${!stage}' value in my code, but this may be different in your implementation - probably $ENV.

This will transform the "/codebuild/output/src887072543/src/.serverless/function.zip" statements to ".serverless/function.zip", allowing the deploy process to find the file without error.

This took me a while to figure out, so I hope it helps others that may be experiencing the same issue.

vicary · 2022-07-18T17:22:26Z

Thanks @jplandry908, it worked like a charm!

dschep added the bug label Nov 12, 2018

dschep added the cat/packaging label Jan 31, 2019

brainstorm mentioned this issue Mar 17, 2019

Stick with serverless 1.38.x for now... softprops/serverless-aws-rust-http#4

Merged

thundergolfer mentioned this issue Apr 1, 2019

Build tweaks thundergolfer/library-management-slack-bot#5

Merged

emibelli mentioned this issue May 10, 2019

Packaging functions individually causes "no serviceName.zip file found in the package path you provided" #6120

Closed

medikoo closed this as completed Feb 24, 2021

VincentHuysmans1 mentioned this issue Feb 25, 2021

No xxx.zip provided when trying to deploy package using CodePipeline/CodeBuild #9015

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Serverless Error ---- No .serverless/*.zip file found in the package path you provided #4720

Serverless Error ---- No .serverless/*.zip file found in the package path you provided #4720

ryub3n commented Feb 5, 2018 •

edited

ryub3n commented Feb 6, 2018

kkesley commented Apr 17, 2018

AhiVT commented Nov 2, 2018

dennisjade commented Nov 12, 2018

nkhine commented Mar 16, 2019

cs17 commented Mar 17, 2019

brainstorm commented Mar 17, 2019

brainstorm commented Mar 17, 2019

joshtrotter commented Mar 17, 2019

aidinkhosrowshahi commented Mar 17, 2019

shierro commented Mar 18, 2019

calexandrepcjr commented Apr 1, 2019

nikita-sheremet-clearscale commented Oct 5, 2019

aniljaiswal commented Oct 15, 2019 •

edited

warapitiya commented Nov 7, 2019

MichaelGoberling commented Mar 30, 2020

sschulze commented Apr 30, 2020

jack-morrissey-calabrio commented Jun 1, 2020

medikoo commented Jun 2, 2020

aychtang commented Aug 27, 2020 •

edited

aychtang commented Aug 27, 2020

medikoo commented Aug 27, 2020

VincentHuysmans1 commented Feb 23, 2021 •

edited

medikoo commented Feb 24, 2021

jplandry908 commented May 2, 2021 •

edited

vicary commented Jul 18, 2022

Serverless Error ---- No .serverless/*.zip file found in the package path you provided #4720

Serverless Error ---- No .serverless/*.zip file found in the package path you provided #4720

Comments

ryub3n commented Feb 5, 2018 • edited

This is a (Bug Report / Feature Proposal)

Description

Additional Data

ryub3n commented Feb 6, 2018

kkesley commented Apr 17, 2018

AhiVT commented Nov 2, 2018

dennisjade commented Nov 12, 2018

nkhine commented Mar 16, 2019

cs17 commented Mar 17, 2019

brainstorm commented Mar 17, 2019

brainstorm commented Mar 17, 2019

joshtrotter commented Mar 17, 2019

aidinkhosrowshahi commented Mar 17, 2019

shierro commented Mar 18, 2019

calexandrepcjr commented Apr 1, 2019

nikita-sheremet-clearscale commented Oct 5, 2019

aniljaiswal commented Oct 15, 2019 • edited

warapitiya commented Nov 7, 2019

MichaelGoberling commented Mar 30, 2020

sschulze commented Apr 30, 2020

jack-morrissey-calabrio commented Jun 1, 2020

medikoo commented Jun 2, 2020

aychtang commented Aug 27, 2020 • edited

aychtang commented Aug 27, 2020

medikoo commented Aug 27, 2020

VincentHuysmans1 commented Feb 23, 2021 • edited

medikoo commented Feb 24, 2021

jplandry908 commented May 2, 2021 • edited

vicary commented Jul 18, 2022

ryub3n commented Feb 5, 2018 •

edited

aniljaiswal commented Oct 15, 2019 •

edited

aychtang commented Aug 27, 2020 •

edited

VincentHuysmans1 commented Feb 23, 2021 •

edited

jplandry908 commented May 2, 2021 •

edited