Admin Sales Order Create Fails with PayflowPro

[pmclain]

Preconditions (*)

1. Magento 2.3.0
2. Configure Paypal PayFlow Pro for credit card payment method

Steps to reproduce (*)

1. Create new order in admin panel
2. Select credit card payment method for PayFlow Pro

Expected result (*)

1. Order placement succeeds

Actual result (*)

1. Order creation fails with error Invalid account number

The order creation fails because Magento_Payment/js/transparent fails to load. This file was moved in 2.2, 0ce439b#diff-b0845d35ccdd892fe5e1a93a9b714b66 and updated in requirejs-config 0ce439b#diff-7fec090bf536a50e1bdfa20e039e27edR9 0ce439b#diff-6de82c32cd46b3be45d4d65e403f4136R9

It looks like the file relocation was not ported to 2.3.0, but the requirejs-config was, causing the 404 error and order creation failure.

[magento-engcom-team]

Hi @pmclain. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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.

@pmclain do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[pmclain]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @pmclain. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @pmclain, here is your Magento instance.
Admin access: https://i-19763-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[pmclain]

[magento-engcom-team]

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: 👇

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

• 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 branch

  Details

  - 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]

@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-97154 were created