Bug #19173

host never leaves build mode when token expires during built

Added by Dmitri Dolguikh over 5 years ago. Updated about 4 years ago.

Host creation
Target version:
Bugzilla link:
Fixed in Releases:
Found in Releases:


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 >= ?",'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.

Associated revisions

Revision 5e38d636 (diff)
Added by Dmitri Dolguikh about 5 years ago

Fixes #19173 - build notification succeeds with expired token.


#1 Updated by The Foreman Bot over 5 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request added

#2 Updated by Anonymous about 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#3 Updated by Ivan Necas about 5 years ago

  • Target version set to 1.13.1

#4 Updated by Marek Hulán about 5 years ago

  • Legacy Backlogs Release (now unused) set to 240

Also available in: Atom PDF