No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Troubleshooting Guide 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
The System Cannot Self-heal After the VM Is Restarted

The System Cannot Self-heal After the VM Is Restarted

Symptom

When the cloud storage is disconnected from the VM for more than 90s, and the VM is restarted, the system cannot self-heal due to lack of the system disk.

Troubleshooting Method

The system cannot self-heal when there is no system disk. Manually restart the VM that is connected to the storage after the storage link is restored.

  1. Log in to ManageOne Maintenance Portal using a browser.

    • Login address: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943.
    • The default username is admin, and the default password is Huawei12#$.

  2. In the navigation bar on the top of the page, choose O&M Maps to switch to the O&M Maps page.
  3. In the Quick Links navigation pane on the right of the O&M Maps page, click Service OM.
  4. Choose Services > Computing > ECS > Compute Instances > VMs. On the page displayed, select the name of the FusionSphere OpenStack system where FusionStage VMs reside in the upper left corner of the page and search for FusionStage VMs among all VMs using the keyword "manage". If there are Addon nodes in the data zone, power off the Addon nodes first. If there are no Addon nodes in the data zone, sequentially restart docking storage for VM exception nodes. You can power off the nodes in any sequence.
  5. After the VM is restarted, log in to the VM using SSH. If you can successfully log in to the VM, the fault is rectified.
  6. If the problem persists, contact technical support for assistance.
Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 1542

Downloads: 12

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next