Thanks, this is now pushed. Can someone run the groups/resultsdb.yml playbook ? On Wed, 24 Apr 2019 at 11:04, Stephen John Smoogen <smooge@xxxxxxxxx> wrote: > > > > On Wed, 24 Apr 2019 at 02:48, Clement Verna <cverna@xxxxxxxxxxxxxxxxx> wrote: >> >> Hi all, >> >> Currently resultsdb in production is not configured properly to send >> messages using fedora-messaging which in turns causes greenwave to not >> send messages (greenwaves publishes messages when it receives new >> results). >> >> The attached patch makes sure that we create the fedora-messaging in >> production and not only in staging. >> >> This should be fixing https://pagure.io/fedora-infrastructure/issue/7735 >> >> +1s ? > > > I have reviewed +1 > >> >> _______________________________________________ >> infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > > > > -- > Stephen J Smoogen. > > _______________________________________________ > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
