| << Back to previous view |
|
[QB-3672] Improve error messages : Error allocating node for step
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Benoit Maury-Bouet | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| File Attachments: |
2022-01-16_16-44-00.png
|
| Description |
|
Dear all,
Could you add the configuration pathname or id to the error mesages about :Error allocating node for step 'XXX' ? That would help finding the faulty configuration on a large server Thanks |
| Comments |
| Comment by Robin Shen [ 16/Jan/22 08:44 AM ] |
| This message is displayed in step overview of failed build, which is under configuration page, or do you mean something else? |
| Comment by Benoit Maury-Bouet [ 17/Jan/22 07:03 AM ] |
|
Hi Robin,
Yes I would like to get that information as well in the error message itself. This is fine indeed when you look at the GUI but we would like to get that information also by parsing QB logs as well push them in ELK. It would help us design some dashboard and also be able to dig in some issues that could have been there for a while. |
| Comment by Robin Shen [ 17/Jan/22 10:35 AM ] |
|
Configuration info also displayed in system log:
2022-01-17 18:34:12,722 [Thread-74] ERROR com.pmease.quickbuild.DefaultBuildEngine - Error allocating node (configuration: root, build id: null, step: master) com.pmease.quickbuild.QuickbuildException: Can not find any node matching specified criteria. at com.pmease.quickbuild.DefaultBuildEngine.run(DefaultBuildEngine.java:1386) at java.lang.Thread.run(Thread.java:748) |
| Comment by Benoit Maury-Bouet [ 17/Jan/22 10:40 AM ] |
|
Ah nice did it change between 10.x and 11.x ?
Because what I get for now is : Error allocating node for step 'master' so no indication of the configuration |
| Comment by Robin Shen [ 17/Jan/22 10:44 AM ] |
| Yes, it is 11.0.x |
| Comment by Benoit Maury-Bouet [ 17/Jan/22 10:46 AM ] |
|
Ahh perfect then we can close this then it looks like we'll have what we need when switching to 11.x then
THanks |