similar to: [PATCH v2] appliance init: find NIC name for dhcpcd

Here are two patches: one fixes the gpg-agent causing unmount to fail after running dnf to install packages. The other ones fixes dhcpcd call in the init program to provide it an interface name. Cédric Bosdonnat (2): appliance init: find NIC name for dhcpcd Make sure gpg-agent is terminated before umount appliance/init | 3 ++- customize/customize_run.ml | 3 ++- 2 files

dhcpcd requires an interface name as parameter to work. We are now getting it from /proc/sys/net/ipv4/conf/ folder children. --- appliance/init | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/appliance/init b/appliance/init index cca62e7..ef18959 100755 --- a/appliance/init +++ b/appliance/init @@ -111,7 +111,8 @@ if test "$guestfs_network" = 1; then if

On Thu, Oct 02, Richard W.M. Jones wrote: > The script won't fail, but the network won't work. What's the > alternative on SuSE? I think that would be dhcpcd, which is also used by NetworkManager. Olaf

On Thu, Oct 02, Richard W.M. Jones wrote: > +if grep -sq guestfs_network=1 /proc/cmdline; then > + dhclient > +fi dhclient will be missing at least in openSUSE. Not an issue now, does the script fail if the command fails to execute due to ENOENT? Olaf

Hi, ran into a problem w/ linode hosted VM where IPv6 address changed after they migrated it to a different host. They claim I can fix it with sed -i 's/slaac private/slaac hwaddr/' /etc/dhcpcd.conf However there appears to be no dhcpcd.conf on any of my CentOS 7 systems. What is the CentOS 7 equivalent?

Workaround for Ubuntu which uses this script to try to start a systemd service. That won't work because systemd is not used inside the appliance. See: https://bugs.launchpad.net/ubuntu/+source/supermin/+bug/1824236 Thanks: Ioanna Alifieraki --- appliance/init | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/appliance/init b/appliance/init index 4f2b55822..b1c4d09ea

v3: - Various changes to dhclient/dhcpcd as discussed on the mailing list.

On Thu, Oct 02, 2014 at 01:53:45PM +0200, Olaf Hering wrote: > On Thu, Oct 02, Richard W.M. Jones wrote: > > > The script won't fail, but the network won't work. What's the > > alternative on SuSE? > > I think that would be dhcpcd, which is also used by NetworkManager. It turns out we don't package dhcpcd in Fedora. If we did the following, would it

Sadly, the dhclient-script shipped as part of isc-dhcp-client in Ubuntu unconditionally reads from /etc/fstab without checking for its existence. Since no package holds /etc/fstab, this file will not exist in the appliance, cause dhclient to fail (actually keep looping calling the failing dhclient-script) when the network is requested. As a workaround, touch /etc/fstab just before enabling the

On Thu, Oct 02, Richard W.M. Jones wrote: > It seems as if it would, from reading the dhcpcd man page .. Looks like the syntax is 'dhcpcd <interface>'. Olaf

On 03/13/2015 12:21 PM, Richard W.M. Jones wrote: > So what's happening is that /etc/resolv.conf in the appliance never > gets created. > Is the /dev/tcp test by IP evidence that the problem goes deeper than name resolution? > Run `./run virt-rescue --network --scratch' on the Ubuntu host and see if: > > - either dhclient or dhcpcd exists in the appliance > >

Yeah, it's definitely an issue with dhclient. I patched the init script to use dhcpcd instead and everything is working as expected now. I've attached a log containing the strace of dhclient if that helps you or someone else in the future. Thanks for all your help Rich. Shawn On Tue, Jun 30, 2015 at 9:53 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Tue, Jun 30, 2015

Hello guys, we use libguests for dynamic creation of our VM and we do various modifications of those VMs in the process. One with I am struggling with is to signing keys of our custom repository - " vm.sh("wget -O - " + key_address + " | apt-key add -")" where "vm" is a GuestFS object. So I have set "vm.set_network(True)" and I have installed

Hi Rich, I set LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1 when calling virt-builder, and here is the log: [ 0.1] Downloading: file:///home/myan/work/libguestfs/builder/website/ubuntu-14.04.xz [ 1.4] Planning how to build this image [ 1.4] Uncompressing [ 4.4] Opening the new disk libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: trace: set_tmpdir

Read the content of /proc/cmdline using bash features, and use its [[ ... ]] expression to find texts in a variable. This shaves off 5 grep invocations. --- appliance/init | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/appliance/init b/appliance/init index f6fe9b9..8d662fa 100755 --- a/appliance/init +++ b/appliance/init @@ -75,7 +75,9 @@ $UDEVD --daemon

Package: logcheck Severity: wishlist I'm attaching rules suggestions for dhcpcd as a git patch, and also a sample from my logs. Please review the patch (I can fix any issues with it) and include in logcheck if you like it. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 0001-Added-rules-for-dhcpcd.patch URL:

On 03/13/2015 11:13 AM, Richard W.M. Jones wrote: > > Yes, the log indicates name resolution not working. Please try the > diagnosis steps that I outlined in: > > https://www.redhat.com/archives/libguestfs/2015-March/msg00075.html Sorry, I somehow missed the above message. $ ./run guestfish get-backend direct Here are the outputs of the /dev/tcp test, first doing: $ ./run

I had tried this approach, to add /etc/dhcp/dhclient-enter-hooks.d/resolved to excludefiles, however it didn't work. As far as I know, this hook is included in the base image and according to [1], the current implementation does not apply excludefiles to the base image. Jo [1] https://github.com/libguestfs/supermin/blob/b2401285cd3e3d42006fc164ef1f046cc35a50c4/src/mode_build.ml#L137 On

does the IPAPPEND option still exist? If so I want clearification on it please. Out of the syslinux documentation it says the following. The flag_val is an OR of the following options: 1: indicates that an option of the following format should be generated and added to the kernel command line: ip=client-ip:boot-server-ip:gw-ip:netmask ... based on the input from the DHCP/BOOTP or PXE boot

Hello, I''m using shorewall-4.5.16 with centos5. The dhclient stores the lease information on the /var/lib/dhclient/dhclient-<DEVICE>.leases file. The /var/lib/shorewall/firewall script has the function detect_dynamic_gateway that detects the gateway based on the leases file. The code in the function is: detect_dynamic_gateway() { # $1 = interface local interface