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).
ALM-70310 Snapshot Audit Alarm

ALM-70310 Snapshot Audit Alarm

Description

This alarm is generated when there are abnormal snapshots in the result of a system audit.

Attribute

Alarm ID

Alarm Severity

Auto Clear

70310

Major

Yes

Parameters

Name

Meaning

Fault Location Info

  • servicename: specifies the name of the service for which the alarm is generated.

Additional Info

  • detail_info: provides detailed information about the alarm generated during snapshot audit.

Impact on the System

  • The abnormal snapshots cannot be managed by the system.
  • The orphan snapshot cannot be queried in FusionSphere OpenStack, but occupies the storage backend space.
  • The invalid snapshot is unavailable in the OpenStack system and occupies system resources.
  • The stuck snapshot becomes unavailable in the OpenStack system and occupies system resources.
  • If the snapshot status recorded in the cascading system is inconsistent with that in the cascaded systems, the snapshot cannot be used.

Possible Causes

  • An orphan snapshot exists in the system.
  • An invalid snapshot exists in the system.
  • The system contains snapshots that are in the intermediate state.
  • Snapshots in the cascading system are inconsistent with those in the cascaded systems.
NOTE:

Obtain the audit issue that caused the alarm from the alarm details and handle the issue according to the following procedure.

Procedure

NOTE:

If the audit alarm is generated in a cascaded FusionSphere OpenStack system, the alarm must be handled regardless of whether it is also generated in the cascading system. After the alarm is cleared, audit the cascading system (manually or using the automatic routine audit by the cascading system) to ensure data consistency between the cascading and cascaded systems.

  1. Obtain the value of Details in Additional Info in the alarm details and add .csv to the end of the value to generate the audit report name.
  2. Determine the deployment scenario of the current environment. Obtain the audit report.

  3. Obtain "Analyzing Audit Results" based on the scenario where the current environment is deployed.Identify the handling method based on the audit report name and handle the audit items.

  4. Determine the scenario where the current environment is deployed and obtain section "Manual Audit." Start the system audit again.

    • Region Type I scenario:
    • Region Type II and Region Type III scenarios:

  5. Check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 6.

  6. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 49516

Downloads: 33

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