Error with fileLock path

[rogerdz]

Preconditions and environment

• Magento version 2.4-develop
• Anything else that would help a developer reproduce the bug

Steps to reproduce

1. Config lock provider = file: bin/magento setup:config:set --lock-provider=file --lock-file-path=var/locks
2. Run command: rm -rf var/locks && rm -rf pub/var/locks
3. Run command: bin/magento cache:clean
4. Login admin

Expected result

should only create 1 locks folder: magento_dir/var/locks

Actual result

create 2 separate folder locks: magento_dir/var/locks and magento_dir/pub/var/locks

Additional information

No response

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 @rogerdz. 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.

[m2-assistant]

Hi @engcom-Delta. 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

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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-Delta]

Hi @rogerdz ,

Verified the issue on 2.4-develop, it is reproducible.

Hence, Confirming the issue.

Steps to reproduce:-

1.Config lock provider = file: bin/magento setup:config:set --lock-provider=file --lock-file-path=var/locks
2.Run command: rm -rf var/locks && rm -rf pub/var/locks
3.Run command: bin/magento cache:clean
4.Login admin

Ran commands

Created 2 separate folder locks: magento_dir/var/locks and magento_dir/pub/var/locks

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-12090 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Delta. Thank you for verifying the issue.
Issue Available: @engcom-Delta, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.