From 3050554efd5f44c133c89fa6c34b9ba99f389cf5 Mon Sep 17 00:00:00 2001 From: Andreas Scheuring Date: Mon, 6 Mar 2017 17:16:57 +0100 Subject: [PATCH] guest-image-tools: Fix startup order for autoconfigure_networking.service Sometimes the autoconfigure_networking.service fails with the following errors: /lib/s390-tools/lsznet.raw: line 187: cannot create temp file for here-document: Permission denied lsznet.raw: ERROR: sysfs reported 0 CHPIDs instead of expected 8 /sbin/znetconf: line 1302: cannot create temp file for here-document: Read-only file system znetconf: Error: No configuration found for device ID 0.0.0004 This happens as the service started too early, even before the local filesystem is available. Changing the systemd startup order to start the service after the file system target is reached solves the issue. Change-Id: I90fd98ee225405d8d9d60b466a46efaa1aa6b6d8 Closes-Bug: #1670349 --- .../usr/lib/systemd/system/autoconfigure_networking.service | 1 + 1 file changed, 1 insertion(+) diff --git a/guest_image_tools/usr/lib/systemd/system/autoconfigure_networking.service b/guest_image_tools/usr/lib/systemd/system/autoconfigure_networking.service index a5a7344..ca0edc1 100644 --- a/guest_image_tools/usr/lib/systemd/system/autoconfigure_networking.service +++ b/guest_image_tools/usr/lib/systemd/system/autoconfigure_networking.service @@ -2,6 +2,7 @@ Description=Autoconfigure Network Interfaces (pre-networking) DefaultDependencies=no Before=cloud-init-local.service +After=local-fs-pre.target [Service] Type=oneshot