SR-IOV numvfs setting is invalid by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Fedor Zhadaev | ||
Mitaka |
Fix Released
|
High
|
Fedor Zhadaev | ||
Newton |
Fix Released
|
High
|
Alexey Shtokolov |
Bug Description
Steps to reproduce:
1. create an environment (any settings)
2. add a node to the environment with SR-IOV enabled inteface(s) and go to the node interfaces configuration screen
3. enable SR-IOV on a node interface and check SR-IOV settings
Expected result: all SR-IOV settings are valid by default
Actual result: numvfs setting is marked as invalid on UI.
UI highlights numvfs field because it has "number" type and "null" default value. "null" isn't recognized by UI as valid number input value.
Proposed solution is to add nullable=true flag to numvfs setting
(which was supported on UI https:/
It will generate checkbox near the number control, that indicates
if setting value is null or not.
Changed in fuel: | |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
Changed in fuel: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → Andriy Popovych (popovych-andrey) |
description: | updated |
Changed in fuel: | |
assignee: | Julia Aranovich (jkirnosova) → Fuel Sustaining (fuel-sustaining-team) |
status: | In Progress → Confirmed |
Changed in fuel: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → Fedor Zhadaev (fzhadaev) |
Changed in fuel: | |
milestone: | 9.2 → 11.0 |
tags: | added: on-verification |
tags: | removed: on-verification |
tags: | added: on-verification |
tags: | removed: on-verification |
Fix proposed to branch: stable/mitaka /review. openstack. org/412118
Review: https:/