Ensure that ansible 2.7.10 is used rather than 2.8 (latest)

[ccravens]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
It seems that kubespray does not yet support Ansible 2.8 which was recently released. But because the requirements file had anything above 2.7, it seems that it's pulling in 2.8.

Which issue(s) this PR fixes:

Fixes #
NONE
Special notes for your reviewer:
NONE
Does this PR introduce a user-facing change?:
NONE

[k8s-ci-robot]

Welcome @ccravens!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[DanyC97]

@ccravens curious, is any issue related to ansible 2.8 not being supported ?

[woopstar]

I'd rather stick to a specific version (2.7.10) so it works similarly for people.

[MarkusTeufelberger]

Isn't this anyways just mostly used in CI? I hope people are not installing Ansible for the first time when starting to use Kubespray...

[woopstar]

It is. But I'd rather stick to a specific version in a release, so we make sure it "works" in backward. If we hard pin it to 2.7.10 we are sure people actually USE that version (if they at least do pip install before they do cluster stuff)

[MarkusTeufelberger]

https://github.com/kubernetes-sigs/kubespray#requirements lists "Ansible version ... (or newer) [...]" - this then should also probably be changed to something like "Ansible version 2.7.10, all older and newer versions are supported on a best effort basis but not guaranteed to work"?

[woopstar]

Good idea. Let's update that! @ccravens can you do so ?

[ccravens]

sorry, didn't see this mention, I got the 2.7.10 enforcement pushed up now for review

[woopstar]

Please rebase from master to make the CI work.

[ccravens]

@MarkusTeufelberger for our case we are attempting to install k8s using vanilla AWS EC2 AMI that do not have ansible installed, so the ansible dependency is being installed through the requirements.txt file

[ccravens]

@woopstar I just noticed when rebasing master that it seems they are enforcing ansible to 2.7.8 now in master... Should we leave as 2.7.8? Or updated to 2.7.10?

[woopstar]

Update to 2.7.8 so it follows master branch or update to 2.7.10 and also do another PR to update to 2.7.10 in master ;)

[woopstar]

ping @ccravens

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ccravens
To complete the pull request process, please assign chadswen
You can assign the PR to them by writing /assign @chadswen in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@ccravens: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[holmsten]

This was fixed in #4783
/close

[k8s-ci-robot]

@holmsten: Closed this PR.

In response to this:

This was fixed in #4783
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.