Bug 2118147

Summary: migrating VMs get scheduled to cordoned nodes and and fail the migration testing.
Product: Container Native Virtualization (CNV) Reporter: Boaz <bbenshab>
Component: InfrastructureAssignee: Dominik Holler <dholler>
Status: NEW --- QA Contact: guy chen <guchen>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.10.3CC: akamra, dholler, fdeutsch, gkapoor
Target Milestone: ---Flags: dholler: needinfo? (bbenshab)
Target Release: future   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:

Comment 1 Dominik Holler 2022-08-26 16:21:15 UTC 
Is there a way to run the scenario again to produce the relevant log files?

1. Enable logging of the scheduler by:

oc patch kubescheduler cluster --type='merge' -p "$(cat <<- EOF
spec:
  logLevel: TraceAll
EOF
)"

2. give the cluster a few minutes to propagate the config change

3. run the scenario

4. get the log files of the scheduler via

for pod in $(oc get -n openshift-kube-scheduler pods -o name | grep kube-scheduler | grep -v guard) ; do (oc logs -n openshift-kube-scheduler $pod kube-scheduler > ${pod/pod\/}.log ) ; done

5. ensure that the logfiles contains the relevant information via

grep  "score=" openshift-kube-scheduler-xxxx-master-y.log
Comment 3 Geetika Kapoor 2023-07-05 12:02:00 UTC 
Hi Guy, Could you give it a try and help in reproducing this bug. Thanks