InvalidRequestBody Is Reported When a Grayscale Release Task Is Created for a Service with Multiple Ports
Symptom
When a grayscale release task is created for a service with multiple ports, "ASM.0002 InvalidRequestBody" is reported.
Fault Location
Log in to the ASM console, press F12, and switch to the Network tab to view APIs. Error code 400 is returned when each POST request is sent to create a grayscale release task. The returned information is as follows:
some ports of the service have been configured with routes, ports=[%v]
Analysis
Some ports are deleted from the service that is properly configured. For example, service01 has two ports 80 and 81, and port 81 is deleted on the CCE console.
Solution
Restore the deleted service ports.
Performing Grayscale Release FAQs
- Why Can't I Change the Image Used for the Grayscale Version When Performing Grayscale Release?
- Why Does Not a Grayscale Policy that Based on Request Content Take Effect for Some Services?
- InvalidRequestBody Is Reported When a Grayscale Release Task Is Created for a Service with Multiple Ports
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
