[Starlingx-discuss] command "fm alarm-show 800.011" doesn't work
钱江
qianjiang at baicells.com
Fri Sep 20 04:06:50 UTC 2019
Hi,
I got an error during applying the openstack application. I don't know how to check the log, later I find "fm" command may work.
[sysadmin at controller-0 ~(keystone_admin)]$ fm alarm-list
+----------+---------------------------------------------------------------------+--------------------------------------+----------+-----------------------+
| Alarm ID | Reason Text | Entity ID | Severity | Time Stamp |
+----------+---------------------------------------------------------------------+--------------------------------------+----------+-----------------------+
| 200.001 | controller-0 was administratively locked to take it out-of-service. | host=controller-0 | warning | 2019-09-20T03:36:20. |
| | | | | 251464 |
| | | | | |
| 750.002 | Application Apply Failure | k8s_application=stx-openstack | major | 2019-09-20T02:03:28. |
| | | | | 153979 |
Then, I use "fm alarm-show" to get details
[sysadmin at controller-0 ~(keystone_admin)]$ fm alarm-show 750.002
Alarm not found: 750.002
It says, the alarm is not found, isn't the "750.002" uuid?
Or is there another way to check the log of an applicaiton failure?
[sysadmin at controller-0 ~(keystone_admin)]$ system application-show stx-openstack
+---------------+------------------------------------------+
| Property | Value |
+---------------+------------------------------------------+
| active | False |
| app_version | 1.0-18-centos-stable-latest |
| created_at | 2019-09-19T06:44:02.827627+00:00 |
| manifest_file | stx-openstack.yaml |
| manifest_name | armada-manifest |
| name | stx-openstack |
| progress | operation aborted, check logs for detail |
| status | apply-failed |
| updated_at | 2019-09-20T02:03:28.251645+00:00 |
+---------------+------------------------------------------+
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190920/06d1273e/attachment.html>
More information about the Starlingx-discuss
mailing list