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 Alarm and Event Reference 04

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).
1060016 Failed to Expand the Capacity of an EVS Disk

1060016 Failed to Expand the Capacity of an EVS Disk

Description

Failed to expand the capacity of an EVS disk.

Attribute

ID

Alarm Severity

Auto Clear

1060016

Minor

No

Parameters

Parameter

Description

ID

Indicates the event ID.

Object Type

Indicates the event type.

Generated At

Indicates the last time the event was generated.

Fault Location Info

TenantID

Indicates the ID of the tenant who is performing an operation when the event is generated.

VolumeID

Indicates the ID of the EVS disk for which the event is generated.

JobID

Indicates the ID of the task for which the event is generated.

Additional Info

Service

Indicates the service name.

MicroService

Indicates the microservice name.

Operation

Indicates the operation name.

ErrorPhase

Indicates the error phase.

ErrorMessage

Indicates the error message.

Impact on the System

None

Possible Causes

  • An exception occurs when a request for expanding the EVS disk capacity is delivered to FusionSphere OpenStack Cinder.
  • The underlying capacity expansion failed. As a result, the EVS disk is in the error_extending state.
  • A timeout occurs when FusionSphere OpenStack Cinder expands the EVS disk capacity.

Procedure

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

    • The login address is https://Address for accessing ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943.
    • Default username: admin; default password: Huawei12#$

  2. In the navigation tree, choose Alarms > Event Logs. Click Filter to filter the event based on the event name.
  3. Query the following event information:

    • Fault Location Info (including VolumeID, TenantID, and JobID)
    • Additional Info
    • Generated At

  4. If a joint locating with other components is required and the alarm information does not provide information for locating faults occurred on other components, obtain the location information from the log. If no, skip this step.

    1. Use PuTTY to log in to the CPT-SRV01 node using the IP address corresponding to the CPT-SRV01 field (searching in the xxx_export_all_EN.xlsm file) and log in to the CPT-SRV02 node using the IP address corresponding to the CPT-SRV02 field (searching in the xxx_export_all_EN.xlsm file).

      Default account: apicom, default password: Huawei12#$

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

      The default password of user root is Cloud12#$.

      sudo su root

    3. Run the following command to switch to the directory containing EVS disk logs:

      cd /var/log/apicom/taskmgr/dbs

    4. Run the following command to query all logs relating to the task according to JobID:

      grep -n "jobId" * | less

    5. If the obtained log information is too much for viewing, use query composition to query precise information. An example is provided to query the log information of one specific minute:

      grep -n "jobId" * | grep "2018-04-10 12:07" | less

  5. Query the additional information. If Operation is extendVolume, the EVS disk capacity fails to be expanded. Determine the phase when the error occurs based on ErrorPhase.

    • If ErrorPhase is Failed to Expand the Capacity of an EVS Disk, go to 6.
    • If ErrorPhase is Monitored a Failed Capacity Expansion of an EVS Disk, check whether the error information contains the following information:
      • If extend volume: No Valid host was found. No weighed hosts available is displayed, the cinder cannot find proper backend storage when scheduling backend storage. Perform the following operations to locate the fault:
        • On the Service OM page, check whether the backend storage in volume_type has sufficient virtual and physical capacity. If the backend storage capacity is insufficient, expand the storage pool or add a new storage pool by following the instructions in Capacity Expansion for Service Storage (SAN and FusionStorage Block) in HUAWEI CLOUD Stack 6.5.0 Capacity Expansion Guide.
      • If extend volume: Bad or unexpected response from the storage volume backend API is displayed, capacity expansion at the cinder-volume layer failed. Check whether the error information contains the following information:
        • If Check LUN exist error is displayed, the device responds an exception when the cinder driver connects to the device. Check whether the Management Storage Link or Authentication Failure alarm (alarm ID: 6024) is reported on ManageOne Maintenance Portal. If yes, clear the alarm by referring to HUAWEI CLOUD Stack 6.5.0 Alarm&Event Reference.

      If the preceding information is not displayed or the failure cause cannot be identified, go to 7.

  6. Perform the following steps to determine the problem cause:

    Query Additional Info. If Additional Info contains ClientException, the request of expanding the EVS disk capacity fails to be delivered. Locate the fault by referring to Troubleshooting Guide for Typical Cinder Problems. If the fault persists, provide the disk ID to the FusionSphere OpenStack Cinder O&M personnel to locate and rectify the fault.

  7. Query Additional Info and determine the cause of the failure:

    • If Additional Info contains the volume status is error_extending, it indicates that the status of the disk is incorrect.
    • If Additional Information contains the volume status is extending, the capacity expansion times out. Contact the FusionSphere OpenStack Cinder O&M personnel to locate the fault and check whether disk expansion is complete. If the capacity expansion is not complete, wait until the execution is complete. If the operation is successful, contact O&M personnel to update the VDC quota.
    • If Additional Info contains ClientException, it indicates that obtaining the disk information is abnormal.

    If the cause of the capacity expansion failure cannot be confirmed, locate the fault by referring to Troubleshooting Guide for Typical Cinder Problems. Provide the disk ID and last occurrence time you have obtained to the FusionSphere OpenStack Cinder O&M personnel to locate and rectify the fault.

  8. After the problem is resolved, contact the user to expand the EVS disk capacity again.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 35867

Downloads: 31

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