Bug 1674040

Summary: Stuck on "Checking for virtulization packages" part when it starts up
Product: [Community] Virtualization Tools Reporter: Anex Johnson <anexjohnson007>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED UPSTREAM QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: berrange, crobinso, gscrivan, tburke
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-08 20:52:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
This is the output from giving the --debug option none

Description Anex Johnson 2019-02-08 20:13:42 UTC 
Created attachment 1528218 [details]
This is the output from giving the --debug option

Description of problem:
It wont automatically connect when it starts up 
I'm running void linux with musl: here is the issue i opened in void linux's repo
https://github.com/void-linux/void-packages/issues/8338

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


How reproducible:

Steps to Reproduce:
1.  Open virt-manager

Actual results:
It prints "Checking for virtulization packages" and is stuck in this part

Expected results:
It shoul've connected to the hypervisor when it starts up


Additional info:
It was a simple fix in "virtManager/engine.py:164"
when the variable unitpath is reference in the logging line, the fix was to add a default empty string value for the variable unitpath in "virtManager/engine.py" at line 138
Comment 1 Cole Robinson 2019-02-08 20:52:25 UTC 
Thanks for the report and the diagnosis, that's unfortunate, typically pylint catches those issues. I've fixed it upstream

commit ae8a4f3db3c1492a219a0d6ec8d32c765ac076bd (HEAD -> master, origin/master, origin/HEAD)
Author: Cole Robinson <crobinso>
Date:   Fri Feb 8 15:50:15 2019 -0500

    engine: Fix first run startup error (bz 1674040)
    
    unitpath can be used uninitialized
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1674040