[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
Hi Thorsten, thanks for your report. I discussed that with cloud-init team, and we're not clear about the steps you're doing to observe the issue. It's an interesting problem, so we'd like to ask you to report a new bug against cloud-init, with the following information: 1) The most detailed steps you can provide in order we can reproduce the issue, specially detailed information about the changes/configs you're doing with NICs. 2) A tarball created by running the command "cloud-init collect-logs" after you have reproduced the issue. Please comment here with the number of the new LP, we'll follow from there. Thanks in advance, Guilherme -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
The same problem also happens in EC2-VPC mode if the network interface changes. This happens if you create a custom AMI, e.g. using Packer, from the official Ubuntu 18.04 LTS AMI. The first start by packer writes the MAC address into /etc/netplan/50-cloud-init.yaml which gets part of the custom AMI. If you then try to launch an instance from that AMI it gets a new network interface with a new MAC address and the instance will not have any internet connection. I tries to call "cloud-init clean" at the end of the packer build but that didn't have any positive effect. It seems the current approach is kind of broken in general. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
Problem is resolved in Bionic's latest version of cloud-init, released yesterday: $ dpkg -l | grep cloud-init ii cloud-init 18.5-45-g3554ffe8-0ubuntu1~18.04.1 I've manually upgraded the package after bringing-up my EC2 Classic instance, so notice the AWS image doesn't have the latest cloud-init version yet. Thanks, Guilherme ** Changed in: cloud-init (Ubuntu Bionic) Status: Confirmed => Fix Released ** Changed in: cloud-init (Ubuntu Xenial) Status: Confirmed => Fix Released ** Changed in: cloud-init (Ubuntu Cosmic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
SRU release status LP: https://bugs.launchpad.net/ubuntu/+source/cloud- init/+bug/1819067 Thanks Odd_Bloke, for the pointer! ** Changed in: cloud-init (Ubuntu Bionic) Importance: Undecided => High ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: cloud-init (Ubuntu Cosmic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
This bug was fixed in the package cloud-init - 18.5-45-g3554ffe8-0ubuntu1 --- cloud-init (18.5-45-g3554ffe8-0ubuntu1) disco; urgency=medium * New upstream snapshot. - cloud-init-per: POSIX sh does not support string subst, use sed (LP: #1819222) -- Daniel Watkins Fri, 08 Mar 2019 17:42:34 -0500 ** Changed in: cloud-init (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cloud-init (Ubuntu Cosmic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cloud-init (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cloud-init (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
** Changed in: cloud-init (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
This bug is fixed with commit 0bb4c74e to cloud-init on branch master. To view that commit see the following URL: https://git.launchpad.net/cloud-init/commit/?id=0bb4c74e -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
** Merge proposal linked: https://code.launchpad.net/~gpiccoli/cloud-init/+git/cloud-init/+merge/363154 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
** Merge proposal linked: https://code.launchpad.net/~gpiccoli/cloud-init/+git/cloud-init/+merge/362749 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
Hi, Yes probably the regeneration on every boot is better, but without understanding the internals it was easier for me to manually patch and remove those from config than trying to figure out how to get it to be regenerated every boot. Because wanted to patch manually couple of instances before putting them into use. Now just don't update them, before this is fixed :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
Thank you very much Jani Ollikainen for the great bug report, with instructions on how to reproduce and even more - you basically investigated the issue and figured it out yourself. I'll discuss internally if the best option is to have cloud-init to generate the netplan file in all boots (which I think makes sense) or if we shouldn't have that "mac match" block. Cheers, Guilherme ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => High ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
same problem here! [ 12.935611] cloud-init[640]: Cloud-init v. 18.3-9-g2e62cb8a-0ubuntu1~18.04.2 running 'init' at Mon, 21 Jan 2019 07:38:47 +. Up 12.29 seconds. [ 12.958782] cloud-init[640]: ci-info: +++Net device info [ 12.965639] cloud-init[640]: ci-info: ++---+---+---+---+---+ [ 12.980218] cloud-init[640]: ci-info: | Device | Up | Address |Mask | Scope | Hw-Address| [ 12.992808] cloud-init[640]: ci-info: ++---+---+---+---+---+ [ 13.015538] cloud-init[640]: ci-info: | eth0 | False | . | . | . | 22:00:0b:2c:9a:2b | [ 13.022671] cloud-init[640]: ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . | [ 13.036164] cloud-init[640]: ci-info: | lo | True | ::1/128 | . | host | . | [ 13.048743] cloud-init[640]: ci-info: ++---+---+---+---+---+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
** Summary changed: - No network in AWS (EC-Classic) after stopping and starging instance + No network in AWS (EC-Classic) after stopping and starting instance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
