Bug 1532703
| Summary: | When deploying an Overcloud on auto discovered nodes nova errors with host not mapped to any cell | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ramon Acedo <racedoro> |
| Component: | openstack-tripleo-common | Assignee: | Dmitry Tantsur <dtantsur> |
| Status: | CLOSED ERRATA | QA Contact: | mlammon |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 12.0 (Pike) | CC: | berrange, bfournie, dasmith, dyasny, eglynn, kchamart, mburns, rhel-osp-director-maint, sbauza, sferdjao, sgordon, slinaber, srevivo, vromanso |
| Target Milestone: | z2 | Keywords: | Triaged, ZStream |
| Target Release: | 12.0 (Pike) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-common-7.6.9-2.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-03-28 17:27:14 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: | |||
|
Description
Ramon Acedo
2018-01-09 15:57:24 UTC
I think we should enable the periodic task for host discovery in the undercloud (we already do it for the overcloud). Moving to instack-undercloud. master patch proposed Trying another approach that won't involve a potentially expensive periodic task: https://review.openstack.org/#/c/532495/ After applying the patch https://review.openstack.org/#/c/532495/ the cells issue is gone and there's no need to run 'nova-manage cell_v2 discover_hosts' I have managed to deploy a overcloud on autodiscovered nodes with no extra steps in OSP12. Had to properly tag the nodes first though Deployed latest osp 12 2018-03-10.1 Env openstack-tripleo-common-7.6.9-2.el7ost.noarch Based on commet#4&5 and code is in puddle we can move to verify 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://access.redhat.com/errata/RHBA-2018:0607 |