netcf does not seem to handle "source-directory" directive in /etc/network/interfaces

Bug #1273719 reported by Clark Laughlin on 2014-01-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
augeas (Ubuntu)
High
Unassigned
netcf (Ubuntu)
High
Unassigned

Bug Description

While doing some libvirt tests, I experienced errors executing any iface-* commands. After debugging, I found that libvirt uses netcf for these operations. I tracked the problem down to a "source-directory" line in my /etc/network/interfaces file. Once I removed that line, all the libvirt operations that relied on netcf seemed to work correctly.

I am not sure what the specific package version is -- it was used to build libvirt from upstream sources. The build occurred on a saucy system.

Thanks for reporting this bug. I believe the support needs to be
provided through the augeas interfaces.aug lens. I suspect that
netcf will get the support for free when that happens, though I
could be wrong.

 affects: ubuntu/netcf
 status: confirmed
 importance: high
 affects: ubuntu/augeas
 status: confirmed
 importance: high

Changed in netcf (Ubuntu):
importance: Undecided → High
status: New → Confirmed
Clark Laughlin (clark-laughlin) wrote :

I looked and saw that augeas seems to be getting an update in trusty to support the "source" stanza:

https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1270881

Is "source" the correct stanza to use, and not "source-directory"?

Not quite. As 'man 5 interfaces' shows, source sources a file, while
source-directory sources all files in a directory. Hopefully the fix
for this can be as simple as the source fix.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers