Skip to content

[action] [PR:25561] Include generated services in Sysmonitor#26194

Merged
vmittal-msft merged 1 commit intosonic-net:202511from
mssonicbld:cherry/202511/25561
Mar 16, 2026
Merged

[action] [PR:25561] Include generated services in Sysmonitor#26194
vmittal-msft merged 1 commit intosonic-net:202511from
mssonicbld:cherry/202511/25561

Conversation

@mssonicbld
Copy link
Collaborator

Why I did it

Starting from the systemd version used in Debian Trixie (systemd 257), systemd-sonic-generator creates service unit files in /run/systemd/generator/ to handle multi-instance dependency expansion on DPU and multi-ASIC platforms. systemd marks these units as UnitFileState=generated instead of enabled or static.

sysmonitor did not recognize "generated" as a valid state, causing these services to be silently skipped during health checks — they were missing from show system-health sysready-status and STATE_DB ALL_SERVICE_STATUS.

Work item tracking
  • Microsoft ADO (number only):

How I did it

Adds "generated" to the accepted UnitFileState values in sysmonitor.py, so that services with UnitFileState=generated are correctly reported in show system-health sysready-status.

This 1-line change adds "generated" to the accepted states so that all services are properly monitored regardless of where their unit file resides.

Tests

Added two unit tests to verify that the generated state is handled correctly:

  • test_get_unit_status_generated_running_ok — a service with UnitFileState=generated and ActiveState=active is reported as OK
  • test_get_unit_status_generated_inactive_not_ok — a service with UnitFileState=generated and ActiveState=inactive is reported as NOT OK

How to verify it

show system-health sysready-status

Which release branch to backport (provide reason below if selected)

  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

Signed-off-by: Sonic Build Admin [email protected]

A picture of a cute animal (not mandatory but encouraged)

<!--
     Please make sure you've read and understood our contributing guidelines:
     https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md

     ** Make sure all your commits include a signature generated with `git commit -s` **

     If this is a bug fix, make sure your description includes "fixes #xxxx", or
     "closes #xxxx" or "resolves #xxxx"

     Please provide the following information:
-->

#### Why I did it

Starting from the systemd version used in Debian Trixie (systemd 257), `systemd-sonic-generator` creates service unit files in `/run/systemd/generator/` to handle multi-instance dependency expansion on DPU and multi-ASIC platforms. systemd marks these units as `UnitFileState=generated` instead of `enabled` or `static`.

`sysmonitor` did not recognize `"generated"` as a valid state, causing these services to be silently skipped during health checks — they were missing from `show system-health sysready-status` and `STATE_DB ALL_SERVICE_STATUS`.

##### Work item tracking
- Microsoft ADO **(number only)**:

#### How I did it

Adds `"generated"` to the accepted `UnitFileState` values in `sysmonitor.py`, so that services with `UnitFileState=generated` are correctly reported in `show system-health sysready-status`.

This 1-line change adds `"generated"` to the accepted states so that all services are properly monitored regardless of where their unit file resides.

#### Tests

Added two unit tests to verify that the `generated` state is handled correctly:

- `test_get_unit_status_generated_running_ok` — a service with `UnitFileState=generated` and `ActiveState=active` is reported as OK
- `test_get_unit_status_generated_inactive_not_ok` — a service with `UnitFileState=generated` and `ActiveState=inactive` is reported as NOT OK

#### How to verify it

`show system-health sysready-status`

<!--
If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012.
-->

#### Which release branch to backport (provide reason below if selected)

<!--
- Note we only backport fixes to a release branch, *not* features!
- Please also provide a reason for the backporting below.
- e.g.
- [x] 202006
-->

- [ ] 202305
- [ ] 202311
- [ ] 202405
- [ ] 202411
- [ ] 202505
- [x] 202511

#### Tested branch (Please provide the tested image version)

<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->

- [ ] <!-- image version 1 -->
- [ ] <!-- image version 2 -->

#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->

<!--
 Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
-->

#### Link to config_db schema for YANG module changes
<!--
Provide a link to config_db schema for the table for which YANG model
is defined
Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md
-->

Signed-off-by: Sonic Build Admin <[email protected]>

#### A picture of a cute animal (not mandatory but encouraged)
@mssonicbld
Copy link
Collaborator Author

Original PR: #25561

@mssonicbld
Copy link
Collaborator Author

/azp run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@vmittal-msft vmittal-msft merged commit 43eaa83 into sonic-net:202511 Mar 16, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants