[ https://ovirt-jira.atlassian.net/browse/OVIRT-733?page=com.atlassian.jira.pl... ] Evgheni Dereveanchin reassigned OVIRT-733: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra)

ovirt-node-ng leftover libvirt settings ---------------------------------------

Key: OVIRT-733 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-733 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: Evgheni Dereveanchin Priority: Low

I was working on node updates and troubleshooting OVIRT-630 when I came across errors like this in the logs on a freshly booted EL7 slave: {{ Sep 19 15:10:07 el7-vm16 libvirtd[1239]: libvirt version: 1.2.17, package: 13.el7_2.5 (CentOS BuildSystem <http://bugs.centos.org>, 2016-06-23-14:23:27, worker1.bsys.centos.org) Sep 19 15:10:07 el7-vm16 libvirtd[1239]: cannot open path '/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng': No such file or directory Sep 19 15:10:07 el7-vm16 libvirtd[1239]: Failed to autostart storage pool 'ovirt-node-ng': cannot open path '/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng': No such file or directory }} Looks like ovirt-node-ng_master_build-artifacts-el7-x86_64 is leaving behind storage pool configurations. Opening this to investigate further, even though I doubt it affects anything at the moment.

-- This message was sent by Atlassian JIRA (v1000.319.1#100012)