This bug was fixed in the package ec2-instance-connect -
1.1.12+dfsg1-0ubuntu3~16.04.2
---
ec2-instance-connect (1.1.12+dfsg1-0ubuntu3~16.04.2) xenial; urgency=medium
* System startup now ignores failures on host key harvesting (LP:
#1915345)
-- Balint Reczey Wed, 31 Mar 2021
This bug was fixed in the package ec2-instance-connect -
1.1.12+dfsg1-0ubuntu3~18.04.2
---
ec2-instance-connect (1.1.12+dfsg1-0ubuntu3~18.04.2) bionic; urgency=medium
* System startup now ignores failures on host key harvesting (LP:
#1915345)
-- Balint Reczey Wed, 31 Mar 2021
This bug was fixed in the package ec2-instance-connect -
1.1.12+dfsg1-0ubuntu3.20.04.1
---
ec2-instance-connect (1.1.12+dfsg1-0ubuntu3.20.04.1) focal; urgency=medium
* System startup now ignores failures on host key harvesting (LP:
#1915345)
-- Balint Reczey Wed, 31 Mar 2021
This bug was fixed in the package ec2-instance-connect -
1.1.12+dfsg1-0ubuntu3.20.10.1
---
ec2-instance-connect (1.1.12+dfsg1-0ubuntu3.20.10.1) groovy; urgency=medium
* System startup now ignores failures on host key harvesting (LP:
#1915345)
-- Balint Reczey Wed, 31 Mar 2021
AWS did not respond on GitHub nor on internal channels to clarify if
they are happy with their current fix. I agree with @rcj's concern that
usability-wise the fix could be improved, but this improvement can take
place later in a separate SRU. I'm marking the bug as verification-done
because the
@rcj Thank you for testing the package. I realized that the "fix" is
just ignoring the error and noted this regression in [Where problems
could occur] section. I, possibly wrongly, assumed that this is
upstream's intention and thank you for asking for clarification
upstream.
For now I don't
I've left a comment in the upstream bug https://github.com/aws/aws-ec2
-instance-connect-config/issues/28#issuecomment-816650597 regarding my
SRU test feedback.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have tested in AWS local zone us-west-2-lax-1a
xenial:
image: ami-008b09448b998a562
build serial: 20201014
ec2-instance-connect 1.1.12+dfsg1-0ubuntu3~16.04.2
bionic:
image: ami-02701bcdc5509e57b
build serial: 20210224
ec2-instance-connect 1.1.12+dfsg1-0ubuntu3~18.04.2
focal:
image:
** Tags removed: verification-needed verification-needed-focal
verification-needed-groovy verification-needed-xenial
** Tags added: verification-failed verification-failed-focal
verification-failed-groovy verification-failed-xenial
--
You received this bug notification because you are a member
Hello Robert, or anyone else affected,
Accepted ec2-instance-connect into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/ec2
-instance-connect/1.1.12+dfsg1-0ubuntu3~16.04.2 in a few hours, and then
in the -proposed repository.
Please help us
Hello Robert, or anyone else affected,
Accepted ec2-instance-connect into groovy-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/ec2
-instance-connect/1.1.12+dfsg1-0ubuntu3.20.10.1 in a few hours, and then
in the -proposed repository.
Please help us
** Description changed:
+ [Impact]
+
+ * ec2-instance-connect breaks during host key harvesting for instances
+ launched in local zones [1] making the system boot to degraded mode
+ only.
+
+ [Test Plan]
+
+ * Start a system with the the fixed ec2-instance-connect package in a
+ local zone [1]
This bug was fixed in the package ec2-instance-connect - 1.1.14-0ubuntu1
---
ec2-instance-connect (1.1.14-0ubuntu1) hirsute; urgency=medium
* Bugfix only upload
Also contains test improvements which don't affect the package in Ubuntu.
* New upstream version 1.1.13 (LP:
13 matches
Mail list logo
