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

windows_zipfile throws Errno::ENOENT for file with $ in the name #606

Open
cosmincucu opened this issue Jan 31, 2019 · 1 comment
Open

Comments

@cosmincucu
Copy link

Cookbook version

5.2.2

Chef-client version

14.5.33

Platform Details

windows server 2016 standard

Scenario:

using the windows cookbook to unzip an app folder.

Steps to Reproduce:

using the windows cookbook to unzip an app folder. There are quite a lot of folders in the zip, and some of the files have the $ symbol in them.

Expected Result:

i'd expect the unzip to finish successfully.

Actual Result:

As soon as the process gets to the first file with the $ in it, it fails with an error :

    Errno::ENOENT
    -------------
    No such file or directory @ rb_sysopen - [long path for a file that contains $]
@welcomebot
Copy link

Hey There
It looks like this is the first issue you've filed against the chef-cookbooks project. I'm here to offer you a bit of extra help to make sure we can quickly get back to you.
Make sure you've filled out all the fields in our issue template. Make sure you've provided us with the version of chef-client you're running, your operating system and the version of the cookbook. If you're not using the most up to date version of the cookbook then please make sure to update first. Lots of things change between versions even if you're issue isn't listed in the changelog. Finally please give us a detailed description of the issue you're having. The more we know about what you're trying to do, what actually happens, and how you can reproduce the problem, the better.

If you're looking for more immediate troubleshooting help make sure to check out #general on the Chef Community Slack. There's plenty of folks there willing to lend a helping hand. Thanks for the first issue. We hope we can get back to you soon with a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants