-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
None
-
-
None
Description of problem:
When changing the instancetype from cx1.medium->large the maxSockets field is also changed, which in process raise a RestartRequired condition. This mean that hot-plugging is prevented until restart, but the user does not know or have a general information on any of the processes. It would be useful to let users know about RestartRequired condition which blocks hot-pluging. This is generic use case and virt should provide with details regarding need for restart.UI can further consume that backend information and populate on UI needs for restart.
Version-Release number of selected component (if applicable):
4.20
How reproducible:
always
Steps to Reproduce:
1. Create a VM with cx1.medium instance type 2. Switch the instance type to cx1.large
Actual results:
No alert is shown
Expected results:
Some kind of information
Additional info:
although some parts of this https://github.com/abrennan89/openshift-docs/blob/e0f3064841ee2a45b07ef70f17c96fe236d6b1f4/modules/virt-disable-CPU-VM-hotplug-instancetype.adoc explains the behavior but a better output can be very useful and clear details of fields. hot plug docs - https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/virtualization/managing-vms#virt-hot-plugging-memory_virt-edit-vms