Debian: computes in degraded state due to sssd alarms

Bug #1988328 reported by Andy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
Medium
Andy

Bug Description

Brief Description
-----------------
After a standard system is installed, the computes remained in a degraded state due to sssd alarms for the nodes.

Severity
--------
Major: System/Feature is usable but degraded

Steps to Reproduce
------------------
- Install a standard Debian system
- system host-list show computes in degrade state
- fm alarm-list shows sssd service failed

Expected Behavior
------------------
Computes should go into the unlocked-enabled-available state with no alarms.

Actual Behavior
----------------
Computes are degraded due to sssd alarm.

Reproducibility
---------------
100% reproducible

System Configuration
--------------------
Multi-node Debian system

Branch/Pull Time/Commit
-----------------------
STX master latest.

Last Pass
---------
Unknown.

Timestamp/Logs
--------------
[sysadmin@controller-0 ~(keystone_admin)]$ fm alarm-list
+----------+-------------------------------------------------------------------------------------------------+---------------------------+----------+-------------------+
| Alarm ID | Reason Text | Entity ID | Severity | Time Stamp |
+----------+-------------------------------------------------------------------------------------------------+---------------------------+----------+-------------------+
| 100.103 | Memory threshold exceeded ; threshold 80.00%, actual 80.16% | host=controller-0.memory= | major | 2022-08-31T06:47: |
| | | platform | | 58.927290 |
| | | | | |
| 200.006 | compute-0 is degraded due to the failure of its 'sssd' process. Auto recovery of this major | host=compute-0.process= | major | 2022-08-31T02:32: |
| | process is in progress. | sssd | | 03.576791 |
| | | | | |
| 200.006 | compute-1 is degraded due to the failure of its 'sssd' process. Auto recovery of this major | host=compute-1.process= | major | 2022-08-31T02:25: |
| | process is in progress. | sssd | | 51.001852 |
| | | | | |
+----------+-------------------------------------------------------------------------------------------------+---------------------------+----------+-------------------+

Test Activity
-------------
Developer Testing

Workaround
----------
N/A

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to stx-puppet (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/stx-puppet/+/855387

Changed in starlingx:
status: New → In Progress
Andy (andy.wrs)
Changed in starlingx:
assignee: nobody → Andy (andy.wrs)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to stx-puppet (master)

Reviewed: https://review.opendev.org/c/starlingx/stx-puppet/+/855387
Committed: https://opendev.org/starlingx/stx-puppet/commit/fd874b5a5ee8a8a1d219b2d8e1cd04ee38b40592
Submitter: "Zuul (22348)"
Branch: master

commit fd874b5a5ee8a8a1d219b2d8e1cd04ee38b40592
Author: Andy Ning <email address hidden>
Date: Wed Aug 31 11:50:27 2022 -0400

    Enable sssd service on worker node

    This change enabled sssd service on work node.

    Test Plan on Debian:
    PASS: After worker node is unlocked, verify that sssd service
          is running.
    PASS: Verify worker node is in healthy states:
          unlocked | enabled | available
    PASS: Verify there are no alarms related to sssd service for
          worker nodes.
    PASS: Add a ldap user, and ssh to worker node by the newly added
          ldap user.

    Closes-Bug: 1988328
    Signed-off-by: Andy Ning <email address hidden>
    Change-Id: Icd76e0bd97c97c1eb146af280a96d04a59945ef7

Changed in starlingx:
status: In Progress → Fix Released
Ghada Khalil (gkhalil)
Changed in starlingx:
importance: Undecided → Medium
tags: added: stx.8.0 stx.debian stx.security
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.