What Can I Do If an MCI Object Fails to Be Created?

Symptom

The MCI object fails to be created.

Troubleshooting

Run the kubectl describe mci mci-example -n demo command to view events. The following figures show example command outputs.

Case 1
Case 2

Solution

If an error is reported as shown in case 1, the listener port configured during MCI object creation has been used. You can use either of the following solutions:

Edit the MCI object that fails to be created and use an unused listener port.
Log in to the ELB console and delete the listener of the corresponding port.

If an error is reported as shown in case 2, karmada.io/elb.projectid is incorrectly configured during MCI object creation. In this case, you need to delete the created MCI and create a new one with the correct configuration.

Parent topic: Cluster Federation

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot