Documentation

Deployment error when upgrading to OpenSearch 1.3 Adobe Commerce on Cloud infrastructure

Last update: Tue Sep 30 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

If you encounter deployment errors after upgrading OpenSearch from version 1.2 to 1.3 in Adobe Commerce on Cloud infrastructure, update the .magento/services.yaml file, commit and push the changes, reindex Adobe Commerce, and verify there are no validation errors.

Description description

Environment

  • Product: Adobe Commerce on Cloud infrastructure
  • Environment Type: Adobe Commerce Pro Cluster environments

Issue

When attempting to deploy code to the Staging or Production environment after upgrading OpenSearch from version 1.2 to 1.3, an error occurs:

E: Error parsing configuration files: services.opensearch.type: “opensearch:1.3” is not a valid service type

Resolution resolution

To resolve this issue, follow these steps:

  1. Ensure that the .magento/services.yaml file has been correctly updated with the new OpenSearch version. An example of correct entry in services.yaml is:

    code language-none 
    opensearch:
    type: opensearch:1
    disk: 1024

  2. Commit and push your changes to the repository using Git commands:

    1. Clone the repository, if you haven’t already done so.

      code language-none 
      git clone --branch <staging_branch> <repository_url>

    2. Navigate to your project directory, and make the necessary changes in:

      .magento/services.yaml

    3. Add and commit your changes.

      code language-none 
      git add .magento/services.yaml
git commit -m "Service Upgrade"

    4. Push your changes back to the remote repository.

      code language-none 
      git push origin <current_branch>

  3. Verify that there are no validation errors when pushing updates by checking deployment logs for any issues related to YAML parsing or service configurations.

  4. If you encounter further issues during deployment, ensure that all other services listed in services.yaml are correctly configured according to their respective versions.

  5. Reindex Adobe Commerce after making these changes.

  6. Test again by deploying code into the environment, ensuring no errors occur during this process.

The key to resolving this issue is to omit the minor version on the service.

If following these steps doesn’t resolve the issue, submit an Adobe Commerce ticket and include detailed information about the actions taken and any error messages received during deployment attempts.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f