I've seen a similar situation on my Debian installation. After restart, the slave node label is visible in the configuration, but the jobs will not schedule on that slave node until I save the (unchanged) configuration of the slave node.
I've seen a similar situation on my Debian installation. After restart, the slave node label is visible in the configuration, but the jobs will not schedule on that slave node until I save the (unchanged) configuration of the slave node.