dustymabe reported a new issue against the project: `atomic-wg` that you are following: ``
we hit [an issue](https://pagure.io/releng/issue/6761) yesterday because fedimg failed upload all of our AMIs for that day's build of FAH.
This is most likely due to the fact that we use a builder instance to pull the cloud disk image and then create the EBS. Bringing up the builder instance can fail (commodity hardware in EC2) and thus can lead to situations like this. It would be much better if we don't use a builder instance.
This is being worked on in https://github.com/fedora-infra/fedimg/issues/42.
This ticket will track that work that is 'two weeks away' from completion. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/269
The issue: `fedimg: don't use 'builder' instance for uploading AMIs` of project: `atomic-wg` has been assigned to `sayanchowdhury` by dustymabe.
sayanchowdhury added a new comment to an issue you are following: `` I have been testing autocloudreporter (it's working fine), but have hit a issue where I need to make some minor changes to resultdb_conventions.
I need to add a class that would be handling the messages for AMIs. Right now, The [FedoraImageResult](https://pagure.io/taskotron/resultsdb_conventions/blob/master/f/resultsdb_co...) handles the autocloud compose test messages. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/269
dustymabe added a new comment to an issue you are following: `` @sayanchowdhury is still working on the snapshots being public issue - will continue work on this after that is resolved. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/269
-
Dusty Mabe -
Sayan Chowdhury