Description of problem:
When building hosts, the templates get rendered using a token that is valid for a certain amount of time.
This token is also verified in the "built" template, which is suposed to flip the host from "in build" to "build finished".
Thus if you start your deployment while the token was still OK, and it expires *during* the build, the state will not be switched and the machine will boot in build mode again on next reboot.
The new build will error out, but the machine will remain in the booted broken build system and will not boot from local disc.

The problem is because of:
The unattended "built" template calls "find_host_by_token" which calls "Host.for_token(token).first" (see app/controllers/unattended_controller.rb)
for_token is defined as
  scope :for_token, ->(token) { joins(:token).where(:tokens => { :value => token }).where("expires >= ?", Time.now.utc.to_s(:db)).select('hosts.*') }
(in app/models/concerns/hostext/token.rb upstream, app/models/host/managed.rb in satellite 6.2)
thus the host is never found and the "built" mode flip is never executed.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. put host in build mode
2. wait till token is almost expired
3. boot and build machine

Actual results:
host is not marked as "finished"/"built" when token expires before /unattended/built is called

Expected results:
host is marked as built

Additional info:
Not sure if it would be better to have the built template not verify the token expiry, or extend the token for some time when the actual build starts. Or maybe just have a clenaup task that flips all machines that have expired tokens into "built" state.