[10:32:57] <marostegui>	 I am out but why is ms1 alerting?
[11:13:52] <cezmunsta>	 marostegui: db1151 and "11:09 root@cumin1003: START - Cookbook sre.mysql.depool depool db1151: Security updates" ?
[11:14:36] <cezmunsta>	 btw ... what does that show as root rather then the user that is executing it?
[11:14:44] <cezmunsta>	 s/what/why/
[11:15:06] <federico3>	 where did it alert?
[11:16:50] <federico3>	 I see it on alertmanager, it's doing a rolling upgrade , I'll chase the alert
[11:19:53] <marostegui>	 cezmunsta: thanks
[11:20:00] <marostegui>	 federico3: its slave should've been downtimed too
[11:20:52] <cezmunsta>	 federico3: do you use sudo -i -> root instead of your name?
[11:21:37] <federico3>	 it seems the script is not aware of the topology
[11:22:01] <federico3>	 cezmunsta: no, just sudo
[11:22:48] <cezmunsta>	 Hmm when I run cookbooks I see my name 
[11:22:59] <federico3>	 these are not cookbooks
[11:23:23] <federico3>	 (not yet)
[11:33:46] <federico3>	 I'm updating the script FWIW, ms3 will alert in the meantime 
[11:36:20] <federico3>	 or actually I can stop and use the script after the fix
[13:41:46] <cezmunsta>	 "Lock for key /spicerack/locks/cookbooks/sre.mysql.major-upgrade and ID a90d3ecb-12ae-48a2-9abf-da260cb42c84 not found. Unable to release it. Was expired?" is this anything to be concerned about at the end of a reimage? 
[15:02:14] <federico3>	 odd, maybe some glitch on the host but if there's nothing sus in the logs from the actual upgrade it's most likely harmless as the lock removal on the cb is the last thing being done