#33 Send compose check reports for Atomic installer ISO to Mike McGrath and the cloud list if anything fails
Closed: Fixed None Opened 8 years ago by acarter.

Like this - http://fpaste.org/312109/53148673/

Send to - mmcgrath@redhat.com; cloud@lists.fedoraproject.org

Send when: only when there are one or more failures if that option is available

This notification will serve the purpose of alerting owners of problems so they can be fixed before we get to the release cycle


For the record, this is actually a request for check-compose, which lives in the fedora-qa git repo, but we don't have a project that covers that repo, so I asked acarter to file here. I will take care of this.

check-compose doesn't have a 'send report only on failure' mode ATM, but I can add it easily. To do this cleanly I'll also have to allow the config file to specify different emails for different types of report...

also note, for the record, that while openQA only tests the Atomic installer ISO, check-compose does a bit more than that. check-compose also does the 'expected images' bit. The current list of 'expected images' for a Postrelease milestone (which is what I call the post-release nightly composes, that currently contain only Cloud images, in fedfind lingo) is:

cloud disk raw x86_64
cloud vagrant libvirt x86_64
cloud vagrant virtualbox x86_64
cloud docker x86_64
cloud_atomic canned x86_64

canned is the installer image. The idea of the 'expected images' check is not necessarily to list absolutely every image that would appear in a complete compose, but just to list the ones that we really care about. It's entirely meant as an aid to humans, so this list should be whatever the people who look after the composes want it to be; if you want any changes, just ask.

OK, I believe this is all in place now - I had to make it possible to set different options per milestone in check-compose and also add an 'only send email on failure' mode, add a postrelease timer, and poke the ansible infra bits so that everything's configured appropriately. I ran the service manually for 2016-01-19 as a quick test and I think it worked properly, but I think the email to cloud@ is stuck in moderation, someone will need to allow mails from rawhide@fp.o (which is the address I have compose check emails set to come from).

Will close this once we're sure it's all working properly and I didn't break the Rawhide reports either.

mmcgrath confirms he's getting his copies, but the ones being sent to cloud@lists.fp.o do not seem to be getting through, still. No-one has responded to my requests to check the list configuration yet. :/

Well I'm sending out the mails, so there ain't a lot more I can do here.

Login to comment on this ticket.

Metadata