- Newest
- Most votes
- Most comments
Hello
I understand that, you are getting error 'ModuleNotFoundError' with an error message 'No module named _awscrt' when you revised a deployment which was working fine before . You can see the python packages are available in your component artifacts-unarchived location in packages folder awscrt, awsiot, boto3, botocore. However, when you try to import from awsiot.greengrasscoreipc.clientv2 import GreengrassCoreIPCClientV2, you are observing the above mentioned error.
Can you please perform either of the following to see if the mentioned issue is mitigated:
- Try installing the package as a 'ggc_user" directly which ensures that whatever was missing from the artifact is now being picked up from the ggc_user site-packages.
=== sudo -u ggc_user python3 -m pip install awsiotsdk
- You can also specify the installation of necessary packages/libraries in the lifecycle section[1] of your component's recipe.
=== Lifecycle: Install: RequiresPrivilege: true Script: | python3 -m pip install awsiotsdk
Please look into the below custom component's recipe in the below workshop link for your reference : [+] https://catalog.workshops.aws/greengrass/en-US/chapter5-pubsubipc/10-step1
References:
[1] AWS IoT Greengrass component recipe reference - https://docs.aws.amazon.com/greengrass/v2/developerguide/component-recipe-reference.html
Thanks the mitigation worked for us, the actual problem is on the CI pipeline where there were few modifications on the component configurations and it started failing. Now its been fixed and working
Relevant content
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago