No module named '_cffi_backend'

[praveen-pk]

This is autogenerated. Please review and update as needed.

Describe the bug

Command Name
az storage container create

Errors:

No module named '_cffi_backend'
Traceback (most recent call last):
python3.6/site-packages/knack/cli.py, ln 206, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 528, in execute
    self.commands_loader.load_arguments(command)
azure/cli/core/__init__.py, ln 299, in load_arguments
    self.command_table[command].load_arguments()  # this loads the arguments via reflection
cli/core/commands/__init__.py, ln 291, in load_arguments
    super(AzCliCommand, self).load_arguments()
...
storage/v2018_11_09/blob/_encryption.py, ln 13, in <module>
    from cryptography.hazmat.primitives.padding import PKCS7
cryptography/hazmat/primitives/padding.py, ln 13, in <module>
    from cryptography.hazmat.bindings._padding import lib
ModuleNotFoundError: No module named '_cffi_backend'

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

• Put any pre-requisite steps here...
• az storage container create --account-name {} --account-key {} --name {}

Expected Behavior

Environment Summary

Linux-4.4.0-19041-Microsoft-x86_64-with-fedora-31-Generic
Python 3.7.6

azure-cli 2.1.0 *

Extensions:
azure-devops 0.17.0

Additional Context

[yonzhan]

add to S171

[yonzhan]

add to S172

[Juliehzl]

@praveen-pk May I know how you install azure cli?
If you are using pip install, could you try python3 -m pip install cffi to resolve the issue as shown in inducer/pyopencl#95?

For more inforamtion, you can see
https://github.com/Azure/azure-cli/blob/dev/doc/install_troubleshooting.md#errors-on-install-with-cffi-or-cryptography
(1 liked)Azure/azure-cliAzure Command-Line Interface. Contribute to Azure/azure-cli development by creating an account on GitHub.github.com.

[praveen-pk]

I ran into this issue while using an older version of fedoraremix WSL Image. I reset my WSL environment recently and cannot reproduce the issue anymore. If this issue is not reproducible, please feel free to resolve it.