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

The WinRM setup script used for the ansible client in the testing vagrantfile no longer exists. #150

Open
6 tasks done
corbob opened this issue Jun 3, 2024 · 1 comment
Labels
0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue Bug Issues where something has happened which was not expected or intended Tests Issues related to the tests (NUnit, xUnit, Pester, Etc)

Comments

@corbob
Copy link
Member

corbob commented Jun 3, 2024

Checklist

  • I confirm there are no unresolved issues reported on the Chocolatey Status page.
  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my problem.
  • I have verified this is not an issue for a specific package.
  • I have verified this issue is not security related.
  • I confirm I am using official, and not unofficial, or modified, Chocolatey products.

What You Are Seeing?

I'm trying to stand up the Ansible testing vagrant found here: https://github.com/chocolatey/chocolatey-ansible/blob/master/testing-chocolatey/Vagrantfile. It is referencing a file on ansible/ansible that no longer exists in that location, and so fails to set WinRM as expected.

What is Expected?

WinRM is configured on the client as expected.

How Did You Get This To Happen?

  1. Run vagrant up in the testing-chocolatey directory.
  2. Note the error when it comes to the Windows client setup (my system locked up between when I observed it and getting to open this issue. I will attempt to circle back and provide the actual error).

System Details

  • Operating System: 10
  • Windows PowerShell version: 5.1
  • Chocolatey CLI Version: N/A
  • Chocolatey Licensed Extension version: N/A
  • Chocolatey License type: N/A
  • Terminal/Emulator: Windows Terminal

Installed Packages

N/A

Output Log

my system locked up between when I observed it and getting to open this issue. I will attempt to circle back and provide the actual error

Additional Context

No response

@corbob corbob added the Bug Issues where something has happened which was not expected or intended label Jun 3, 2024
@corbob
Copy link
Member Author

corbob commented Jun 3, 2024

I have found the PR that removed this from the repository, and where it has moved: ansible/ansible#81011 (comment) The linked comment gives some suggestions for referencing this file.

@vexx32 vexx32 added the Tests Issues related to the tests (NUnit, xUnit, Pester, Etc) label Jun 13, 2024
@vexx32 vexx32 added the 0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue label Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue Bug Issues where something has happened which was not expected or intended Tests Issues related to the tests (NUnit, xUnit, Pester, Etc)
Projects
None yet
Development

No branches or pull requests

2 participants