Internal Server Error in /V1/order/{orderId}/ship API Endpoint

[rogerdz]

Description (*)

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes Internal Server Error in /V1/order/{orderId}/ship API Endpoint #35931

Manual testing scenarios (*)

1. ...
2. ...

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @rogerdz. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.

Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[rogerdz]

@magento run all tests

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

[engcom-Hotel]

@magento run all tests

[engcom-Hotel]

Hello @rogerdz,

Thanks for the contribution!

Please look into the failed tests it seems multiple tests are failing due to this change.

Thanks

[rogerdz]

@magento run all tests

[rogerdz]

@magento run all tests

[rogerdz]

@magento run all tests

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run Functional Tests B2B, Functional Tests CE, Functional Tests EE, Integration Tests

[engcom-Dash]

@engcom-Hotel I have verified the failing functional Test cases are not because of this PR changes. They are inconsistent and seems to be flaky. Also the integration failures observed on the other PRs too.

B2B Run 1 B2B Run 2

CE Run 1 CE Run 2

EE Run 1 EE Run 2

Known Issues:
https://jira.corp.adobe.com/browse/AC-15240
https://jira.corp.adobe.com/browse/ACQE-8335
https://jira.corp.adobe.com/browse/AC-15248

Could you please review this PR?

[engcom-Hotel]

@magento run all tests