Processing control commands:
> tags -1 + pending
Bug #964596 [cloud.debian.org] cloud.debian.org: Debian 10 EC2: IPv4 address
suddenly flushed
Added tag(s) pending.
--
964596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tags -1 + pending
> I think it's reasonable to add a check in
> /usr/local/sbin/inet6-ifup-helper for future revisions of the stretch
> AMI to exit successfully if IPv6 is disabled on $IFACE.
We recently merged some changes that will do this on newly launched
instances. It won't help
On Thu, Jul 09, 2020 at 12:09:44PM +0200, Martin Olsson wrote:
>Severity: major
JFYI, "major" is not a valid severity. The complete list of severities
is listed at https://www.debian.org/Bugs/Developer#severities In the
case of this bug, since the behavior is only triggered by customization
Package: cloud.debian.org
Severity: major
User: cloud.debian@packages.debian.org
Usertags: aws
Problem:
Production systems in AWS lose all network connectivity after 1h, after a
dist-upgrade from Debian 9 to Debian 10 has been performed.
One can't ssh in to investigate and no remote console
