AWS - Incorrect path seperate used when defining package path. #5934

maxplezzel · 2019-03-17T10:06:51Z

This is a Bug Report

Description

Incorrect path separator used when determining where the deployment artefact is located in AWS deployment.

What went wrong?
When setting the package path the wrong path seperate was being used for MacOS, resulting in the incorrect path being used to upload artefacts to S3.
What did you expect should have happened?
Correct path seperate to be used based upon OS.
What was the config you used?
Standard
What stacktrace or error message from your provider did you see?

Serverless: Uploading CloudFormation file to S3...
Serverless: Uploading artifacts...

  Error --------------------------------------------------

  ENOENT: no such file or directory, stat './server/.serverless/.serverless/fishcare-cms-server.zip'

     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Issues:        forum.serverless.com

  Your Environment Information -----------------------------
     OS:                     darwin
     Node Version:           9.3.0
     Serverless Version:     1.39.0

Solution

Change:

File: serverless/lib/plugins/aws/package/lib/saveServiceState.js
Line: 35
To: packageRef.artifact.substr(packageRef.artifact.lastIndexOf(path.sep) + 1)

I would make the change myself but haven't contributed before and don't have time right now to meet contribution requirements.

The text was updated successfully, but these errors were encountered:

julienseverin · 2019-03-17T11:44:12Z

Got the same issue, had to rollback to 1.38.0

ClementKerneur · 2019-03-17T14:38:43Z

Same problem, i rollback to 1.38.0 also !!!

chrisanderss0n · 2019-03-17T17:17:19Z

I will fix, PR coming up.

ghost · 2019-03-18T09:36:59Z

I've been sitting with this issue for two days now, thanks @maxplezzel
Finally got it working🐱‍👤

pmuens · 2019-03-18T10:16:57Z

Just reverted #4188 which seems to be the root cause. Patch release should be out in ~30 minutes...

decebal · 2019-08-16T10:59:15Z

Somehow this one has resurfaced in the latest versions 1.49 and 1.50, I am still on my way to test which one works.
I rolled back to 1.38.0, but a more thorough investigation would be better, I think.

aardrop · 2020-04-17T22:22:04Z

I'm still having this issue with version 1.66. I'm happy to roll back for now but I worry that is not sustainable, does anyone know a solution or work around?

colorninja · 2020-04-27T23:41:16Z

Seems to have found it's way back into 1.66 apparently and 1.68 doesn't work for me too. I am running into the following error (PC configuration included):

Serverless: Packaging service...
 Serverless: Excluding development dependencies...
  
   Error --------------------------------------------------
  
   Error: ENOENT: no such file or directory, open '/builds/.../node_modules/.bin/image-size'
  
      For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.
  
   Get Support --------------------------------------------
      Docs:          docs.serverless.com
      Bugs:          github.com/serverless/serverless/issues
      Issues:        forum.serverless.com
  
   Your Environment Information ---------------------------
      Operating System:          linux
      Node Version:              12.14.1
      Framework Version:         1.68.0
      Plugin Version:            3.6.8
      SDK Version:               2.3.0
      Components Version:        2.30.2

alphonso77 · 2020-04-28T19:49:47Z

I was experiencing this behavior as well. I tried reverting to several versions to no avail. I dug around a little bit and I'm not sure which one of these actions fixed the problem, but here's the steps I took (windows 10, PS):

Run npm list -g --depth 0 (this listed all of the packages I'd installed globally via npm, and several of them had broken dependencies)
uninstall all npm packages (including serverless): npm uninstall -g <package-name>
choco upgrade serverless
run sls deploy again, works

cknuteson-firstlook · 2020-05-05T15:06:45Z

Chiming in to say this is happening with 1.69.0

Serverless: Compiling with Typescript...
Serverless: Using local tsconfig.json
Serverless: Typescript compiled.
Serverless: Packaging service...
Serverless: Excluding development dependencies...
 
  Error --------------------------------------------------
 
  Error: ENOENT: no such file or directory, stat '/Users/<me>/<project>/packages/backend/.build/node_modules/.bin/tsc'
 
     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.
 
  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Issues:        forum.serverless.com
 
  Your Environment Information ---------------------------
     Operating System:          darwin
     Node Version:              12.16.1
     Framework Version:         1.69.0 (standalone)
     Plugin Version:            3.6.8
     SDK Version:               2.3.0
     Components Version:        2.30.2

mithundas79 · 2020-12-03T15:40:52Z

This is an issue when i am trying to use the serverless express template.

C:\Users\LENOVO\Documents\Official\Projects\OCPP-Client\bluedot-cpms-service\ocpp_express>serverless create --template-url https://github.com/serverless/components/tree/master/templates/express
Serverless: Generating boilerplate...
Serverless: Downloading and installing "templates\express"...
(node:22640) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated

  Serverless Error ---------------------------------------

  Error: ENOENT: no such file or directory, stat 'C:\Users\LENOVO\AppData\Local\Temp\components\templates\express'

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Issues:        forum.serverless.com

  Your Environment Information ---------------------------
     Operating System:          win32
     Node Version:              13.9.0
     Framework Version:         1.78.1
     Plugin Version:            3.7.0
     SDK Version:               2.3.1
     Components Version:        2.34.5

mithundas79 · 2020-12-03T15:54:24Z

Ok problem is https://github.com/serverless/components/tree/master/templates/express NOT FOUND :(

bcraft · 2020-12-04T15:46:08Z

picked this exact issue up again today on 2.12, replicated things manually and cannot repeat the error but sls package wont go through.

wmlutz · 2020-12-12T18:58:10Z

@bcraft I just tried to get things going today on 2.15.0 and ran into the same problem.

mithundas79 · 2020-12-12T20:16:48Z

Ok problem is https://github.com/serverless/components/tree/master/templates/express NOT FOUND :(

I hv not taken the template, rather i used the simplier serverless-http method and this is running for me. So not sure my issue is related to anything above.

brognilucas · 2021-04-21T08:29:04Z

Having the same problem here. When I deploy from my local environment works though.

crsepulv · 2023-04-19T16:49:12Z

in my case the problem is

serverless-plugin-typescript
if I remove it, deploys well.

pmuens added bug cat/packaging labels Mar 18, 2019

pmuens mentioned this issue Mar 18, 2019

Revert "Fixed #4188 - Package generating incorrect package artifact path in serverless-state.json" #5936

Merged

pmuens closed this as completed in #5936 Mar 18, 2019

Brianvdb mentioned this issue Feb 1, 2020

Layer not deployed when foldername contains a dots. #7280

Open

serverless deleted a comment from voidp34r Feb 10, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

AWS - Incorrect path seperate used when defining package path. #5934

AWS - Incorrect path seperate used when defining package path. #5934

maxplezzel commented Mar 17, 2019 •

edited

julienseverin commented Mar 17, 2019

ClementKerneur commented Mar 17, 2019

chrisanderss0n commented Mar 17, 2019

ghost commented Mar 18, 2019

pmuens commented Mar 18, 2019

decebal commented Aug 16, 2019 •

edited

aardrop commented Apr 17, 2020

colorninja commented Apr 27, 2020

alphonso77 commented Apr 28, 2020

cknuteson-firstlook commented May 5, 2020 •

edited

mithundas79 commented Dec 3, 2020

mithundas79 commented Dec 3, 2020

bcraft commented Dec 4, 2020

wmlutz commented Dec 12, 2020

mithundas79 commented Dec 12, 2020

brognilucas commented Apr 21, 2021

crsepulv commented Apr 19, 2023

AWS - Incorrect path seperate used when defining package path. #5934

AWS - Incorrect path seperate used when defining package path. #5934

Comments

maxplezzel commented Mar 17, 2019 • edited

This is a Bug Report

Description

Solution

I would make the change myself but haven't contributed before and don't have time right now to meet contribution requirements.

julienseverin commented Mar 17, 2019

ClementKerneur commented Mar 17, 2019

chrisanderss0n commented Mar 17, 2019

ghost commented Mar 18, 2019

pmuens commented Mar 18, 2019

decebal commented Aug 16, 2019 • edited

aardrop commented Apr 17, 2020

colorninja commented Apr 27, 2020

alphonso77 commented Apr 28, 2020

cknuteson-firstlook commented May 5, 2020 • edited

mithundas79 commented Dec 3, 2020

mithundas79 commented Dec 3, 2020

bcraft commented Dec 4, 2020

wmlutz commented Dec 12, 2020

mithundas79 commented Dec 12, 2020

brognilucas commented Apr 21, 2021

crsepulv commented Apr 19, 2023

maxplezzel commented Mar 17, 2019 •

edited

decebal commented Aug 16, 2019 •

edited

cknuteson-firstlook commented May 5, 2020 •

edited