Description of problem:

When running a job on multiple hosts, opening that Job overview in WebUI, in the host list, all the subtasks that haven't been run yet are shown to be in state "N/A". In previous versions, it was "planned". I believe N/A is not something a user should see - similar to NULL, unhandled exceptions etc.

How reproducible:

Deterministic

Is this issue a regression from an earlier version:

Yes

Steps to Reproduce:

1. Run a job on two hosts that takes some time to finish, with concurrency set to 1

2. Look at the second host's subtask state

Actual behavior:

N/A

Expected behavior:

Something more descriptive