Update requirements.txt

[jfc-evs]

Correction for:
Collecting cryptography (from ansible==2.9.16->-r kubespray/requirements.txt (line 1))
Downloading https://files.pythonhosted.org/packages/06/ed/cb79cc94ec58d9d92557238fc6c629cd6e07d72334d2de556aecc2211370/cryptography-3.4.1.tar.gz (544kB)
Complete output from command python setup.py egg_info:

        =============================DEBUG ASSISTANCE==========================
        If you are seeing an error here please try the following to
        successfully install cryptography:

        Upgrade to the latest pip and try again. This will fix errors for most
        users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip
        =============================DEBUG ASSISTANCE==========================

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/tmp/pip-build-ha3jzl4a/cryptography/setup.py", line 14, in <module>
    from setuptools_rust import RustExtension
ModuleNotFoundError: No module named 'setuptools_rust'

----------------------------------------

Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-ha3jzl4a/cryptography/

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:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jfc-evs
To complete the pull request process, please assign floryut after the PR has been reviewed.
You can assign the PR to them by writing /assign @floryut 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]

Welcome @jfc-evs!

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]

Hi @jfc-evs. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[floryut]

@jfc-evs Thank you for the PR, could you please sign CLA ?
/ok-to-test

[LuckySB]

what is your OS and python version ?

[jfc-evs]

[root@70b4dd7cf5d2 ~]# rpm -q centos-release
centos-release-7-5.1804.el7.centos.2.x86_64
[root@70b4dd7cf5d2 ~]# python --version
Python 2.7.5

[LuckySB]

it is very very strange
on all my centos7 pip install -r requirements.txt works without errors

centos-release-7-7.1908.0.el7.centos.x86_64
python 2.7.5

pip freeze
ansible==2.9.16
cryptography==1.7.2

[k8s-ci-robot]

@jfc-evs: 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.

[aplhk]

I had the same issue in a recent installation of kubespray 2.14, which upgrading my pip from 9.0.3 to 21.0.1 fixed it.

I guess the reason is the compatibility issues between cryptography library and the pip as mentioned in: Azure/azure-cli#16858

$ rpm -q centos-release
centos-release-7-9.2009.1.el7.centos.x86_64
$ python --version
Python 2.7.5

---

ansible==2.9.6
cryptography==3.4.6

Logs:

Collecting ansible==2.9.6 (from -r kubespray/requirements.txt (line 1))
  Using cached https://files.pythonhosted.org/packages/ae/b7/c717363f767f7af33d90af9458d5f1e0960db9c2393a6c221c2ce97ad1aa/ansible-2.9.6.tar.gz
Requirement already satisfied: jinja2==2.11.1 in /home/user/.local/lib/python3.6/site-packages (from -r kubespray/requirements.txt (line 2))
Collecting netaddr==0.7.19 (from -r kubespray/requirements.txt (line 3))
  Using cached https://files.pythonhosted.org/packages/ba/97/ce14451a9fd7bdb5a397abf99b24a1a6bb7a1a440b019bebd2e9a0dbec74/netaddr-0.7.19-py2.py3-none-any.whl
Collecting pbr==5.4.4 (from -r kubespray/requirements.txt (line 4))
  Using cached https://files.pythonhosted.org/packages/7a/db/a968fd7beb9fe06901c1841cb25c9ccb666ca1b9a19b114d1bbedf1126fc/pbr-5.4.4-py2.py3-none-any.whl
Collecting jmespath==0.9.5 (from -r kubespray/requirements.txt (line 5))
  Using cached https://files.pythonhosted.org/packages/a3/43/1e939e1fcd87b827fe192d0c9fc25b48c5b3368902bfb913de7754b0dc03/jmespath-0.9.5-py2.py3-none-any.whl
Collecting ruamel.yaml==0.16.10 (from -r kubespray/requirements.txt (line 6))
  Using cached https://files.pythonhosted.org/packages/a6/92/59af3e38227b9cc14520bf1e59516d99ceca53e3b8448094248171e9432b/ruamel.yaml-0.16.10-py2.py3-none-any.whl
Requirement already satisfied: PyYAML in /usr/lib64/python3.6/site-packages (from ansible==2.9.6->-r kubespray/requirements.txt (line 1))
Collecting cryptography (from ansible==2.9.6->-r kubespray/requirements.txt (line 1))
  Using cached https://files.pythonhosted.org/packages/fa/2d/2154d8cb773064570f48ec0b60258a4522490fcb115a6c7c9423482ca993/cryptography-3.4.6.tar.gz
    Complete output from command python setup.py egg_info:

            =============================DEBUG ASSISTANCE==========================
            If you are seeing an error here please try the following to
            successfully install cryptography:

            Upgrade to the latest pip and try again. This will fix errors for most
            users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip
            =============================DEBUG ASSISTANCE==========================

    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-7xjex8m9/cryptography/setup.py", line 14, in <module>
        from setuptools_rust import RustExtension
    ModuleNotFoundError: No module named 'setuptools_rust'

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-7xjex8m9/cryptography/

[floryut]

pip "issue" then ? moving to close, WDYT ?

[floryut]

Please reopen if needed.

[oomichi]

I faced the same issue on CentOS 7 virtual machine which is deployed on MS Azure cloud.

[oomichi]

@jfc-evs If it is hard to sign CLA on your side, can I open another PR on my side?

[jfc-evs]

@oomichi Yes CLA is hard to sign for me, feel free to open another PR in your side (I also use Centos 7)

[oomichi]

@oomichi Yes CLA is hard to sign for me, feel free to open another PR in your side (I also use Centos 7)

Thanks, I will do that based on your change.

[oomichi]

I submitted #7403 after confirming I can reproduce it again.