Loading...

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Undefined
Fix Version/s: None
Affects Version/s: 4.18
Component/s: GitOps ZTP
Labels:
- rds-core
- rds-core-reference

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
None
Regression:
None

Target Backport Versions:
None
Target Version:

4.21.0
Release Blocker:
None
Sprint:
None

RH Private Keywords:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Impact Score:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:
cluster-compare showing a diff for what it seems it is a default value in the NUMA -aware scheduler.

**********************************Cluster CR: nodetopology.openshift.io/v1_NUMAResourcesOperator_numaresourcesoperator
Reference File: required/scheduling/nrop.yaml
Description:
  https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/core/telco-core-ref-design-components.html#telco-core-scheduling_core-ref-design-components
Diff Output: diff -u -N /tmp/MERGED-3051149764/nodetopology-openshift-io-v1_numaresourcesoperator_numaresourcesoperator /tmp/LIVE-3422791799/nodetopology-openshift-io-v1_numaresourcesoperator_numaresourcesoperator
--- /tmp/MERGED-3051149764/nodetopology-openshift-io-v1_numaresourcesoperator_numaresourcesoperator    2025-07-14 13:07:54.094366304 +0000
+++ /tmp/LIVE-3422791799/nodetopology-openshift-io-v1_numaresourcesoperator_numaresourcesoperator    2025-07-14 13:07:54.094366304 +0000
@@ -3,6 +3,7 @@
 metadata:
   name: numaresourcesoperator
 spec:
+  logLevel: Normal
   nodeGroups:
   - config:
       infoRefreshMode: Periodic**********************************Cluster CR: nodetopology.openshift.io/v1_NUMAResourcesScheduler_numaresourcesscheduler
Reference File: required/scheduling/sched.yaml
Description:
  https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/core/telco-core-ref-design-components.html#telco-core-scheduling_core-ref-design-components
Diff Output: diff -u -N /tmp/MERGED-852033724/nodetopology-openshift-io-v1_numaresourcesscheduler_numaresourcesscheduler /tmp/LIVE-1576982138/nodetopology-openshift-io-v1_numaresourcesscheduler_numaresourcesscheduler
--- /tmp/MERGED-852033724/nodetopology-openshift-io-v1_numaresourcesscheduler_numaresourcesscheduler    2025-07-14 13:07:54.085366263 +0000
+++ /tmp/LIVE-1576982138/nodetopology-openshift-io-v1_numaresourcesscheduler_numaresourcesscheduler    2025-07-14 13:07:54.085366263 +0000
@@ -4,4 +4,5 @@
   name: numaresourcesscheduler
 spec:
   imageSpec: registry.redhat.io/openshift4/noderesourcetopology-scheduler-rhel9:v4.18.0
+  logLevel: Normal
   schedulerName: topo-aware-scheduler**********************************

Version-Release number of selected component (if applicable):

OCP 4.18, cluster-compare 4.19

How reproducible:

 Apply the CR referring to: telco-core/configuration/reference-crs/required/scheduling/sched.yaml

Steps to Reproduce:

    1. oc apply -f telco-core/configuration/reference-crs/required/scheduling/sched.yaml
    2. oc cluster-compare -r metadata.yaml

Actual results:

    **********************************Cluster CR: nodetopology.openshift.io/v1_NUMAResourcesOperator_numaresourcesoperator Reference File: required/scheduling/nrop.yaml Description:   https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/core/telco-core-ref-design-components.html#telco-core-scheduling_core-ref-design-components Diff Output: diff -u -N /tmp/MERGED-3051149764/nodetopology-openshift-io-v1_numaresourcesoperator_numaresourcesoperator /tmp/LIVE-3422791799/nodetopology-openshift-io-v1_numaresourcesoperator_numaresourcesoperator --- /tmp/MERGED-3051149764/nodetopology-openshift-io-v1_numaresourcesoperator_numaresourcesoperator    2025-07-14 13:07:54.094366304 +0000 +++ /tmp/LIVE-3422791799/nodetopology-openshift-io-v1_numaresourcesoperator_numaresourcesoperator    2025-07-14 13:07:54.094366304 +0000 @@ -3,6 +3,7 @@  metadata:    name: numaresourcesoperator  spec: +  logLevel: Normal    nodeGroups:    - config:        infoRefreshMode: Periodic**********************************Cluster CR: nodetopology.openshift.io/v1_NUMAResourcesScheduler_numaresourcesscheduler Reference File: required/scheduling/sched.yaml Description:   https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/core/telco-core-ref-design-components.html#telco-core-scheduling_core-ref-design-components Diff Output: diff -u -N /tmp/MERGED-852033724/nodetopology-openshift-io-v1_numaresourcesscheduler_numaresourcesscheduler /tmp/LIVE-1576982138/nodetopology-openshift-io-v1_numaresourcesscheduler_numaresourcesscheduler --- /tmp/MERGED-852033724/nodetopology-openshift-io-v1_numaresourcesscheduler_numaresourcesscheduler    2025-07-14 13:07:54.085366263 +0000 +++ /tmp/LIVE-1576982138/nodetopology-openshift-io-v1_numaresourcesscheduler_numaresourcesscheduler    2025-07-14 13:07:54.085366263 +0000 @@ -4,4 +4,5 @@    name: numaresourcesscheduler  spec:    imageSpec: registry.redhat.io/openshift4/noderesourcetopology-scheduler-rhel9:v4.18.0 +  logLevel: Normal    schedulerName: topo-aware-scheduler**********************************

Expected results:

 No diff, for defaults.

Additional info:

  N.A.

links to

openshift-kni/telco-reference#384: telco-core: OCPBUGS-59293: cluster compare to accept logLevel field in nrop

Assignee:: Abraham Miller

Reporter:: Simone Ferlin-Reiter

Need Info From:: None

Contributors:: None

QA Contact:: Bahaa Azem

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2025/07/14 1:15 PM

Updated:: 2025/10/07 8:15 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates