# \[K8S\] RecursionError when initializing with MinIO **URL:** \ **Category:** Tutor Help\ **Tags:** tutor\ **Created:** [June 5, 2025, 11:11am UTC](https://discuss.openedx.org/t/k8s-recursionerror-when-initializing-with-minio/16250 "2025-06-05T11:11:24Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Retr0](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/retr0/32/8020_2.png) [@Retr0](https://discuss.openedx.org/u/Retr0)\ **Post date:** [June 5, 2025, 11:11am UTC](https://discuss.openedx.org/t/k8s-recursionerror-when-initializing-with-minio/16250/1 "2025-06-05T11:11:24Z")
Hello everyone, I am configuring a high availability Open edX installation using Tutor. I am running on AWS with: - Main installation at an EKS cluster. - MySQL using AuroraDB-MySQL - MongoDB using AWS - Redis using AWS Elastic Cache cluster - SMTP using AWS SES - MeiliSearch and MinIO using the provided ones by Tutor. - Their storage providers are AWS EFS setup at the cluster using their CSI controller. When I tried to init the platform, the LMS init job that was applying the migrations run into the following RecursionError when applying a specific migration: ```auto Traceback (most recent call last): File "/openedx/edx-platform/lms/djangoapps/certificates/migrations/0003_data__default_modes.py", line 20, in forwards conf.icon.save( File "/openedx/venv/lib/python3.11/site-packages/django/db/models/fields/files.py", line 93, in save self.name = self.storage.save(name, content, max_length=self.field.max_length) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ < lines have been omitted > File "/openedx/venv/lib/python3.11/site-packages/botocore/awsrequest.py", line 614, in __init__ self.update(*args, **kwargs) File "", line 947, in update File "", line 119, in __instancecheck__ RecursionError: maximum recursion depth exceeded in comparison ``` This specific migration causes an infinite loop which results in the script crashing. I looked into it further and it is related to S3 storage, which in this case is handled by MinIO. I have tried the following with no luck in fixing this: - Clean install Tutor. Purge all config and reconfigure again. - Delete the MinIO persistent volume and let it recreate it/re-initialize it. - Disabling and setting up the plugin again. I have also checked multiple times my configuration but it should not be something caused by it, mainly because I did not change the Tutor-provided init values. I am attaching a log file of the job in case it can be helpful. Any ideas on what could cause this or how to fix it would be greatly appreciated. [log.txt](https://discuss.openedx.org/uploads/short-url/g8KxBh31j9vQ9DTbFX35wFNyyng.txt) (9.6 KB) ---
**Author:** ![Retr0](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/retr0/32/8020_2.png) [@Retr0](https://discuss.openedx.org/u/Retr0)\ **Post date:** [June 5, 2025, 1:26pm UTC](https://discuss.openedx.org/t/k8s-recursionerror-when-initializing-with-minio/16250/2 "2025-06-05T13:26:22Z")
I did some more digging and found out this resolved issue: [Minio breaks migrations with fresh install on teak · Issue #61 · overhangio/tutor-minio · GitHub](https://github.com/overhangio/tutor-minio/issues/61) Could these two be related? cc: @Danyal_Faheem ---
**Author:** ![Danyal\_Faheem](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/danyal_faheem/32/8121_2.png) [@Danyal\_Faheem](https://discuss.openedx.org/u/Danyal_Faheem)\ **Post date:** [June 5, 2025, 2:15pm UTC](https://discuss.openedx.org/t/k8s-recursionerror-when-initializing-with-minio/16250/3 "2025-06-05T14:15:07Z")
Hi @Retr0, thank you for bringing this to our attention. Looking at the 2 issues, they indeed do appear on the same migration step but I believe that is because that is the first time in the setup process that S3 is used (to upload files). The issue mentioned in [Minio breaks migrations with fresh install on teak · Issue #61 · overhangio/tutor-minio · GitHub](https://github.com/overhangio/tutor-minio/issues/61) occurred due to a [boto3 version upgrade](https://github.com/boto/boto3/issues/4392) which was made in the edx-platform master branch and a release with that branch is yet to be cut. From the very helpful logs provided, I can see that boto3 tries to retry the put request and look for the bucket region. Can you verify that the bucket specified is accessible by openedx? Can I also request you to mention the tutor and tutor-minio version being used so that we can try to look into this further? ---
**Author:** ![Retr0](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/retr0/32/8020_2.png) [@Retr0](https://discuss.openedx.org/u/Retr0)\ **Post date:** [June 5, 2025, 7:14pm UTC](https://discuss.openedx.org/t/k8s-recursionerror-when-initializing-with-minio/16250/4 "2025-06-05T19:14:39Z")
Hey @Danyal_Faheem thanks for the quick response! The bucket specified _should_ be accessible considering MinIO is running using the default options provided by the [plugin](https://github.com/overhangio/tutor-minio?tab=readme-ov-file#configuration). I can also verify that the main bucket (“openedx”) exists through the console panel. One thing I noticed and I believe is worth mentioning is that the `files.{{ LMS_HOST }}` application is extremely slow and eventually times out when tried to visit from a browser. All other apps of Tutor (e.g. `meilisearch.{{ LMS_HOST }}` or `minio.{{ LMS_HOST }`) are working normally so I don’t have a reason to believe it’s a DNS issue. tutor version: tutor, version 19.0.4 tutor-minio version: 19.0.1 ---
**Author:** ![Retr0](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/retr0/32/8020_2.png) [@Retr0](https://discuss.openedx.org/u/Retr0)\ **Post date:** [June 9, 2025, 10:35am UTC](https://discuss.openedx.org/t/k8s-recursionerror-when-initializing-with-minio/16250/5 "2025-06-09T10:35:23Z")
I have resolved the issue! For anyone else that might stumble upon this in the future… Read carefully the [Configuration and customisation — Tutor documentation](https://docs.tutor.edly.io/configuration.html#ssl-tls-certificates-for-https-access) section for HTTPS access. In my setup HTTPS termination was done by the AWS Application Load Balancer. This means that visiting a “http” link will redirect you to its “https” counterpart with no issues so with that I mind I set `ENABLE_HTTPS=false` and `ENABLE_WEB_PROXY=false`. **But this doesn’t apply to any applications.** Applications (like `curl` which helped me realize the issue after a lot of testing) will use “http” links if `ENABLE_HTTPS=false` which means that they will encounter a `301 Moved Permanently` error. This causes an infinite redirection loop in this specific case of boto3. So all I had to do is set `ENABLE_HTTPS=true` so they use the “https” links directly and dodge the 301 redirection loop.