Bug 1094710 - [Openstack-Staypuft]: Provisioning token expires on previously created hosts
Summary: [Openstack-Staypuft]: Provisioning token expires on previously created hosts
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rubygem-staypuft
Version: 4.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: z4
: 4.0
Assignee: Martyn Taylor
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On: 1093055
Blocks: 1093126
TreeView+ depends on / blocked
 
Reported: 2014-05-06 10:40 UTC by Martyn Taylor
Modified: 2014-07-29 19:22 UTC (History)
8 users (show)

Fixed In Version: ruby193-rubygem-staypuft-0.0.13
Doc Type: Bug Fix
Doc Text:
Previously, provision tokens set on a host could expire before the deployment completed. As a result, hosts were not able to finish the provisioning process due to the expired token. This update resets the host token prior to the hosts provisioning. The result is that host provisioning tokens only timeout if the timeout value is exceeded.
Clone Of: 1093055
Environment:
Last Closed: 2014-07-15 16:59:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Martyn Taylor 2014-05-06 10:40:57 UTC 
Fix submitted: https://github.com/theforeman/staypuft/pull/118
Comment 3 Martyn Taylor 2014-05-14 08:46:53 UTC 
commit 0864b1fb7b1589dd5208f21f4cea8acaa2141030
Author: Martyn Taylor <mtaylor>
Date:   Tue May 6 11:05:31 2014 +0100

    Reset host token during build task
    
    Foreman sets the expire provisioning token on a host machine when host
    machine build flag is set, not when the host is actually provisioned.
    In Staypuft we delay the provisioning of some machines until later in
    the orchestration sequence.  This may result in token expiry.  This
    patch resets the host expire token during the Staypuft host build task.
Note You need to log in before you can comment on or make changes to this bug.