[LU-10183] If node provisioning fails, Maloo should try again Created: 01/Nov/17 Updated: 05/Apr/18 Resolved: 05/Apr/18 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Ben Evans (Inactive) | Assignee: | WC Triage |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Project: | Test Infrastructure | ||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
If maloo fails the node-provisioning task, as a user I need to push a new version of the patch. It would be nice if Maloo simply tried again later, or let me press a button to re-run the test, rather than update the patch. |
| Comments |
| Comment by James Nunez (Inactive) [ 20/Dec/17 ] |
|
Ben - When node-provisioning fails, autotest does try several times to load/configure Lustre on the nodes. The issue I've run into is that the node or VM may be bad and it would be beneficial for the initialization to be retried on a different set of nodes/VMs. Retrying on different nodes/VMs was requested previously and remains an open issue. |
| Comment by Ben Evans (Inactive) [ 20/Dec/17 ] |
|
From a non-priviliged user's perspective, if I push a commit to gerrit, and provisioning fails, my only recourse to try again is to either rebase the change (if possible) or make a silly change, like adding a space or a period to the commit message and pushing it again. There's no way for me to hit a "try it again" button. These don't happen often, but they do seem to come in bursts, and it gets pretty frustrating. |
| Comment by Peter Jones [ 05/Apr/18 ] |
|
Ben You should be setup to be able to re-trigger tests now Peter |