Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cdk depoy fail: ENOENT: no such file or directory, open #26556

Closed
ltcao opened this issue Jul 28, 2023 · 3 comments
Closed

cdk depoy fail: ENOENT: no such file or directory, open #26556

ltcao opened this issue Jul 28, 2023 · 3 comments
Labels
@aws-cdk/aws-eks Related to Amazon Elastic Kubernetes Service bug This issue is a bug. p2

Comments

@ltcao
Copy link

ltcao commented Jul 28, 2023

Describe the bug

encountering the following error while attempting to deploy EKS cluster using python as the language:

`
XXX-test-cluster: fail: ENOENT: no such file or directory, open 'C:\Users\XXX\AppData\Local\Temp\8\jsii-kernel-klD6CO\node_modules@aws-cdk\asset-node-proxy-agent-v5\lib\layer.zip'

XXX-test-cluster: fail: ENOENT: no such file or directory, open 'C:\Users\XXX\AppData\Local\Temp\8\jsii-kernel-klD6CO\node_modules@aws-cdk\asset-kubectl-v20\lib\layer.zip'

XXX-test-cluster: fail: ENOENT: no such file or directory, open 'C:\Users\XXX\AppData\Local\Temp\8\jsii-kernel-klD6CO\node_modules@aws-cdk\asset-awscli-v1\lib\layer.zip'
`

image

upon examining the path, the files are missing.

Expected Behavior

deployment to succeed?

Current Behavior

deployment encountering unexpected error.

Reproduction Steps

executing on code:

cdk deploy

Possible Solution

No response

Additional Information/Context

package.json:

{ "dependencies": { "@aws-cdk/asset-awscli-v1": "^2.2.200", "@aws-cdk/asset-kubectl-v20": "^2.1.2", "@aws-cdk/asset-node-proxy-agent-v5": "^2.0.166", "aws-cdk": "^2.88.0", "typescript": "^5.1.6" }, "bundleDependencies": [ "@aws-cdk/asset-awscli-v1", "@aws-cdk/asset-kubectl-v20", "@aws-cdk/asset-node-proxy-agent-v5" ] }

NPM modules are saved in project scope (and not global scope).

CDK CLI Version

2.88.0 (build 5d497f9)

Framework Version

2.88.0

Node.js Version

v18.15.0

OS

windows 10

Language

Python

Language Version

3.9.13 (tags/v3.9.13:6de2ca5, May 17 2022, 16:36:42)

Other information

image

@ltcao ltcao added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Jul 28, 2023
@github-actions github-actions bot added the @aws-cdk/aws-eks Related to Amazon Elastic Kubernetes Service label Jul 28, 2023
@pahud
Copy link
Contributor

pahud commented Jul 31, 2023

Can you share your full CDK code?

@pahud pahud added response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. p2 and removed needs-triage This issue or PR still needs to be triaged. labels Jul 31, 2023
@github-actions github-actions bot removed the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Aug 1, 2023
@ltcao
Copy link
Author

ltcao commented Aug 1, 2023

we've discovered that using the --no-staging option during the deployment call is causing this behavior. removing it has allowed us to progress.

@ltcao ltcao closed this as completed Aug 1, 2023
@github-actions
Copy link

github-actions bot commented Aug 1, 2023

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-eks Related to Amazon Elastic Kubernetes Service bug This issue is a bug. p2
Projects
None yet
Development

No branches or pull requests

2 participants