-
Notifications
You must be signed in to change notification settings - Fork 31
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 7 permission denied #60
Comments
What happens when you try to create a file by hand in |
Yea I tried that. It created just fine. On Wed, May 21, 2014 at 11:29 AM, Adrien Thebo notifications@github.comwrote:
Christian |
Has pe_build ever worked? Is there anything nonstandard about how your home directory is set up? |
Works great for me on Linux. Never got it working on Windows. Nothing as On Thu, May 22, 2014 at 12:49 PM, Adrien Thebo notifications@github.comwrote:
Christian |
Hi. Same issue here on multiple Windows hosts. Works on my Linux and OSX machines. Customer needs to use their Windows machines though. Please let me know what I can do to assist in diagnosing? |
Can we get some Debugging information please? Vagrant version along with installed plugins followed by a debug output (preferably in a gist we can refer to for the full one with just the area surrounding the issue pasted here). For details on setting log level of vagrant, see http://docs.vagrantup.com/v2/other/debugging.html |
Hey there Rob. Thanks! Info below:
relevant piece:
Full gist located here: It appears to me AppData path is getting mangled along the way. Not sure where it's getting "AD1C02~1" value from. |
UPDATE: I now know where the string came from... Seems valid. Maybe it could be written to $TEMP instead? C:\Users>dir /x Directory of C:\Users 06/10/2014 03:40 PM .06/10/2014 03:40 PM .. 06/10/2014 03:20 PM AD6147 06/17/2014 04:08 PM AD1C021.PAU ad.paultalbot 12/17/2013 04:12 PM Administrator 12/17/2013 03:24 PM ADMINI 02/05/2014 02:34 PM FS_WIN1 FS_WIN7_JOIN 06/10/2014 03:25 PM jasinger 06/23/2014 04:09 PM PAULTA~1 paultalbot 12/17/2013 03:52 PM Public 02/05/2014 02:33 PM rrudat 0 File(s) 0 bytes 11 Dir(s) 240,036,208,640 bytes free C:\Users> |
I hate to pester you guys... But I'm dead in the water. Any ideas come out of what I'd submitted? |
This issue looks like it's due to Windows locking open files. After the file is downloaded it is handed to Are you able to test running vagrant-pe_build from source to test a potential fix? In the mean time, you can work around this issue by downloading them yourself and placing them into |
Hello, thanks for the workaround. It got me past that step. Can certainly try to run from source too if that's useful on your end. Encountered an error on the next step. Will use another "issue" to describe. In the meantime, if you don't mind instructing me on running from source I'll get on it right away. |
Still an issue on Windows. How about using |
I haven't hit this personally, since I don't use Windows as my primary environment, but I've seen the issue happen at least once. Optimistically marking this to be fixed in the next release since it sounds like we just need to adjust how archives are created and moved. |
has this been addressed? and if so how can I get that code? I don't want to have to add work around steps for all my users. thanks in advance, D |
There haven't been any fixes submitted for this yet. I'm planning to do a "Windows bug bash" release focused on Windows fixes once I get done shoring up support for PE 2015.x agent installation. If anyone wants to submit a PR to fix this issue, I'd be happy to review it! |
Built a VM turducken yesterday (Vagrant inside of Windows inside of Vagrant inside of OS X) during #puppethack and tested a fix for this. It will go out in a patch release this week. |
Version 0.13.6 has been shipped and includes this fix. |
Get the following error during provisioning pe_bootstrap for role master. Anyone have any thoughts?
The text was updated successfully, but these errors were encountered: