The fm-api must start as early as possible so it can process alarms from other services. During a fresh install the fm-api host is a valid IP address, but after unlock it receives a host FQDN (for example: controller-0.internal). The fm-api service is started by systemctl, while dnsmasq is managed by SM. Even when dnsmasq is running, it may take some time before it can answer DNS queries. To handle this, the fm-api now checks whether the host FQDN can be resolved before starting the wsgi.Server. Tests performed: - AIO-DX IPv4 fresh install - AIO-DX IPv6 fresh install - AIO-DX swact - AIO-SX subcloud factory install - AIO-SX backup and restore Partial-Bug: 2116270 Change-Id: Ia41f948a5baf3aedff514dd74eeea95a068c044c Signed-off-by: Fabiano Correa Mercer <fabiano.correamercer@windriver.com>
Fault Management (FM)
The starlingx/fault repository handles Fault Management (FM) services1, and provides the fm command-line interface (CLI)2.
This repository is not intended to be developed standalone, but rather as part of the StarlingX Source System, which is defined by the StarlingX manifest3.
References
Description
Languages
Python
60.8%
C++
33.4%
Shell
3%
C
1.6%
Makefile
1.1%