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).
Stack Troubleshooting

Stack Troubleshooting

Symptom

Stacks fail to be deployed and are abnormal.

Possible Causes

  • Invocation of the CFE interface fails.
  • Resource creation times out.
  • Resource names are duplicate.

Troubleshooting Method

  1. Log in to FusionStage.

    1. Use a browser to log in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios) as a VDC administrator or VDC operator.
      Login address:
      • Login address in a non-B2B scenario: https://Address for accessing ManageOne Operation Portal, for example, https://console.demo.com.
      • Login address in the B2B scenario: https://Address for accessing ManageOne Tenant Portal, for example, https://tenant.demo.com
    2. Select your region and then project from the drop-down list on the top menu bar.
    3. Choose Console > Application > FusionStage from the main menu.

  2. Choose Application Publishing > Application Orchestration > Stack.
  3. Access the abnormal stack details page and click Execution Logs to view the error information.
  4. Use the logs to analyze the possible causes.

    • Invocation of the CFE interface fails.
      1. Use PuTTY to log in to the manage_lb1_ip node.

        The default username is paas, and the default password is QAZ2wsx@123!.

      2. Run the following command and enter the password of the root user to switch to the root user:

        su - root

        Default password: QAZ2wsx@123!

      3. Run the following command to query the pod status:

        kubectl get pod -n fst-manage |grep cfe-api

        • If the pod is abnormal, run the following command to restart it:

          kubectl delete pod -n fst-manage podname

          podname indicates the queried pod name.

        • If the pod is normal, contact technical support for assistance.
    • Resource creation times out.
      1. View the logs to identify abnormal resources and their types. Resource types include daemonsets, deployments, and jobs.
      2. Locate the cause.
        1. Access the abnormal stack details page and click Elements to identify abnormal resources. Click the resources. In the displayed application management page, view application events to locate the cause and rectify the fault. If the fault persists, contact technical support for assistance.
        2. Log in to the master on which abnormal stacks are deployed as the paas user.
        3. Run the following command and enter the password of the root user to switch to the root user:

          su - root

          Default password: QAZ2wsx@123!

        4. Run the following commands to query events, view the error information, and rectify the fault. Table 20-1 lists error information.

          kubectl get {resource type} {resource name} resourcename -n namespace -oyaml

          Table 20-1 Error information

          Error Information

          Meaning and Solution

          fit no node

          The node tag is inconsistent with the filtering tag of the application resource. Modify the node tags.

          pull image error

          The image URL specified when deploying the stack is incorrect. Redeploy the stack.

          mount volume failed

          Contact technical support for assistance.

    • Resource names are duplicate. Repeated stack deployment leads to duplicate resource names, because resource names are fixed in a design package. Change resource names in the design package to resolve this problem.
    • If the problem persists, contact technical support for assistance.

Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 2115

Downloads: 12

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