Red Hat Bugzilla – Bug 1235848
vip.yaml missing interface parameter for ControlPlaneNetwork
Last modified: 2015-08-05 09:56:34 EDT
Description of problem: Tuskar is being very picky about the parameters in the network/ports/vip.yaml file. Heat is fine with the fact that this file is missing ControlPlaneNetwork (because it's not used in the file), but Tuskar refuses to deploy. Version-Release number of selected component (if applicable): 2015-06-25.2 How reproducible: 100% Steps to Reproduce: 1. Try to deploy with -e <environment_file> and --plan-uuid 2. 3. Actual results: ERROR: openstack ERROR: Unknown Property ControlPlaneNetwork Expected results: The overcloud should deploy Additional info: This is going to require a patch to the vip.yaml template. I am submitting a patch upstream right now.
The impact of this is somewhat limited. It means that the redis_vip can only live on the control plane when using network isolation. We should be able to put the redis_vip on the internal API network, but until the vip.yaml is patched it will have to live on the ctlplane network.
I have an upstream patch for this which is in review now, not quite ready to merge. https://review.openstack.org/#/c/196400/
Dan, Is the patch needed? I thought this worked with tuskar now without a patch?
(In reply to Mike Burns from comment #5) > Dan, > > Is the patch needed? I thought this worked with tuskar now without a patch? Yes, this is needed. There is still a bug in this area.
Mike - You can include this in the next downstream build.
Mike - Change of plans, don't include this yet.
The upstream fix for this was merged upstream. https://review.openstack.org/#q,Ic20281e58a1130afe18d5aec505a3df199841fd5,n,z
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-2015:1549