I have a Job bound to master. This job has been started by a script and is now waiting for execution on master because another Job is running on the master (one executor).

The Build Queue mouseover displays: "Waiting for next available executor on" (no mention of which node)

The Build Queue xml api shows:

<queue>
	<item>
		<action>
			<cause>
				<shortDescription>Started by remote host 127.0.0.1 with note: server_post_promote transaction -snip- / 169402 @ 2011/07/27 13:10:03</shortDescription>
			</cause>
			<cause>
				<shortDescription>Started by remote host 127.0.0.1 with note: server_post_promote transaction -snip- / 169419 @ 2011/07/27 13:21:18</shortDescription>
			</cause>
		</action>
		<blocked>false</blocked>
		<buildable>true</buildable>
		<params></params>
		<stuck>true</stuck>
		<task>
			<name>BS-Update-1</name>
			<url>http://-snip-/jenkins/job/BS-Update-1/</url>
			<color>blue</color>
		</task>
		<why>Waiting for next available executor on </why>
		<buildableStartMilliseconds>1311772204293</buildableStartMilliseconds>
	</item>
</queue>

Note how the why is missing the node name.

Going to the job page however, the Build history is (correctly) displaying: "#24 (pending - Waiting for next available executor on master )"

I have also cross-checked with another job that is also bound to master:
When I start it manually, the same problem exists wrt. to the non-displayed node name.
(And I assume that the fact that this job is display as "stuck" whereas the manually started one isn't, is just to do with how "stuck" is calculated and that this job has waited more often or something.)