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
This commit is contained in:
Andreas Scheuring 2017-03-06 17:16:57 +01:00
parent 3c02543ea8
commit 3050554efd
1 changed files with 1 additions and 0 deletions

View File

@ -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