Bug 1380701
Summary: | osp-director-10: first attempt of openstack undercloud install fails over "timed out creating the default Deployment Plan" (second attempt to re-run succeed) | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Omri Hochman <ohochman> |
Component: | instack-undercloud | Assignee: | Dougal Matthews <dmatthew> |
Status: | CLOSED ERRATA | QA Contact: | Alexander Chuzhoy <sasha> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 10.0 (Newton) | CC: | dbecker, dmatthew, jcoufal, jjoyce, jschluet, jslagle, mburns, mcornea, morazi, rhel-osp-director-maint, sasha, slinaber, tvignaud |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | 10.0 (Newton) | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | instack-undercloud-5.0.0-0.20160929132429.56e65af.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-12-14 16:06:41 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: | |||
Bug Blocks: | 1337794 |
Description
Omri Hochman
2016-09-30 11:33:00 UTC
This is the same as this upstream bug: https://bugs.launchpad.net/tripleo/+bug/1628388 It was resolved hre: https://github.com/openstack/instack-undercloud/commit/0c86110ef1499db20e816c43c700716417752bdd ok, thanks for the update. i believe this has been built downstream. can you confirm and if so, set the Fixed in Version and move the bug to MODIFIED? Verified: Environment: instack-undercloud-5.0.0-0.20160930175750.9d2a655.el7ost.noarch The reported issue doesn't reproduce. I spotted this error in upstream CI and increased the timeout value. From the logs no error had happened, it just took longer than expected for some reason. https://review.openstack.org/#/c/391373/ Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-2948.html |