amazon-ec2-net-utils 2.4.1-1 released

[Mitchell Dzurick]

This bug tracks an update to the amazon-ec2-net-utils packages in the following ubuntu releases to the versions below:

* Mantic (23.10) : 2.4.1-1ubuntu0.23.10.1
* Lunar (23.04) : 2.4.1-1ubuntu0.23.04.1

These updates do not have an SRU policy exception yet, but an exception is currently being proposed. In the meantime, a one-time exception is requested for this change.

### UPSTREAM CHANGES ###

The upstream commits between 2.3.0 and 2.4.1 are:

b721f41 (HEAD -> main, tag: v2.4.1, origin/main, origin/HEAD) Release version 2.4.1
7d61595 Don't install rules for the primary interface
66a33f0 (tag: v2.4.0) Release 2.4.0
31c9589 Fix directory ownership in spec file
0a57c62 Route configuration simplification
05f1d16 Preserve the original value of the errexit shell option
f15e9da Wait for device-number propagation to IMDS
b3c7d03 Fix a process synchronization issue during ENI removal
eb5d784 Add scratch-rpm makefile target
c71ae5d Fix shellcheck SC2320 warning
dc1f1e9 Update GitHub Actions config to reflect AL2023 rebrand
6140feb Refresh README and CONTRIBUTING
edc076e Add documentation for setup-policy-routes
57cc0e5 (tag: v2.3.0) Bump version to 2.3.0 in GNUMakefile and package metadata

Out of these commits, the following are important functional changes

7d61595 Don't install rules for the primary interface
  * Fixes https://github.com/amazonlinux/amazon-ec2-net-utils/issues/97
0a57c62 Route configuration simplification
  * This says simplification, but actually fixes the routes, without this patch, the routes are incorrect and networking will not work.
f15e9da Wait for device-number propagation to IMDS
  * fixes https://github.com/amazonlinux/amazon-ec2-net-utils/issues/90
b3c7d03 Fix a process synchronization issue during ENI removal

### DEBIAN ###

The debian package 2.4.1-1 also has some important changes unique to debian

The commits between 2.3.0-2 and 2.4.1-1 are:

73ad81e (HEAD -> master, tag: debian/2.4.1-1, origin/master) Add systemd-resolved to Recommends and update postinst
491c46d Release 2.4.1-1 to unstable
0a015ed Update changelog
b3c94c9 Revert "Don't provide a postinst file"
8baf4ac Merge tag 'upstream/2.4.1'
b721f41 (tag: upstream/2.4.1, origin/upstream) Release version 2.4.1
7d61595 Don't install rules for the primary interface
6fbe179 Release 2.4.0-1 to unstable
7b437dd Merge tag 'upstream/2.4.0'
ae77856 debian/watch: correct upstream url
66a33f0 (tag: v2.4.0, tag: upstream/2.4.0) Release 2.4.0
31c9589 Fix directory ownership in spec file
0a57c62 Route configuration simplification
05f1d16 Preserve the original value of the errexit shell option
f15e9da Wait for device-number propagation to IMDS
b3c7d03 Fix a process synchronization issue during ENI removal
eb5d784 Add scratch-rpm makefile target
c71ae5d Fix shellcheck SC2320 warning
ce67e64 (tag: debian/2.3.0-3) Install systemd services to /lib/systemd/system
dc1f1e9 Update GitHub Actions config to reflect AL2023 rebrand
6140feb Refresh README and CONTRIBUTING
edc076e Add documentation for setup-policy-routes
f9a4c36 (tag: debian/2.3.0-2) Set Maintainer to the cloud team and add myself to Uploaders

Out of these commits, these are important or functional changes:

b3c94c9 Revert "Don't provide a postinst file"
  * This is a fix we requested, so that reboots are not required after installation

[ Test Plan ]
This is a complicated package to test, but 3 tests will be performed:

1. E2E testing with https://github.com/canonical/server-test-scripts/tree/main/cpc/aws/amazon-ec2-net-utils

2. On installation, instance is ssh accessible

3. On upgrade (from previous package), instance is ssh accessible

(2) and (3) are important to ensure that the debian/postinst does not break the networking and leave the system in a state that can not be accessed.

[ Regresion Potential ]
amazon-ec2-net-utils is a package in universe, and is strictly optional. At the moment, it is meant to be exclusively used on AWS instances where network interfaces can be hotplugged.

This package inherently causes concerns as it will modify the networking on the system, and that always is a thing to be concerned of.

On installation, this package will attempt to configure networking, which could have issues in certain configurations which leave the system in a state that is not accessible via ssh. In this case, users would have to connect to the AWS instance through the AWS console.

[Mitchell Dzurick (mitchdz)]

Setting to Invalid because there is active work in upstream that we should wait for.