Package: cloud.debian.org
Severity: important
Hi,
I tried to launch in instance from the latest stretch ami (ami-772ab761 i.e.
us-east-1) into a VPC. It failed - more specifically networking.service failed.
Here's the relevant output from syslog:
[ [0;1;31mFAILED [0m] Failed to start Raise network interfaces.
See 'systemctl status networking.service' for details.
Starting Initial cloud-init job (metadata service crawler)...
[ [0;32m OK [0m] Reached target Network.
[ 9.288945] cloud-init[390]: Cloud-init v. 0.7.9 running 'init' at Mon, 22
May 2017 09:14:57 +0000. Up 9.19 seconds.
[ 9.294365] cloud-init[390]: ci-info: +++++++++++++++++++++++++++Net device
info++++++++++++++++++++++++++++
[ 9.299149] cloud-init[390]: ci-info:
+--------+-------+-----------+-----------+-------+-------------------+
[ 9.303735] cloud-init[390]: ci-info: | Device | Up | Address | Mask
| Scope | Hw-Address |
[ 9.308328] cloud-init[390]: ci-info:
+--------+-------+-----------+-----------+-------+-------------------+
[ 9.312879] cloud-init[390]: ci-info: | ens3: | False | . | .
| . | 0e:3d:ec:0d:c9:56 |
[ 9.317451] cloud-init[390]: ci-info: | lo: | True | 127.0.0.1 |
255.0.0.0 | . | . |
[ 9.321656] cloud-init[390]: ci-info: | lo: | True | . | .
| d | . |
[ 9.325631] cloud-init[390]: ci-info:
+--------+-------+-----------+-----------+-------+-------------------+
I guess networking was looking for eth0 but systemd knew better (i.e. ens3).
Can't provide any more details since I couldn't access the instance :-) .
This is easy to reproduce. Launch a t2.micro from the ami, specify a VPC
(create if necessary), enable public IP and launch. Try to ssh into the
instance.
This may be related to Bug#745587
(https://lists.debian.org/debian-cloud/2017/04/msg00017.html).
In any case, not being able to launch into a VPC seems pretty severe, all
things considered.
