Unable to install sample data on 2.4.8-beta2 with PHP 8.4

[markshust]

Preconditions and environment

It appears that in Magento 2.4.8, the magento/module-bundle-sample-data module doesn't have PHP 8.4 as a supported version constraint.

Given this release is imminent, this is a very-used core feature, and will wreck havoc for anyone that attempts to install sample data on the new release, marking this as S0 severity.

I'm not sure if this was fixed internally, but will raise a ticket in the event it has not been.

Steps to reproduce

1. Install Magento 2.4.8-beta2 using PHP 8.4
2. Attempt to install sample data with bin/magento sampledata:deploy

Expected result

Sample data is successfully installed

Actual result

Error:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires magento/module-bundle-sample-data 100.4.* -> satisfiable by magento/module-bundle-sample-data[100.4.0-beta1, ..., 100.4.3].
    - magento/module-bundle-sample-data[100.4.0-beta1, ..., 100.4.0] require php ~7.3.0||~7.4.0 -> your php version (8.4.5) does not satisfy that requirement.
    - magento/module-bundle-sample-data[100.4.1-beta2, ..., 100.4.1-beta3] require php ~7.4.0||~8.0.0 -> your php version (8.4.5) does not satisfy that requirement.
    - magento/module-bundle-sample-data 100.4.1-beta4 requires php ~7.4.0||~8.0.0||~8.1.0 -> your php version (8.4.5) does not satisfy that requirement.
    - magento/module-bundle-sample-data 100.4.1 requires php ~7.4.0||~8.1.0 -> your php version (8.4.5) does not satisfy that requirement.
    - magento/module-bundle-sample-data[100.4.2-beta1, ..., 100.4.2] require php ~8.1.0||~8.2.0 -> your php version (8.4.5) does not satisfy that requirement.
    - magento/module-bundle-sample-data[100.4.3-beta3, ..., 100.4.3] require php ~8.1.0||~8.2.0||~8.3.0 -> your php version (8.4.5) does not satisfy that requirement.

Additional information

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

• 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-November. 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-November]

Hello @markshust

Thank you for reporting and collaboration,

We have gone through the provided steps, we are unable to reproduce it , please find the screenshot attached.

Could you please recheck and let us know if you still facing.

Hence this issue is marking as "Needs Update"

Thank You!