[FOLIO-1555] folio-ansible: build failing with pipelining enabled Created: 05/Oct/18 Updated: 12/Nov/18 Resolved: 09/Oct/18 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P3 |
| Reporter: | Wayne Schneider | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, sprint48 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Development Team: | Prokopovych |
| Description |
|
When using Ansible pipelining to improve performance, there are intermittent errors for URI module requests. For example:
{"msg": "The conditional check 'load_module_data.status == updated_code|int' failed. The error was: error while evaluating conditional (load_module_data.status == updated_code|int): 'dict object' has no attribute 'status'"}
It appears that the changed_when conditional may be evaluated before the variable is registered (that's one theory, anyway). This is affecting packer builds from Jenkins at the moment, I haven't see the error elsewhere. |
| Comments |
| Comment by Wayne Schneider [ 09/Oct/18 ] |
|
Rolling back pipelining for packer builds seems to take care of the problem for now. Pipelining is still working fine for the folio-testing-backend build. |