Unable to update application memory using GUI when vswitch type is set to none
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Austin Sun |
Bug Description
Brief Description
-----------------
When modify the application memory setting using GUI with the vswitch type set to none , an error message window popped up unless the user enters a number greater than 0 in the #of vSwitch 1G Hugepages Node fields.
System will not allocate the default huge pages for vswitch when the vswitch type is set to none and the #of vSwitch 1G Hugepages Node fields should be hidden in Update Memory Allocation form.
Severity
--------
Major
Steps to Reproduce
------------------
1.configure a AIO-SX system with the vswitch_type set to none
2 login Horizon dashboard as 'admin'
3 lock the node to modify the memory
4. select page Admin -> Inventory -> Memory -> Update Memory
a. reduce 512 from the number of 2M-page
b. add 1 1G-page
Save the changes
Expected Behavior
------------------
# of vSwitch 1G Hugepages Node fields should be hidden when the vswitch type is set to none. The application memory allocation should be accepted without any errors.
Actual Behavior
----------------
An error message popped up unless the user enters a non-zero value for vswitch huge pages.
Reproducibility
---------------
yes
System Configuration
-------
AIO-SX and Multi-node system
Branch/Pull Time/Commit
-------
f/stein as of 2019-04-24
Timestamp/Logs
--------------
Marking release gating; as this is related to huge pages assigning to Austin to start.