The Puppet Labs Issue Tracker has Moved:

Bug #3652

Quoting incompatible between 0.24 and 0.25

Added by Alan Sparks almost 5 years ago. Updated over 3 years ago.

Status:Needs More InformationStart date:04/22/2010
Priority:NormalDue date:
Assignee:Alan Sparks% Done:


Target version:-
Affected Puppet version:0.25.4 Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:


I hope this is related to bug #3387. But symptoms are not the same.

For augeus in 0.24.8, paths with single quotes (for filters) required escapes, similar to the following:

augeas { "ensure /etc/hosts hostname IP":
   context => "/files/etc/hosts",
   changes => [
      "set \"*[canonical='$hostname']/ipaddr\" $ipaddress",

Same resource fails to work under 0.25.4. Apparently while the parser in 0.24 broke the augeas command at the single-quote, 0.25.4 now maintains the escaped double quotes, and tacks the context onto the front of the path. Which means you wind up sending a path like: /files/etc/hosts/\“*[canonical=‘$hostname’]/ipaddr\” which is syntactically incorrect.

Is there no way to allow compatibility between the two releases at least for migration, without putting in a massive case expression based on puppetversion?


#1 Updated by James Turnbull almost 5 years ago

  • Status changed from Unreviewed to Needs Decision
  • Assignee set to Bryan Kearney

#2 Updated by James Turnbull about 4 years ago

  • Assignee changed from Bryan Kearney to Nigel Kersten

#3 Updated by Markus Roberts about 4 years ago

I do not see what change could have caused the described problem, in part because I am not understanding the intended outcome. Specifically, I’m not getting what “the parser in 0.24 broke the augeas command at the single-quote” means.

#4 Updated by Nigel Kersten over 3 years ago

  • Status changed from Needs Decision to Needs More Information
  • Assignee changed from Nigel Kersten to Alan Sparks

Also available in: Atom PDF