|
Bugzilla – Full Text Bug Listing |
| Summary: | systemd[1]: "Started Process Core Dump" in journals on localhost, recurring issue with NetworkManager | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Varun Kumar Ojha <varun.ojha> |
| Component: | Network | Assignee: | Jonathan Kang <songchuan.kang> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | jcao, qe-virt, varun.ojha, xguo |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Support Config KVM
/usr/sbin/NetworkManager EXE file core file |
||
|
Description
Varun Kumar Ojha
2023-09-29 15:32:32 UTC
Created attachment 869844 [details]
/usr/sbin/NetworkManager EXE file
Created attachment 869845 [details]
core file
Why is the component KVM? IIUC the issue is with NetworkManager, right? What does that have to do with KVM or virtualization in general? You are absolutely correct, and I apologize for the confusion. The issue indeed appears to be related to NetworkManager, and there is no direct connection to KVM or virtualization. I kept KVM because it is seen twice on KVM. The use of "KVM" in the component field seems to be a misclassification. It should be corrected to accurately reflect that the problem is with NetworkManager and not KVM or virtualization. Thank you for pointing out this discrepancy, and I appreciate your attention to detail. Please let me know if you want the following actions: Shall I? 1. I can update the component field from "KVM" to "Network" to accurately reflect the software component involved in this issue. 2. Remove the term "virtualization" from the issue title to provide a more precise description of the problem. These changes will help us maintain clear and accurate records of reported issues. Your feedback is valuable in improving our issue-tracking process. Thanks! (In reply to Varun Kumar Ojha from comment #5) > Please let me know if you want the following actions: Shall I? > > 1. I can update the component field from "KVM" to "Network" to accurately > reflect the software component involved in this issue. > > 2. Remove the term "virtualization" from the issue title to provide a more > precise description of the problem. These changes sound good. I might as well make them while writing this... Following up, is the fix applied? The issue is not seen in recent builds but please confirm and update what has been changed and its resolution. Latest tests KVM: https://openqa.opensuse.org/tests/3618911#next_previous XEN: https://openqa.opensuse.org/tests/3618912#next_previous (In reply to Varun Kumar Ojha from comment #7) > Following up, is the fix applied? > The issue is not seen in recent builds but please confirm and update what > has been changed and its resolution. > > Latest tests > KVM: https://openqa.opensuse.org/tests/3618911#next_previous > XEN: https://openqa.opensuse.org/tests/3618912#next_previous NetworkManager was updated to version 1.44.2 a few days ago[1]. The changelog indicates a possible segment fault was fixed. Maybe that is related with this issue. *[1] https://build.opensuse.org/request/show/1115910 Marking the ticket as closed, the issue was not seen. We will monitor progress tickets, If it is reproducible, we can refer back. Thanks James Fehlig and Jonathan Kang |