-
Notifications
You must be signed in to change notification settings - Fork 403
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
route53 module fails with TypeError: a bytes-like object is required, not 'str' #313
Comments
Files identified in the description: If these files are inaccurate, please update the |
@t-readyroc thank you for raising this issue. the route53 module was recently refactored in #405. These changes should be in collection version 1.4. Could you try that out and let us know if that fixes your issue? |
Files identified in the description:
If these files are inaccurate, please update the |
Still getting same error after upgrading to
|
The traceback includes calls to the original boto rather than boto3/botocore
This implies you're still using the version from 1.3.0 or earlier. Please would you double check that you don't have an old copy of the collection installed. |
It worked after explicitly specifying the collection in the requirements.yml file. It seems that the collection I could see v1.3.0 is installed even without specifying the
Fix:
Thanks @tremble for your help! |
@BitPan Thanks for the confirmation here. There are a number of boto (rather than boto3) based modules which remain and will likely see a similar issue. Migrating all of them to boto3 is something we'd like to see, however it's a non-trival amount of work. Since this is ultimately a bug in the underlying library rather than our consumption of the library I'm going to close this issue. |
* fix public_access example
SUMMARY
This issue has been reported elsewhere, but is 2yrs old now & I'm hoping that the maintainers here can possibly help get the fix merged. The issue was reported in 2018, here, and there is a patch available, which actually fixes the issue, here, but the patch is only a branch, which is now behind master by several minor versions.
I actually attempted to run the playbook without boto, using only boto3, but that also failed ("boto required for this module"). As a side not, your README states that only boto3, not boto is required.
Anyway, I'm sure this report will be closed, but I wanted to make the maintainers aware that it's something that's affecting the users of your module, and am hoping that you can help to get the fix merged.
ISSUE TYPE
COMPONENT NAME
route53
ANSIBLE VERSION
CONFIGURATION
Empty output
OS / ENVIRONMENT
Red Hat 8.3.1. Ansible running on Tower 3.7.3
STEPS TO REPRODUCE
EXPECTED RESULTS
Records created
ACTUAL RESULTS
Type Error from subject
The text was updated successfully, but these errors were encountered: