Bug 1245737
Summary: | hard-coded parameters can't be overridden | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Steven Hardy <shardy> |
Component: | python-rdomanager-oscplugin | Assignee: | Brad P. Crochet <brad> |
Status: | CLOSED ERRATA | QA Contact: | Marius Cornea <mcornea> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 (Kilo) | CC: | akrivoka, calfonso, djuran, dnavale, dprince, ggillies, jdonohue, jraju, jslagle, jstransk, kbasil, mburns, mcornea, michele, mschuppe, ohochman, racedoro, rhel-osp-director-maint, roxenham, sasha, tiswanso, yeylon |
Target Milestone: | y2 | Keywords: | Triaged, ZStream |
Target Release: | 7.0 (Kilo) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-rdomanager-oscplugin-0.0.10-11.el7ost | Doc Type: | Bug Fix |
Doc Text: |
Previously, hard-coded parameters were being passed directly to Orchestration. As a result, the parameters could not be overridden properly.
With this update, a custom environment file from the parameters collected is generated and pass as 'parameter_defaults', allowing parameters to be overridden.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-21 16:47:54 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: | 1191185, 1243520, 1250654, 1273462 |
Description
Steven Hardy
2015-07-22 15:46:51 UTC
One approach I've got is here: https://review.gerrithub.io/#/c/243608/ Using this approach I'm able to override any parameters by simply using a custom environment file. We've just hit this when trying to specify ExtraConfig, as this seems to be one of the hard-coded parameters. Regardless of what we specify in an environment file, ExtraConfig would always be '{}'. For our use case, using 'controllerExtraConfig' instead should suffice for now. The related BZ is bug 1258107. Moving to urgent and blocker for y2. Not being about to turn off debug is filling up disks in the undercloud. Note the review Dan posted has now moved to https://review.openstack.org/#/c/221750/ after the client repo moved to upstream TripleO. IMO we should land that and include the fix ASAP, as this is a major usability issue. Some additional information for things seen during Cisco ML2 driver testing: 1) NeutronNetworkVLANRanges is unable to be set in an override environment file (regardless of parameter section, ie. 'parameters' v. 'parameter_defaults') - workaround: use the command-line option —neutron-network-vlan-ranges 2) controllerExtraConfig: - only works when set in 'parameters:' section in an override environment file - setting it in 'parameter_defaults:' doesn't work - Example: In private (override) environment file: parameters: controllerExtraConfig: { "neutron::server::api_workers": 0, "neutron::server::rpc_workers": 1, } 3) ExtraConfig: - doesn't work, regardless of yaml section 4) NeutronMechanismDrivers setting works within override environment files. Brad, could you look into this please? *** Bug 1250654 has been marked as a duplicate of this bug. *** stack@instack:~>>> heat stack-show overcloud | grep "NeutronVniRanges" | | "NeutronVniRanges": "1:1000", stack@instack:~>>> cat param_overrides.yaml parameters: NeutronVniRanges: "1:3000" stack@instack:~>>> openstack overcloud deploy --templates -e param_overrides.yaml stack@instack:~>>> heat stack-show overcloud | grep "NeutronVniRanges" | | "NeutronVniRanges": "1:3000", 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/RHSA-2015:2650 |