I had to reconfigure a Jenkins slave, just a change of the Java version. This caused Jenkins master to not recognize the changed Java on the remote end (the slave) and my build had failures thinking that the Java was still the old version.
This you can see in the node's System information link when you click on the node, this is what currently Jenkins thinks is on the remote end, and this may be wrong.
Solution was to simply restart the slave so that Jenkins can pick up the changes in the environment
