Revision 2a2e2610
| b/htools/Ganeti/HTools/Program/Hbal.hs | ||
|---|---|---|
| 180 | 180 |
then do |
| 181 | 181 |
hPrintf stderr "Exiting early due to user request, %d\ |
| 182 | 182 |
\ jobset(s) remaining." (length alljss)::IO () |
| 183 |
return False
|
|
| 183 |
return True
|
|
| 184 | 184 |
else execJobSet master nl il cref alljss |
| 185 | 185 |
|
| 186 | 186 |
-- | Execute an entire jobset. |
| b/man/hbal.rst | ||
|---|---|---|
| 415 | 415 |
----------- |
| 416 | 416 |
|
| 417 | 417 |
The exit status of the command will be zero, unless for some reason the |
| 418 |
algorithm fatally failed (e.g. wrong node or instance data), or (in case |
|
| 419 |
of job execution) either one of the jobs has failed or the balancing was |
|
| 420 |
interrupted early. |
|
| 418 |
algorithm failed (e.g. wrong node or instance data), invalid command |
|
| 419 |
line options, or (in case of job execution) one of the jobs has failed. |
|
| 420 |
|
|
| 421 |
Once job execution via Luxi has started (``-X``), if the balancing was |
|
| 422 |
interrupted early (via *SIGINT*, or via ``--max-length``) but all jobs |
|
| 423 |
executed successfully, then the exit status is zero; a non-zero exit |
|
| 424 |
code means that the cluster state should be investigated, since a job |
|
| 425 |
failed or we couldn't compute its status and this can also point to a |
|
| 426 |
problem on the Ganeti side. |
|
| 421 | 427 |
|
| 422 | 428 |
BUGS |
| 423 | 429 |
---- |
Also available in: Unified diff