[Pkg-libvirt-maintainers] Bug#775514: No networking running virt-builder scripts after upgrading from 1.26 to 1.28

[Richard W.M. Jones]

On Tue, Jun 30, 2015 at 09:46:31AM +0200, Hilko Bengen wrote:
> > (2) The second problem is that we run 'dhclient', but for some reason
> > this command cannot acquire an IP address unless you name a specific
> > interface (eg 'dhclient eth0').  This was already reported for Ubuntu:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1224795
> >
> > The workaround is just this patch (to appliance/init):
> >
> > -      dhclient
> > +      dhclient eth0
> 
> Can we assume that the network name is always "eth0"? In that case, I'd
> simply apply that patch.

Correct -- that is the problem that stops me from just adding that
patch upstream.  I guess that different kernel versions, and
particularly, different versions of udev rules, could cause that
interface to have a different name.

`dhclient eth0' seems to work for Debian and Ubuntu.  Even if it
doesn't work, it won't make things worse than they are now.

For upstream, I intend to investigate why `dhclient' alone doesn't
work (it works fine on Fedora).

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW