kushal added a new comment to an issue you are following: `` The VirtualBox backend failed to start the vms. It seems a version issue of VirtualBox, we upgraded the VirtualBox to latest, and manually tested that it is working. From tomorrow's compose we should not be having any issue. I am keeping the issue until we see everything work fine. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/182

sayanchowdhury added a new comment to an issue you are following: `` The issue is due to the new boxes that were added. They are also pushing processing the results. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/182

dustymabe added a new comment to an issue you are following: `` i.e. there were more fedmsg messages getting pushed to production than should have and this was causing issues with autocloud because it was getting extra information about builds that may or may not have existed, etc.. Thanks for the info sayan `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/182

kushal added a new comment to an issue you are following: `` Yesterday I fixed both the new boxes and got fedmsg-hub enabled on them. We are going to remove the old production hardware and move these new boxes into production. So this test was done knowingly for yesterday (still today in your timezone). We will take the box out of fedmsg till we put them back as the production servers. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/182

sayanchowdhury added a new comment to an issue you are following: `` The old boxes has been shutdown and now autocloud is showing the correct number of images. Going ahead and closing the issue. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/182