ReleaseEngineering/How To/Process release email: Difference between revisions

Jump to navigation Jump to search
m
spelling nazi woz here
m (spelling nazi woz here)
Line 48: Line 48:
It pulls the list of hosts to check from http://build.mozilla.org/builds/slaves_needing_reboot.txt
It pulls the list of hosts to check from http://build.mozilla.org/builds/slaves_needing_reboot.txt


== What to do when one is recieved ==
== What to do when one is received ==
not sure yet, unless your buildduty - then you should be watching it
not sure yet, unless your buildduty - then you should be watching it


Line 66: Line 66:
The code for this script is stored [https://github.com/jhford/monitor-puppet here]
The code for this script is stored [https://github.com/jhford/monitor-puppet here]


== What to do when one is recieved ==
== What to do when one is received ==
* if the title contains "[puppet-monitoring][master_name] <slavename> is waiting to be signed", this is for information and requires no immediate action
* if the title contains "[puppet-monitoring][master_name] <slavename> is waiting to be signed", this is for information and requires no immediate action
* if the title contains "[puppet-monitoring][master_name] <slavename> has invalid cert", the script will try once to clean the cert before sending the email once there is a waiting signing request.  If this is successful, you'll see a matching "<slavename> is waiting to be signed" email.  The key will be automatically signed by a cronjob
* if the title contains "[puppet-monitoring][master_name] <slavename> has invalid cert", the script will try once to clean the cert before sending the email once there is a waiting signing request.  If this is successful, you'll see a matching "<slavename> is waiting to be signed" email.  The key will be automatically signed by a cronjob
Line 89: Line 89:
  scl-production-puppet:/N/production/darwin10-i386/test/usr/local/bin/run-puppet.sh  
  scl-production-puppet:/N/production/darwin10-i386/test/usr/local/bin/run-puppet.sh  


== What to do when one is recieved ==
== What to do when one is received ==
* either ignore the email or find the root of the problem and fix it.   
* either ignore the email or find the root of the problem and fix it.   


Line 108: Line 108:
Since this is a "catch all" category, various tools send them. Check the full headers for information on sender and source machine as needed.
Since this is a "catch all" category, various tools send them. Check the full headers for information on sender and source machine as needed.


== What to do when one is recieved ==
== What to do when one is received ==
If you don't know what it's about, you don't need to deal with it beyond setting up a filter to ignore it.
If you don't know what it's about, you don't need to deal with it beyond setting up a filter to ignore it.


Line 161: Line 161:
Include a link to the source of the program sending the email.  Include information on which hosts are sending the email, and give information on how program runs.  Is it a daemon?  Does it have an init script?  Do you run it under screen?   
Include a link to the source of the program sending the email.  Include information on which hosts are sending the email, and give information on how program runs.  Is it a daemon?  Does it have an init script?  Do you run it under screen?   


== What to do when one is recieved ==
== What to do when one is received ==
* if the title contains "[scl-production-puppet-new] <slavename> is waiting to be signed", this is for information and requires no immediate action
* if the title contains "[scl-production-puppet-new] <slavename> is waiting to be signed", this is for information and requires no immediate action
* if the title contains "[scl-production-puppet-new] <slavename> has invalid cert", the script will try once to clean the cert before sending the email.  If this is successful, you'll see a matching "<slavename> is waiting to be signed" email.  The key will be automatically signed
* if the title contains "[scl-production-puppet-new] <slavename> has invalid cert", the script will try once to clean the cert before sending the email.  If this is successful, you'll see a matching "<slavename> is waiting to be signed" email.  The key will be automatically signed
Confirmed users
4,293

edits

Navigation menu