Closed Bug 1453203 Opened 7 years ago Closed 7 years ago

Unrecognised escape sequence

Categories

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

Product:
Infrastructure & Operations
Component:
RelOps: Puppet
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: apop, Assigned: dividehex)

Details

While monitoring channel #buildduty, this notification appeared : [sns alert] Apr 10 20:12:24 releng-puppet2.srv.releng.mdc1.mozilla.com puppet-master: Unrecognised escape sequence '\.' in file /etc/puppet/environments/jwatkins/modules/puppet/manifests/renew_cert.pp at line 21 Can you please check what can be done or point me to the right person that could help us to resolve the issue ?
Assignee: relops → jwatkins
This alerts was from my test environment while I was actively developing on puppet. It didn't hurt production and it did catch an error in my code which has since been fixed.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
FWIW, to squelch the nagios/sns alerts I had changed the membership of the Puppermasters group in papertrail from releng-puppet* to releng-puppet?.srv.releng.scl3*, releng-puppet?.srv.releng.use1*, releng-puppet?.srv.releng.usw2* I had second thoughts about this, since this suppresses all alerts for mdc1/mdc2, and have reverted the membership to the original value. The full error message was puppet-master: Unrecognised escape sequence '\.' in file /etc/puppet/environments/jwatkins/modules/puppet/manifests/renew_cert.pp at line 21 so if this comes up again we might be able to add a negative match on 'environments' to avoid alerts. eg: "Unrecognised escape sequence" --> "Unrecognised escape sequence" -environments
You need to log in before you can comment on or make changes to this bug.