stx-openstack: guestAgent core dumps on Debian
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Rafael Falcão |
Bug Description
Brief Description
-----------------
First Automated Sanity execution with STX-Openstack showed that now on Debian, when the application is applied guestAgent core dumps [1] are constantly generated. This did not happen for Sanity tests without stx-openstack applied.
[1] /var/lib/
Severity
--------
Minor: System/Feature is usable but several test result are wrongly marked as Failed due to these generated files
Steps to Reproduce
------------------
* Install the latest_build Debian ISO
* Upload stx-openstack (Debian stx)
* Apply stx-openstack
* Run stx-openstack Sanity (test automation)
Expected Behavior
------------------
No core dumps are generated
Actual Behavior
----------------
Several guestAgent coredumps can be found at /var/lib/
Reproducibility
---------------
Reproducible
System Configuration
-------
AIO-DX
Branch/Pull Time/Commit
-------
master:
* starlingx/
Last Pass
---------
N/A
Timestamp/Logs
--------------
Teardown started:
***Failure at test teardown: <...>stx-
Core dump or crash found on controller-0 :
[[
'-rw-r----- 1 root root 124142 2022-12-14_21-24-26 core.guestAgent
'-rw-r----- 1 root root 124464 2022-12-14_21-24-59 core.guestAgent
], []]
-----------
Test Failed at test teardown
Test Activity
-------------
Sanity
Workaround
----------
Skip the core dumps check by the end of each test case.
description: | updated |
Changed in starlingx: | |
assignee: | nobody → Rafael Falcão (rafaelvfalc) |
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.distro.openstack |
Changed in starlingx: | |
status: | In Progress → Fix Released |
Changed in starlingx: | |
importance: | Low → Medium |
tags: | added: stx.8.0 |
We found out that the issue is related to a segfault that happens in each deamon initialization (or restart).
[sysadmin@ controller- 0 ~(keystone_admin)]$ dmesg | grep -i 180638 [ 1224.468971] guestAgent[180638]: segfault at 0 ip 00007fbae5f74208 sp 00007ffcfd7ec830 error 4 in libc-2. 31.so[7fbae5f0f 000+14b000]
We will be trying to find a solution for this issue in the nfv service files. Another option can be deactivate the service in the system (if the service is no longer needed). We tried to remove the puppet provision and deprovision commands but it was not successful in order to start the platform without the service. Another modifications in other repos might be needed to deactivate the service.