The NodeLabel Parameter plugin simply does not work.
The label parameter type appears to not match the actual node labels, leaving jobs stalled in the queue.
The node parameter type correctly identifies the matching nodes, but the selected node is not used when the build starts.

I installed this plugin as a workaround for the pipeline job type having no apparent means of identifying the node labels that are capable of running the job without adding it. That's probably another bug.
In this specific case, the node that is identified is part of a VMware-managed cloud, and is online and accessible while it is being ignored by the queue manager.