500 Series Alarm Messages¶
The system inventory and maintenance service reports system changes with different degrees of severity. Use the reported alarms to monitor the overall health of the system.
Alarm messages are numerically coded by the type of alarm.
For more information, see Fault Management Overview.
In the alarm description tables, the severity of the alarms is represented by one or more letters, as follows:
C: Critical
Indicates that a platform service affecting condition has occurred and immediate corrective action is required. (A mandatory platform service has become totally out of service and its capability must be restored.)
M: Major
Indicates that a platform service affecting condition has developed and urgent corrective action is required. (A mandatory platform service has developed a severe degradation and its full capability must be restored.)
or -
An optional platform service has become totally out of service and its capability should be restored.
m: Minor
Indicates that a platform non-service affecting fault condition has developed and corrective action should be taken in order to prevent a more serious fault. (The fault condition is not currently impacting / degrading the capability of the platform service.)
W: Warning
Indicates the detection of a potential or impending service affecting fault. Action should be taken to further diagnose and correct the problem in order to prevent it from becoming a more serious service affecting fault
A slash-separated list of letters is used when the alarm can be triggered with one of several severity levels.
An asterisk (*) indicates the management-affecting severity, if any. A management-affecting alarm is one that cannot be ignored at the indicated severity level or higher by using relaxed alarm rules during an orchestrated patch or upgrade operation.
Note
Degrade Affecting Severity: Critical indicates a node will be degraded if the alarm reaches a Critical level.
Alarm ID: 500.100 |
TPM initialization failed on host. |
Entity Instance |
tenant=<tenant-uuid> |
Degrade Affecting Severity: |
None |
Severity: |
M |
Proposed Repair Action |
Reinstall HTTPS certificate; if problem persists contact next level of support. |
Alarm ID: 500.101 |
Developer patch certificate enabled. |
Entity Instance |
host=controller |
Degrade Affecting Severity: |
None |
Severity: |
C |
Proposed Repair Action |
Reinstall system to disable developer certificate and remove untrusted patches. |
Alarm ID: 500.200 |
Certificate ‘system certificate-show <uuid>’ (mode=<ssl/ssl_ca/docker_registry/openstack/openstack_ca>) expiring soon on <date>. OR Certificate ‘<Namespace>/<Certificate/Secret>’ expiring soon on <date>. OR Certificate ‘<k8sRootCA/EtcdCA>’ expiring soon on <date>. system.certificate.k8sRootCA |
Entity Instance |
system.certificate.mode=<mode>.uuid=<uuid> OR namespace=<namespace-name>.certificate=<certificate-name> OR namespace=<namespace-name>.secret=<secret-name> |
Degrade Affecting Severity: |
None |
Severity: |
M |
Proposed Repair Action |
Renew certificate for the entity identified. |
Management_Affecting_Severity: |
none |
Alarm ID: 500.210 |
Certificate ‘system certificate-show <uuid>’ (mode=<ssl/ssl_ca/docker_registry/openstack/openstack_ca>) expired. OR Certificate ‘<Namespace>/<Certificate/Secret>’ expired. OR Certificate ‘<k8sRootCA/EtcdRootCA>’ expired. |
Entity Instance |
system.certificate.mode=<mode>.uuid=<uuid> OR namespace=<namespace-name>.certificate=<certificate-name> OR namespace=<namespace-name>.secret=<secret-name> OR system.certificate.k8sRootCA |
Degrade Affecting Severity: |
None |
Severity: |
C |
Proposed Repair Action |
Renew certificate for the entity identified. |
Management_Affecting_Severity: |
none |