Bug 1730689
Summary: | [OSP15] Deployment failing due to discrepancy between OVS TripleO param types and puppet expected types | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Vadim Khitrin <vkhitrin> |
Component: | openstack-tripleo-heat-templates | Assignee: | RHOS Maint <rhos-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Vadim Khitrin <vkhitrin> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 15.0 (Stein) | CC: | cfontain, emacchi, fbaudin, hakhande, mburns, rheslop, rhos-maint, skramaja, supadhya, yrachman |
Target Milestone: | --- | Keywords: | Triaged, ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Release Note | |
Doc Text: |
There is a known issue wherein deployments will fail with the following message.
`puppet-user: Error: Parameter value failed on Vs_config[other_config:n-revalidator-threads]: Invalid external_ids 1. Requires a String, not a Integer`
This is due to tripleo parameters of type integer being expected by puppet to be of type string. To work around, include the following in deployment templates:
ComputeOvsDpdkSriovExtraConfig:
"vswitch::dpdk::handler_cores": "1"
"vswitch::dpdk::revalidator_cores": "1"
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-12-03 19:48:29 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
Vadim Khitrin
2019-07-17 11:16:34 UTC
Workaround for now is to include ExtraConfig, for example my Compute role is ‘ComputeOvsDpdkSriov’, I added the following parameter to deployment templates: ComputeOvsDpdkSriovExtraConfig: "vswitch::dpdk::handler_cores": "1" "vswitch::dpdk::revalidator_cores": "1" Re-setting Target Milestone z1 to --- to begin the 15z1 Maintenance Release. Vadim can you update the status and maybe see if this can be closed. |