-
Notifications
You must be signed in to change notification settings - Fork 66
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
Fix Windows Support #129
Fix Windows Support #129
Conversation
* Change calls of 'type' to 'more' to handle paths with spaces * Check to make sure that puppet is in the connection path and reboot otherwise. This fixes issues with Windows SSH servers. * Fix the path calls to the versions.txt file
* Also added a missing requirement to the Gemfile * Requires the following PRs to function: * voxpupuli/beaker-vagrant#26 * puppetlabs/beaker-puppet#129
looks like spec testing is failing for this under Ruby 2.4.4:
|
@puppetlabs-jenkins retest this please |
It looks like the jobs for this are failing due to conflicts installing against Ruby 2.3.1:
We're seeing similar failures in other PRs too (voxpupuli/beaker-google#5), so I've submitted an internal PR against our CI system that will move us off 2.3.1 testing & forward onto 2.6.5 instead. Hopefully we'll get that moving & merged early next week, & I'll re-kick testing here once it's deployed. In the meantime, let me know if you have questions or comments about this. |
@puppetlabs-jenkins retest this please |
this appears to have been an infrastructure issue in CI that I believe should be gone by now. @puppetlabs-jenkins retest this please |
* Also added a missing requirement to the Gemfile * Requires the following PRs to function: * voxpupuli/beaker-vagrant#26 * puppetlabs/beaker-puppet#129
The build failures here are much more curious now and seem like they might be relevant to the change, as only the windows cells are failing, all with this same message (beaker-puppet integration build#174):
I'm not familiar with puppet-agent installer failure-modes, windows or not, so I'd like to see if @puppetlabs/night-s-watch has some expertise that will help us know if this is a smaller transient issue (just a timeout we should re-kick, for instance?) or something we should be worried about in this change. |
@kevpl You might need the other windows fixes published and/or pulled in for this to function. |
Or it could be something in the internal network. They all worked together on the Internet. |
@genebean This should now pass with the updated gems for beaker-puppet and beaker. |
@puppetlabs-jenkins retest this please |
This is causing the agent pipeline to get stuck on all the windows platforms.
is not exiting.
If we don't find a resolution, we'll yank the latest beaker-puppet gem. |
Revert "Merge pull request #129 from trevor-vaughan/windows_paths"
We're not going to yank beaker-puppet, but we have released a new version with a revert to this PR. |
@mihaibuzgau do you have a suggestion for how we could improve testing of PR’s on this repository so that things like this issue would be found pre-merge? Sent with GitHawk |
@mihaibuzgau Please test this with different versions of Windows before you revert. As far as I can tell, you've probably re-broken everyone that's not on your hidden network. The reason that I changed it over to The following Beaker test suite was used to evaluate the changes against multiple VM flavors: https://github.com/simp/rubygem-simp-beaker-helpers/tree/master/spec/acceptance/suites/windows I haven't been able to replicate your failure case but I can definitely make the old version fail on anything newer than Windows 2012. If file_contents_on is fixed to be OS agnostic ( |
@genebean the failure was caught in beaker-puppet acceptance CI, as you can see, the windows box was not responding:
|
@gimmyxd What base box is it using? |
I would like to request we move this conversation to https://tickets.puppetlabs.com/browse/BKR-1631 please |
otherwise. This fixes issues with Windows SSH servers.