puppet jobs failing to start memcached

[Derek Higgins]

All puppet jobs are failing with

2015-05-25 10:10:53.059 | + echo 'Waiting for the overcloud stack to be ready'
2015-05-25 10:10:53.059 | Waiting for the overcloud stack to be ready
2015-05-25 10:10:53.059 | + wait_for_stack_ready -w 2100 10 overcloud
2015-05-25 10:27:02.083 | Command output matched '(CREATE|UPDATE)_FAILED'. Exiting...
2015-05-25 10:27:02.084 | + cleanup
...
2015-05-25 10:27:46.649 | | stack_status_reason | Resource CREATE failed: ResourceUnknownStatus: Resource |
2015-05-25 10:27:46.649 | | | failed - Unknown status FAILED due to "Resource CREATE |
2015-05-25 10:27:46.650 | | | failed: ResourceUnknownStatus: Resource failed - |
2015-05-25 10:27:46.650 | | | Unknown status FAILED due to "Resource CREATE failed: |
2015-05-25 10:27:46.650 | | | Error: Deployment to server failed: deploy_status_code |
2015-05-25 10:27:46.650 | | | : Deployment exited with non-zero status code: 6""
...
The puppet apply is failing to start memcached
May 25 11:17:12 ov-rl42yb3srpw-0-a3tdjdze5hu5-controller-7lasxwb34bb5 os-collect-config[947]: Error: Could not start Service[memcached_11211]: Execution of '/sbin/service memcached_11211 start' returned 6: Starting memcached_11211 (via systemctl): Failed to start memcached_11211.service: Unit memcached_11211.service failed to load: No such file or directory.

This is probably linked to a recent update to the memcached puppet module
https://github.com/saz/puppet-memcached/commit/b8375f9e1dbbf8c94e51e70fa1a4a17872cd05dd

[Jiří Stránský (jistr)]

A pin in TOCI which should work around the issue: https://review.openstack.org/#/c/185364/

Bug reported to puppet-memcached: https://github.com/saz/puppet-memcached/issues/61

[Giulio Fidente (gfidente)]

Moved to Low as upstream module reverted the offending change and is now debating how to reimplement support for multiple instances without breaking backward