Project

General

Profile

Bug #8708

libvirt::host::network defined resource is fragile on updates

Added by intrigeri over 4 years ago. Updated about 2 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
-
Start date:
01/16/2015
Due date:
% Done:

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:
Starter:
Yes
Affected tool:

Description

When we update the source config of a libvirt::host::network defined resource, sometimes it's updated immediately in libvirt's internal active state but gets replaced by the old config later, and sometimes it's only updated on disk (/etc/libvirt/qemu/networks/${name}.xml but not in libvirt's internal active state.

In that defined resource, we're effectively managing that file in /etc with Puppet, and then (with virsh net-define) asking libvirt to read it, and then to create/update it in /etc as well. This might be racy, and be the root cause for the aforedescribed problem.

We should:

  • manage ${name}.xml with Puppet elsewhere than in /etc;
  • let libvirt be the only one that manages the corresponding network definition in /etc/libvirt/qemu/networks with net-define;
  • have the latter be subscribed to the former.

It would likely be more robust, and depend less on net-define's implementation details that may change in the future.

The code lives in https://git-tails.immerda.ch/puppet-libvirt/.


Related issues

Related to Tails - Bug #11182: Manage our VMs configuration with puppet In Progress 02/29/2016

History

#1 Updated by intrigeri about 4 years ago

  • Assignee deleted (intrigeri)

#2 Updated by sajolida about 4 years ago

  • Target version deleted (Sustainability_M1)

#3 Updated by intrigeri about 3 years ago

  • Description updated (diff)
  • Starter set to Yes

#4 Updated by kurono about 2 years ago

  • Assignee set to kurono

#5 Updated by intrigeri about 12 hours ago

  • Related to Bug #11182: Manage our VMs configuration with puppet added

Also available in: Atom PDF