Bug 1497941

Summary: ovirt-fence-kdump-listener fails to start on fedora 25
Product: [oVirt] ovirt-engine Reporter: Eli Mesika <emesika>
Component: ServicesAssignee: Eli Mesika <emesika>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: low Docs Contact:
Priority: low    
Version: 4.2.0CC: bugs, lleistne, michal.skrivanek, mperina
Target Milestone: ovirt-4.4.1Flags: rule-engine: ovirt-4.4+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-01 14:33:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1460625    
Attachments:
Description Flags
DEBUG information none

Description Eli Mesika 2017-10-03 07:56:54 UTC
Created attachment 1333542 [details]
DEBUG information

Description of problem:
ovirt-fence-kdump-listener fails to start on fedora 25

Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps to Reproduce:
1.export OVIRT_SERVICE_DEBUG=1
2.<ovirt>/share/ovirt-engine/services/ovirt-fence-kdump-listener/ovirt-fence-kdump-listener.py start
3.

Actual results:

service fails to validate db connection 

Expected results:

service should start 


Additional info:

log attached

Comment 1 Sandro Bonazzola 2020-01-23 12:31:48 UTC
Can you please check if this is still an issue on Fedora >= 30?

Comment 2 Eli Mesika 2020-02-18 13:17:05 UTC
(In reply to Sandro Bonazzola from comment #1)
> Can you please check if this is still an issue on Fedora >= 30?

kdump listener service is starting without issues on CentOs8 and fc30 after fixing python3 issue (merged upstream) [1]

[1] https://gerrit.ovirt.org/#/c/106942/

Comment 3 Michal Skrivanek 2020-03-19 15:42:25 UTC
We didn't get to this bug for more than 2 years, and it's not being considered for the upcoming 4.4. It's unlikely that it will ever be addressed so I'm suggesting to close it.
If you feel this needs to be addressed and want to work on it please remove cond nack and target accordingly.