On 01/16/2016 09:23 PM, Dusty Mabe wrote:
When selecting an AMI to use in EC2 for Atomic I went to the getfedora
page and I selected `ami-f18fff9b`. I booted this AMI and I see:
-bash-4.3# rpm-ostree status
TIMESTAMP (UTC) VERSIONID OSNAME REFSPEC
* 2015-10-29 03:54:57 23 f85f5e7bfc fedora-atomic
fedora-atomic:fedora-atomic/f23/x86_64/docker-host
Shouldn't the AMIs be updated as part of 2 week atomic?
To add some more information we got reports from someone in IRC that
some of the
non-GP2 hvm images were just plain wrong or missing in some of the regions.
Can we do an audit of all of the images for Cloud Base and Vagrant and
make sure they
1 - exist in aws
2 - match what we say they are
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
