PyInstaller update causes libsqlite3.so ImportError with nested aws cli in credential_process

[TGNThump]

I'm unsure if this is caused by the same issue. If not, happy to make a new issue.
We're seeing client failure from failing to find libsqlite3.so when running a aws cli call within a credential_process in aws config. This is a new issue introduced in 2.24.14. Rolling back the aws-cli snap to v2.24.13 resolves the issue.

[PYI-3717972:ERROR] Failed to execute script 'aws' due to unhandled exception!
Error when retrieving credentials from custom-process: Traceback (most recent call last):
  File "aws.py", line 19, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 384, in exec_module
  File "awscli/clidriver.py", line 70, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 384, in exec_module
  File "awscli/autoprompt/core.py", line 16, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 384, in exec_module
  File "awscli/autoprompt/prompttoolkit.py", line 25, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 384, in exec_module
  File "awscli/autocomplete/local/model.py", line 20, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 384, in exec_module
  File "awscli/autocomplete/db.py", line 3, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 384, in exec_module
  File "sqlite3/__init__.py", line 57, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 384, in exec_module
  File "sqlite3/dbapi2.py", line 27, in <module>
ImportError: libsqlite3.so: cannot open shared object file: No such file or directory
[PYI-3718033:ERROR] Failed to execute script 'aws' due to unhandled exception!

Our aws config looks like:

credential_process = aws configure export-credentials --profile SOME_OTHER_PROFILE_NAME_HERE --format process

For context, the reason for using a credential process with an aws cli call here is to make a shared_credential_file based profile refreshable.

Originally posted by @TGNThump in #9330

@TGNThump The hardcoded RPATH mentioned in this issue was introduced in 2.24.10, so it's unlikely the same issue (though it may be related/compounded by it). Version 2.24.14 upgraded PyInstaller, but was subsequently rolled back in 2.24.15 due to Alpine build regressions: #9331. Does upgrading to 2.24.15 resolve your issue? cc: @ashovlin for another potential PyInstaller upgrade regression.

Originally posted by @hssyoo in #9330

[TGNThump]

@hssyoo @ashovlin I can confirm upgrading to 2.24.15 resolves the issue, so it does seem to be a regression caused by the PyInstaller upgrade.

[RyanFitzSimmonsAK]

Thanks for reporting this issue. I'll be closing it, since it's resolved by upgrading to a more recent version. Future updates about the PyInstaller upgrade will be posted in #9330.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.