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


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


FusionCloud 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).
Service Publishing Failure

Service Publishing Failure


When a service publisher publishes a service, the service status is abnormal, resulting in the service publishing failure.

Possible Causes

  • Backend stack resources failed to be created.
  • Health check failed.
  • Backend components are abnormal.

Troubleshooting Method

  1. Log in to the ServiceStage tenant management zone console.

    1. Use a browser to log in to the ManageOne operation plane as a VDC administrator or a VDC operator.
      • Login address in non-B2B scenarios: https://Address for accessing the console homepage, for example,
      • Login address in B2B scenarios: https://Address to access the tenant portal of the ManageOne operation plane, for example,
    2. Select your region and then project from the drop-down list on the top menu bar.
    3. On the home page, choose Application > Container Application Platform.

      Alternatively, choose Console > Application > Container Application Platform from the main menu.

  2. Choose Marketplace > Service > My Service from the main menu.
  3. Click HandleLog in the target service area to check the type of the issue.
  4. For service stack creation failures, choose AppRelease > App Orchestration > Stack from the main menu to go to the Stack page and search for the mapping stack using the service name as keywords. Then perform the next step based on section Stack Troubleshooting.
  5. If the health check fails, contact support engineers for assistance.
  6. If backend components are abnormal, collect related logs and contact support engineers for assistance.
  7. Clear resources you created when the abnormality occurred, use services again, and check whether statuses of services or instances are normal.
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 23020

Downloads: 37

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