Bug 1710503
| Summary: | all-in-one missing network configuration for network-isolation | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Victor Voronkov <vvoronko> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Alex Schultz <aschultz> |
| Status: | CLOSED ERRATA | QA Contact: | Victor Voronkov <vvoronko> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 15.0 (Stein) | CC: | aschultz, mburns, mcornea, slinaber |
| Target Milestone: | beta | Keywords: | Triaged |
| Target Release: | 15.0 (Stein) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-10.5.1-0.20190612140413.fdcfc30.el8ost | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-09-21 11:22:03 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
Victor Voronkov
2019-05-15 16:18:15 UTC
It turns out that with network-isolation we now need to define the networks on the role themselves or it fails in this fashion. Currently the standalone role[0] does not have any network information associated with it because it can also be shared with a undercloud-less deployment. We'll need to see if we can get away with adding the network config (like on the controllers[1]) for both scenarios or we'll need to create a new role for this deployment architecture. [0] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/roles/Standalone.yaml [1] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/roles/Controller.yaml#L12-L22 https://review.opendev.org/#/c/628265/ actually removed them, i guess we'll need to investigate re-adding them or handling this in a different fashion Not a blocker as the workaround can be to not use network isolation or add the network information to the role being used. Verified on compose RHOS_TRUNK-15.0-RHEL-8-20190619.n.1 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/RHEA-2019:2811 |