Bug 1094710
Summary: | [Openstack-Staypuft]: Provisioning token expires on previously created hosts | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Martyn Taylor <mtaylor> |
Component: | rubygem-staypuft | Assignee: | Martyn Taylor <mtaylor> |
Status: | CLOSED WONTFIX | QA Contact: | Omri Hochman <ohochman> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | aberezin, mburns, mlopes, morazi, mtaylor, ohochman, rhos-maint, yeylon |
Target Milestone: | z4 | Keywords: | FutureFeature, TestOnly, ZStream |
Target Release: | 4.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
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.
|
Story Points: | --- |
Clone Of: | 1093055 | Environment: | |
Last Closed: | 2014-07-15 16:59:24 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1093055 | ||
Bug Blocks: | 1093126 |
Comment 1
Martyn Taylor
2014-05-06 10:40:57 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. |