NetBSD Problem Report #54982

From jschauma@netmeister.org  Tue Feb 18 20:47:20 2020
Return-Path: <jschauma@netmeister.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id A8CD81A9213
	for <gnats-bugs@gnats.NetBSD.org>; Tue, 18 Feb 2020 20:47:20 +0000 (UTC)
Message-Id: <20200218204717.8EAB18533F@panix.netmeister.org>
Date: Tue, 18 Feb 2020 15:47:17 -0500 (EST)
From: jschauma@netmeister.org
Reply-To: jschauma@netmeister.org
To: gnats-bugs@NetBSD.org
Subject: several AWS AMIs are missing
X-Send-Pr-Version: 3.95

>Number:         54982
>Category:       misc
>Synopsis:       several AWS AMIs listed on the website are missing
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    misc-bug-people
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Tue Feb 18 20:50:00 +0000 2020
>Originator:     Jan Schaumann
>Release:        NetBSD 8.0
>Organization:

>Environment:


System: NetBSD panix.netmeister.org 8.0 NetBSD 8.0 (PANIX-VC) #0: Fri May 3 16:47:37 EDT 2019 root@juggler.panix.com:/misc/obj64/misc/devel/netbsd/8.0/src/sys/arch/amd64/compile/PANIX-VC amd64
Architecture: x86_64
Machine: amd64
>Description:

https://wiki.netbsd.org/amazon_ec2/amis/ lists a nunmber of NetBSD AMIs by
region.  However, it appears that several of the listed AMIs do not actually
exist.  The following AMIs appear to not be available:

ami-ab5a4fee
ami-c62d81b1
ami-6e98be3c
ami-c3402df9
ami-7decda7c
ami-5fa61242
ami-415a4f04
ami-f253ff85
ami-989bbdca
ami-63402d59
ami-51e2d450
ami-f1a511ec
ami-32e6f45e
ami-c8ea2bab
ami-8a89d0e9
ami-51d0553d
ami-62249c0a
ami-7945503c
ami-302e8247
ami-3498be66
ami-1d432e27
ami-b7eadcb6
ami-73a6126e
ami-b618a0de
ami-3d5a4f78
ami-aa2c80dd
ami-5a98be08
ami-fd402dc7
ami-3befd93a
ami-07a6121a
ami-4af33229
ami-2bd15447

This makes it difficult to get new users to try out NetBSD in AWS; intermittent failures
like this easily lead to an impression of "NetBSD is broken" and users will move on to
another OS.

>How-To-Repeat:

aws ec2 describe-images --image-id ami-ab5a4fee --region us-west-1

>Fix:

Build and upload images, then update the wiki with the correct IDs.  Automate this
process to ensure new images are published during release builds and information
pushed to the website with the OS release.

>Unformatted:

Home	PR Database Search