Tacker should return error when invalid value is entered for 'cpu_affinit' in VNFD template.
Bug #1584610 reported by
Santosh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
In Progress
|
Low
|
hewei |
Bug Description
A dedicated cpu resource can be requested through tacker vnfd template using cpu_affinity value.
cpu_allocation:
cpu_affinity: <value>
valid values are 'dedicated'. Other than this value, if any invalid value(typo) is given, tacker will go ahead and spin a regular vnf. This might be user error and user may not be aware of it (unless he is consciously creating it). Invalid value for this field should atleast be warned to user if not preventing him to create a vnf.
tags: | added: rfe |
Changed in tacker: | |
assignee: | nobody → Manikantha Srinivas Tadi (manikantha-tadi) |
tags: | removed: rfe |
Changed in tacker: | |
importance: | Undecided → Low |
Changed in tacker: | |
assignee: | Manikantha Srinivas Tadi (manikantha-tadi) → bharaththiruveedula (bharath-ves) |
Changed in tacker: | |
assignee: | bharaththiruveedula (bharath-ves) → hewei (hewei-cmss) |
Changed in tacker: | |
status: | New → In Progress |
To post a comment you must log in.
Tried to reproduced this issue but it was not reproducible.
Verified that fix of this issue is already committed under [1].
[1] https:/ /github. com/openstack/ tacker/ commit/ 43cf012ea8b89c2 029c93ec4f255fa 98633d5df5# diff-da51e626eb b454e0b6c561fc4 4cbbb3f