Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to create a profile" err="unable to build DefaultEvictor plugin #1440

Closed
timetofaceit opened this issue Jun 13, 2024 · 2 comments · Fixed by #1452
Closed

Unable to create a profile" err="unable to build DefaultEvictor plugin #1440

timetofaceit opened this issue Jun 13, 2024 · 2 comments · Fixed by #1452
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@timetofaceit
Copy link

Hi!

I'm facing an error in Descheduler pod logs:

"unable to create a profile" err="unable to build DefaultEvictor plugin: unable to initialize \"DefaultEvictor\" plugin: indexer conflict: map[metadata.ownerReferences:{}]" profile="Descheduler"

I'm installing Descheduler via Helm Chart v0.30.1 with Deployment mode.

My policy config looks like this:

deschedulerPolicy:
  profiles:
    - name: "Descheduler"
      pluginConfig:
        - name: "DefaultEvictor"
          args:
            evictLocalStoragePods: false
            evictSystemCriticalPods: false
            ignorePvcPods: false
            evictFailedBarePods: false
            nodeFit: true
            minReplicas: 2
        - name: "RemoveDuplicates"
        - name: "LowNodeUtilization"
          args:
            thresholds:
              cpu : 30
              memory: 30
              pods: 20
            targetThresholds:
              cpu : 80
              memory: 80
              pods: 50
        - name: "HighNodeUtilization"
          args:
            thresholds:
              cpu : 80
              memory: 80
              pods: 50
        - name: "RemovePodsViolatingInterPodAntiAffinity"
        - name: "RemovePodsViolatingNodeTaints"
        - name: "RemovePodsViolatingNodeAffinity"
          args:
            nodeAffinityType:
              - "requiredDuringSchedulingIgnoredDuringExecution"
        - name: "RemovePodsViolatingTopologySpreadConstraint"
          args:
            topologyBalanceNodeFit: true
            constraints:
              - "DoNotSchedule"
              - "ScheduleAnyway"
      plugins:
        balance:
          enabled:
            - "RemoveDuplicates"
            - "LowNodeUtilization"
            - "HighNodeUtilization"
            - "RemovePodsViolatingTopologySpreadConstraint"
        deschedule:
          enabled:
            - "RemovePodsViolatingInterPodAntiAffinity"
            - "RemovePodsViolatingNodeAffinity"
            - "RemovePodsViolatingNodeTaints"

I also see that when pod starts, everything works fine until CronJob finishes... Then I'm starting to get these errors...

Maybe I'm configuring something wrong? 🤔

@timetofaceit timetofaceit added the kind/bug Categorizes issue or PR as related to a bug. label Jun 13, 2024
@ggggut
Copy link

ggggut commented Jun 26, 2024

It seems related to minReplicas. Removing it fixes the problem for me..

@a7i
Copy link
Contributor

a7i commented Jun 28, 2024

Thank you for reporting this @timetofaceit
/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants