Bug 2061490
| Summary: | [MTV] Cannot set the "MAX_VM_INFLIGHT" value in MTV version 2.3.0 | ||
|---|---|---|---|
| Product: | Migration Toolkit for Virtualization | Reporter: | Tzahi Ashkenazi <tashkena> |
| Component: | General | Assignee: | Sam Lucidi <slucidi> |
| Status: | CLOSED ERRATA | QA Contact: | Tzahi Ashkenazi <tashkena> |
| Severity: | high | Docs Contact: | Richard Hoch <rhoch> |
| Priority: | high | ||
| Version: | 2.3.0 | CC: | dagur, fbladilo, istein, jortel |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | 2.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-04-04 18:04:02 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Suggesting this bug as a blocker since: 1. The way to set MAX_VM_INFLIGHT right now is by setting in in Forklift config map, and later delete the forklift controller 2. The MAX_VM_INFLIGHT actual value is not visible. 3. Would be good to have like in MTV-2.2 a way to set MAX_VM_INFLIGHT via UI. Verified on :
cloud10 with MTV 2.3.0-38
change the value using API ( oc patch command ) & from the OCP UI :
From the UI :
Home > search > under the resources tab , search for forklift-controller > choose forklift-controller > YML > change this value :
spec:
controller_max_vm_inflight: 10
Using the API :
oc patch forkliftcontroller/forklift-controller -n openshift-mtv -p '{"spec": {"controller_max_vm_inflight": 10}}' --type=merge
1. tested with default value which is: 20
2. tested with value of :15
* rhev & vmware 6.7 as providers
* using single host ( rhev & esxi )
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (MTV 2.3.0 images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2022:1183 |
Description of problem: we used to change this value from the UI on the previous version of MTV 2.2 2.1 according to Sam there was some changes on the MTV side that was affected from changing this from the UI the fix will be to set this value from the forklift-controller spec pod ! currently workaround that was tested on MTV 2.3.0-37 : oc edit cm forklift-controller-config -n openshift-mtv apiVersion: v1 data: MAX_VM_INFLIGHT: "40" the controller pod need to be deleted in order to retrieve those new values from the cm. 1. control=`oc get pods |grep controller | awk -F " " '{print$1}'` 2. oc delete pod/$control -nopenshift-mtv Version-Release number of selected component (if applicable): cloud10 MTV 2.3.0-37