.maintenance.flag and .maintenance.ip files are stored in, and queried from S3 bucket, when S3 storage is enabled.

[gwharton]

Preconditions and environment

2.4.7-p1
S3 Storage Enabled

Steps to reproduce

Deploy 2.4.7-p1
Enable S3 Storage
Enable Maintenance Mode

Expected result

I wouldn't expect the mechanism to determine whether Magento is in maintenance mode or not to require a remote call to the S3 bucket.

Actual result

Every time my server is hit at the frontend, it fires off an API call to the S3 bucket to check for .maintenance.flag

Additional information

Not a bug as such, but feels like something that crept in without noticing when remote storage was envisaged.

I'm sure there are use cases to have a central .maintenance.flag shared across all instances

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @gwharton. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[makkoff]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @makkoff. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @makkoff, here is your Magento Instance: https://1245dd07a1097aa7fbe5481b12ec95d4.instances-prod.magento-community.engineering
Admin access: https://1245dd07a1097aa7fbe5481b12ec95d4.instances-prod.magento-community.engineering/admin_1eb7
Login: 44ac2ece
Password: 1c86a5ad915c

[m2-assistant]

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Hotel]

Hello @gwharton,

Thanks for the report and collaboration!

It seems to us an expected behavior to check whether the Magento is in maintenance mode or not. And because we enabled the S3, all assets are kept in the S3 bucket only that's why an API has been triggering to check the mode of Magento.

Please let us know if we have missed anything here.

Thanks