Your message dated Wed, 21 Jun 2017 08:43:10 -0700
with message-id <[email protected]>
and subject line Re: Bug#863385: Possible solution
has caused the Debian Bug report #863385,
regarding cloud.debian.org: Latest stretch AMI (ami-772ab761) fails to launch
successfully into VPCs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
863385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863385
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
On Tue, Jun 06, 2017 at 09:32:50PM +0100, kuLa wrote:
> Conversations on IRC and on [email protected] almost allow us to draw the
> conclusion that for Stretch images we should add 'net.ifnames=0' to the grub
> kernel parameters.
>
> It's going to be divergence from default Debian image but we need it, so
> adding
> it and documenting it on wiki seams to be a reasonable resolution.
>
> But if people know betters solution I'm keen to learn it.
I've made this change in
https://anonscm.debian.org/cgit/cloud/fai-cloud-images.git/commit/?id=47e7b9622c6c573644139020842c48de71d077f8
The strech release images documented at
https://wiki.debian.org/Cloud/AmazonEC2Image/Stretch contain this fix,
so please test and verify that things work for you. When I test on an
r4.large instance, this is what I see:
admin@ip-172-20-0-73:~$ sudo dmesg | grep command
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-amd64
root=UUID=4289eaca-a1d3-4971-94c5-708335e0b693 ro quiet elevator=noop
console=tty console=ttyS0 net.ifnames=0
admin@ip-172-20-0-73:~$ ls /sys/class/net/eth0/device/driver -l
lrwxrwxrwx 1 root root 0 Jun 21 15:03 /sys/class/net/eth0/device/driver ->
../../../bus/pci/drivers/ena
noah
signature.asc
Description: PGP signature
--- End Message ---
