Red Hat Bugzilla – Bug 1234673
"openstack overcloud deploy" does not respect command-line parameters
Last modified: 2015-08-05 09:55:21 EDT
Description of problem: When running "openstack overcloud deploy", the command-line parameters are being ignored. Version-Release number of selected component (if applicable): Puddle 2015-06-22-1 How reproducible: 100% Steps to Reproduce: 1. Install undercloud 2. "openstack overcloud deploy -e /home/stack/environments --use-tripleo-heat-templates --neutron-public-interface nic2 --neutron-network-type gre --neutron-tunnel-types gre --libvirt-type kvm --ntp-server clock.redhat.com --control-scale 1 --compute-scale 2 --plan-uuid 35380043-2860-4f11-a458-2b4485ed7b3d" 3. Actual results: All the command-line parameters are being ignored, including my environment directory, the neutron public interface, and the compute scale. None of that was respected. Expected results: The overcloud should deploy with 2 computes, with neutron public interface on nic2, with network isolation. Additional info:
There are a few different components which cause this issue. `--use-tripleo-heat-templates` shouldn't be used with `--plan-uuid` - we shouldn't allow users to do that. The parameters are, incorrectly not being passed to Heat when using t-h-t. We need to verify they are all being passed in the Tuskar case and the t-h-t case.
Midstream fix https://review.gerrithub.io/237372
Fix merged.
I tried this again today with the latest poodle (2015-06-24 last poodle), and the command line parameters are still not being respected. Here's what I used: openstack overcloud deploy -e /home/stack/network_environment.yaml --use-tripleo-heat-templates --neutron-public-interface nic2 --neutron-network-type gre --neutron-tunnel-types gre --libvirt-type kvm --ntp-server clock.redhat.com --control-scale 1 --compute-scale 2 The network_environment.yaml was ignored. The --compute-scale was ignored. I didn't check the other parameters to see if they were respected. Is this because I'm using --use-tripleo-heat-templates?
@Dan I do not believe it is ignoring the network_environment.yaml. At least, not by the plugin. In my initial attempt to test, I had syntax errors in my network_environment.yaml, and it would not continue until they were fixed. To me, that is a clear indication that it is *not* being ignored. This is with whatever puddle is available 06/25/15 at 8:30am EST.
Verified python-rdomanager-oscplugin-0.0.8-18.el7ost.noarch .
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