I deployed Bodhi 4.0.0 to production today, which no longer uses fedmsg. I think I dropped the nagios stuff from Ansible, but I am not 100% sure, and also I cannot run that playbook. Also, maybe running the playbook isn't enough since Ansible doesn't notice things that were added in the past?
In any case, I will need assistance from an admin to clean up the old nagios checks so it does not alert for fedmsg anymore.
Metadata Update from @smooge: - Issue assigned to smooge
Note: In https://pagure.io/fedora-infrastructure/issue/7848 I noted that there is a thing called tag2distrepo that was also running on backend02. I learned that it is a fedmsg consumer:
https://pagure.io/releng/tag2distrepo/blob/master/f/tag2distrepo/__init__.py
So I guess we might want to keep that monitoring around, though I don't know if we will keep backend02 around or not (might move it to a different host).
All that to say, it might be good to coordinate with whoever works on #7848.
I filed https://pagure.io/fedora-infrastructure/issue/7849 about tag2distrepo.
I found one other stray nagios check that I removed in ansible but someone may need to manually remove from the nagios server: https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/roles?id=2843dd842284766d896cc22b5c9d91f91f62de25
#7849 is fixed now.
This has been removed from nagios and is no longer alerting
Metadata Update from @smooge: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.