[FOLIO-2147] Investigate occasional failure of daily Jenkins builds for folio-clover Created: 05/Jul/19 Updated: 03/Jun/20 Resolved: 09/Jul/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | David Crossley | Assignee: | Ian Hardy |
| Resolution: | Done | Votes: | 0 |
| Labels: | devops, platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | CP: sprint 67 |
| Story Points: | 1 |
| Development Team: | Core: Platform |
| Description |
|
The daily automated builds of both "folio-clover" and "folio-clover-core" sometimes fail. The job indicates SUCCESS state, but it is not successful (taking 40 seconds rather than normal 20 minutes). The Jenkins job console output shows no message for the "add_host" task: TASK [launch_ec2_instance : launch ec2 instance] ******************************* ok: [localhost -> localhost] TASK [launch_ec2_instance : add_host] ****************************************** TASK [launch_ec2_instance : wait for instances to boot] ************************ [WARNING]: Could not match supplied host pattern, ignoring: tag_Group_folio_clover_core Whereas a normal build there is an "ok" result for that "add_host" task, and the normal launch proceeds. Following up a failed job to manually trigger a re-run, is totally successful. |
| Comments |
| Comment by Ian Hardy [ 05/Jul/19 ] |
|
Noticed this is happening on release and testing builds (haven't seen on snapshot). Snapshot sleeps 60 seconds after terminating the previous ec2 instance, release and testing only 30. I'm increasing the timeout to 60 for release and testing as well. |
| Comment by Ian Hardy [ 08/Jul/19 ] |
|
Looks good so far, if there are no more failures of this type in the coming days, I'll close this. |