Bug 1154730 - Set token_duration to 6 hours instead of one hour
Summary: Set token_duration to 6 hours instead of one hour
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhel-osp-installer
Version: Foreman (RHEL 6)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Installer
Assignee: Mike Burns
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-20 15:43 UTC by Ramon Acedo
Modified: 2016-09-29 13:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-29 13:31:45 UTC


Attachments (Terms of Use)

Description Ramon Acedo 2014-10-20 15:43:54 UTC
If the installation takes more than one hour or if the servers have been registered but not deployed for more than an hour the token expires and the host won't be built. The result is the hosts rebooting all the time into installation as the pxelinux.cfg/mac_address_of_the_node is not updated to boot from the local disk.

Comment 1 Ramon Acedo 2014-10-20 15:47:10 UTC
We tried doing this from the foreman console:

# foreman-rake console

h=Host.find_by_name("osp1-controller02.domain.example)
h.token
=> #<Token id: 158, value: "31255447-68d4-4467-a722-861cb65bf832", expires: "2014-10-20 18:17:05", host_id: 87>
h.token.expires="2014-10-20 21:10:57"
h.token.save!

The token expire time is changed but the host still ends up in the building loop.

Comment 2 Lukas Zapletal 2014-10-20 15:48:10 UTC
http://projects.theforeman.org/issues/7995

Comment 5 Jaromir Coufal 2016-09-29 13:31:45 UTC
Closing list of bugs for RHEL OSP Installer since its support cycle has already ended [0]. If there is some bug closed by mistake, feel free to re-open.

For new deployments, please, use RHOSP director (starting with version 7).

-- Jaromir Coufal
-- Sr. Product Manager
-- Red Hat OpenStack Platform

[0] https://access.redhat.com/support/policy/updates/openstack/platform


Note You need to log in before you can comment on or make changes to this bug.