Fabiano Correa Mercer 3ee7272a78 Delay fm-api start until DNS is available
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>
2025-11-20 20:19:04 +00:00
2023-08-29 17:33:47 -03:00
2025-06-16 09:25:01 -03:00
2019-04-19 19:52:34 +00:00
2025-01-16 01:00:27 +00:00
2021-09-01 08:58:34 -04:00
2018-05-31 07:36:00 -07:00
2023-05-31 16:36:27 +00:00
2023-07-19 10:48:29 -03:00
2023-03-02 19:32:25 +00:00

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


  1. https://docs.starlingx.io/api-ref/fault↩︎

  2. https://docs.starlingx.io/cli_ref/fm.html↩︎

  3. https://opendev.org/starlingx/manifest.git↩︎

Description
StarlingX Fault Management
Readme 6.1 MiB
Languages
Python 60.8%
C++ 33.4%
Shell 3%
C 1.6%
Makefile 1.1%