1562061 - Remove MIG agents from RelEng infrastructure

Status: RESOLVED FIXED

(Infrastructure & Operations :: RelOps: Puppet, task)

Description

[Arcadia Rose [OOO until Sept. 21]]

EIS intends to officially end support for the Mozilla InvestiGator project in July and would like to start by asking everyone to remove MIG Agents from their infrastructure. We will be waiting to turn off MIG's own backend infrastructure until after agents are pulled down to avoid causing breakage but ask that this be taken care of at your earliest convenience.

Please feel free to follow up with any questions.

Comment 1

[Jake Watkins [:dividehex]]

Attachment: GitHub Pull Request

Comment 2

[Jake Watkins [:dividehex]]

Hi Emma, I've pushed out a puppet change that should disable and remove mig from all Releng hosts. Do you have a way of seeing incoming connections to the mig API to help us track down any hosts that might still be running mig-agent? I feel confident this should catch all the hosts but I want to make sure we don't miss anything before the API is shutdown.

Thanks!

Comment 3

[Jake Watkins [:dividehex]]

Attachment: GitHub Pull Request

Fixes this:
Fri Jul 12 15:40:28 +0000 2019 Puppet (err): /bin/kill -9 $(/usr/local/bin/mig-agent -q=pid) returned 1 instead of one of [0]
Fri Jul 12 15:40:28 +0000 2019 /Stage[main]/Mig::Agent::Disable/Exec[kill mig]/returns (err): change from notrun to 0 failed: /bin/kill -9 $(/usr/local/bin/mig-agent -q=pid) returned 1 instead of one of [0]

Comment 4

[Arcadia Rose [OOO until Sept. 21]]

Hi Jake, I think everything is good on your end. We'll be bringing MIG's backend infrastructure down this week and will let you know if we find anything still running. From a quick look, it looks like we aren't seeing anything from RelEng's agents.

Comment 5

[Jake Watkins [:dividehex]]

Attachment: GitHub Pull Request - completely remove mig module from puppet