Bug 1299426

Summary: AttributeError: 'NoneType' object has no attribute 'add'
Product: [Community] Virtualization Tools Reporter: Oliver Leitner <never>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: berrange, crobinso, gscrivan, rbalakri
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-19 15:28:18 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:
Attachments:
Description Flags
Compile and Install and Error Log none

Description Oliver Leitner 2016-01-18 10:55:07 UTC
Created attachment 1115799 [details]
Compile and Install and Error Log

Type of error:
Reproducible, show-stopper

Follow up errors:
No icons/text shown in "storage"

Program Version:
Github version from 18.01.2016 / 11:30

OS:
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.3 LTS
Release:        14.04
Codename:       trusty

Kernel:
Linux MyOwn 4.3.0-040300rc6-lowlatency #201510182030 SMP PREEMPT Mon Oct 19 00:36:29 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Summary:
Starting freshly build and installed virt-manager from /usr/local/bin/virt-manager and trying to create a new machine does not work, causes the above error message in a box.

Attached:
virt-manager.build.log (build and install tasks logged)
virt-manager.log (output from ~/.cache/virt-manager/virt-manager.log)

Workaround:
Running the old version via /usr/bin/virt-manager

Bugtracker specific:
Needed to combine both logs, as your bugzilla doesnt support more than one attachment.

Comment 1 Oliver Leitner 2016-01-19 14:30:02 UTC
ok, i think i found the problem myself.

for some reason, the git version of virt-manager doesnt install under /usr/local anymore, but instead overwrites stuff in /usr.

so the version under /usr/bin indeed is the more current one, thats also why it might work.

the version i had under /usr/local was 1.2.1, somewhere around that version, the behaviour of the make install changed.

i dont know if thats a bug or a feature?

Comment 2 Cole Robinson 2016-01-19 15:28:18 UTC
The build system was changed a bit in the last release, the default install directory is different. The reason is that things like gsettings schema don't work by default under /usr/local, so the user had to do some extra steps to make it work. Use python setup.py configure --prefix=/usr/local to maintain the old behavior