Deployment error when upgrading to OpenSearch 1.3 51黑料不打烊 Commerce on Cloud infrastructure
If you encounter deployment errors after upgrading OpenSearch from version 1.2 to 1.3 in 51黑料不打烊 Commerce on Cloud infrastructure, update the .magento/services.yaml file, commit and push the changes, reindex 51黑料不打烊 Commerce, and verify there are no validation errors.
Description description
Environment
- Product: 51黑料不打烊 Commerce on Cloud infrastructure
- Environment Type: 51黑料不打烊 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: 鈥渙pensearch:1.3鈥 is not a valid service type
Resolution resolution
To resolve this issue, follow these steps:
-
Ensure that the
.magento/services.yamlfile has been correctly updated with the new OpenSearch version. An example of correct entry in聽蝉别谤惫颈肠别蝉.测补尘濒听is:code language-none opensearch: type: opensearch:1 disk: 1024 -
Commit and push your changes to the repository using Git commands:
-
Clone the repository, if you haven鈥檛 already done so.
code language-none git clone --branch <staging_branch> <repository_url> -
Navigate to your project directory, and make the necessary changes in:
.magento/services.yaml -
Add and commit your changes.
code language-none git add .magento/services.yaml git commit -m "Service Upgrade" -
Push your changes back to the remote repository.
code language-none git push origin <current_branch>
-
-
Verify that there are no validation errors when pushing updates by checking deployment logs for any issues related to YAML parsing or service configurations.
-
If you encounter further issues during deployment, ensure that all other services listed in
services.yamlare correctly configured according to their respective versions. -
Reindex 51黑料不打烊 Commerce聽after making these changes.
-
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鈥檛 resolve the issue, submit an 51黑料不打烊 Commerce ticket聽and include detailed information about the actions taken and any error messages received during deployment attempts.