Closed torhoehn closed 5 years ago
Hi @torhoehn. Thank you for your report. To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento-engcom-team give me $VERSION instance
where $VERSION
is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.
@torhoehn do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
@magento-engcom-team give me 2.3-develop instance
Hi @torhoehn. Thank you for your request. I'm working on Magento 2.3-develop instance for you
Hi @torhoehn, here is your Magento instance.
Admin access: http://34.228.235.121/i-19115-2-3-develop//admin
Login: admin
Password: 123123q
Instance will be terminated in up to 3 hours.
Hi @engcom-backlog-nazar. 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: :point_down:
[x] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).Details
If the issue has a valid description, the label Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.
[x] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description
label to the issue by yourself.
[ ] 3. Add Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.3-develop
branchDetails
- Add the comment @magento-engcom-team give me 2.3-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.3-develop
branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop
branch. Details
- Add the comment @magento-engcom-team give me 2.2-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.2-develop
branch, please add the label Reproduced on 2.2.x
[ ] 6. Add label Issue: Confirmed
once verification is complete.
[ ] 7. Make sure that automatic system confirms that report has been added to the backlog.
@magento-engcom-team Unfortunately it's working vanilla Magento instance.
Hi @torhoehn seem like this already fixed in 2.3-dev branch, i'm also cannot reproduce on 2.3-dev. If you like to update this please reopen the issue.
@engcom-backlog-nazar Do you know if something has changed or an idea where I have to search for that? So I would be able to apply a fix manually in our project.
@torhoehn Sorry i'm can't find where this was fixed, i was try search in history commits, but not found any related commits
@engcom-backlog-nazar We updated to Magento ver. 2.3.0-beta32. Now it's working again.
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)