[Spce-user] [EXTERNAL] EC2 AMI network issues (Michael Prokop)

[Nogie Ekunwe]

I used the most current AMI and also the most current LTS AMI

Thanks

Sent from my iPhone

> On Feb 19, 2024, at 11:00 AM, spce-user-request at lists.sipwise.com wrote:
> 
> Send Spce-user mailing list submissions to
>    spce-user at lists.sipwise.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>    http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
> or, via email, send a message with subject or body 'help' to
>    spce-user-request at lists.sipwise.com
> 
> You can reach the person managing the list at
>    spce-user-owner at lists.sipwise.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Spce-user digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: [EXTERNAL]  EC2 AMI network issues (Michael Prokop)
>   2. Re: [EXTERNAL]  EC2 AMI network issues (Michael Prokop)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 19 Feb 2024 11:51:25 +0100
> From: Michael Prokop <mprokop at sipwise.com>
> To: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] [EXTERNAL]  EC2 AMI network issues
> Message-ID: <2024-02-19T11-46-42 at devnull.michael-prokop.at>
> Content-Type: text/plain; charset=us-ascii
> 
> Hi,
> 
> * Edo [Sat Feb 17, 2024 at 03:22:35AM -0600]:
> 
>> I have initiated EC2 instances (2) and discovered that the sipwise ami (
>> ami-06ef81cd274aafae9
>> <https://eu-west-1.console.aws.amazon.com/ec2/home?region=eu-west-1#ImageDetails:imageId=ami-06ef81cd274aafae9>)
>> does not start or configure the network card when used to start an ec2
>> instance. I tried 2 sipwise ami's, both have the same symptom. Am I missing
>> something?
>> 
>> attached is a snapshot of the logs from the ec2 showing that the enX0 did
>> not start.
> 
> Thanks for reporting, we'll try to reproduce and look into this.
> JFTR, which instance type did you use?
> 
> regards
> -mika-
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Mon, 19 Feb 2024 13:09:38 +0100
> From: Michael Prokop <mprokop at sipwise.com>
> To: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] [EXTERNAL]  EC2 AMI network issues
> Message-ID: <2024-02-19T13-06-11 at devnull.michael-prokop.at>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi,
> 
> * Edo [Sat Feb 17, 2024 at 03:22:35AM -0600]:
> 
>> I have initiated EC2 instances (2) and discovered that the sipwise ami (
>> ami-06ef81cd274aafae9
>> <https://eu-west-1.console.aws.amazon.com/ec2/home?region=eu-west-1#ImageDetails:imageId=ami-06ef81cd274aafae9>)
>> does not start or configure the network card when used to start an ec2
>> instance. I tried 2 sipwise ami's, both have the same symptom. Am I missing
>> something?
> [...]
> 
> Confirmed and reproduced already, and the underlying issue has been
> identified (networking change in bookworm). We'll look into it...
> 
> regards
> -mika-
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 833 bytes
> Desc: not available
> URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20240219/e57ae524/attachment-0001.asc>
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
> 
> 
> ------------------------------
> 
> End of Spce-user Digest, Vol 56, Issue 4
> ****************************************