incorrect datatype for "OctaviaFlavorId"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo-heat-templates (Ubuntu) |
In Progress
|
Undecided
|
Pratik Pravin Bandarkar |
Bug Description
Description:
Heat templates will expect “OctaviaFlavorId” value to “number”. The default value is “65”. Where the actual flavor ID will be in the format of "number+
For ex. “3a6b8284-
<snip>
2018-12-21 14:32:44.354 18144 ERROR heat.engine.
2018-12-21 14:32:44.354 18144 ERROR heat.engine.
</snip>
To fix the issue, instead of using "Number" we can expect "String":
<snip>
OctaviaFlavorId:
default: 65
description: Nova flavor ID to be used when creating the nova flavor for
#type: number #<==
type: string #<==
</snip>
Steps to reproduce:
1. Deployed "Pike" release with Octavia
2. Created few Octavia load balancers
3. As Octavia loadbalancer was using custom flavor(
4. To fix the issue, I updated data type for "OctaviaFlavorId" from "number" to "String".
Environment:
- Pike
- Queens
- Rocky
Expected result: Installation/
Actual result: Upgradation of OpenStack with alphanumeric OctaviaFlavorId fails.
I think(not tested), even for the fresh installation if the user tries to specify OctaviaFlavorId in alphanumeric format, the installation will fail.
Changed in tripleo-heat-templates (Ubuntu): | |
assignee: | nobody → Pratik Pravin Bandarkar (pratik-bandarkar) |
no longer affects: | tripleo |
Changed in tripleo-heat-templates (Ubuntu): | |
status: | New → In Progress |
This issue was fixed in the openstack/ tripleo- heat-templates 10.3.0 release.