Baike.dev
Log in
Back to tool/Back to issues
#3746·vcluster

[0.33.1] unhandled errors repeating on cronjobs

Author: pasztorlCreated Mar 28, 2026Updated Sep 16, 2026
LabelsSyncingkind-bug

What happened?

Hi, I see this in vcluster logs repeating continuosly:

2026-03-28 17:13:15	INFO	commandwriter/commandwriter.go:128	Unhandled Error	{"component": "vcluster", "component": "controller-manager", "location": "cronjob_controllerv2.go:174", "err": "error syncing CronJobController example/controller, requeuing: Operation cannot be fulfilled on cronjobs.batch \"example\": the object has been modified; please apply your changes to the latest version and try again", "logger": "UnhandledError"}
2026-03-28 17:13:19	INFO	commandwriter/commandwriter.go:128	Unhandled Error	{"component": "vcluster", "component": "controller-manager", "location": "cronjob_controllerv2.go:174", "err": "error syncing CronJobController example/controller, requeuing: Operation cannot be fulfilled on cronjobs.batch \"example\": the object has been modified; please apply your changes to the latest version and try again", "logger": "UnhandledError"}
2026-03-28 17:14:15	INFO	commandwriter/commandwriter.go:128	Unhandled Error	{"component": "vcluster", "component": "controller-manager", "location": "cronjob_controllerv2.go:174", "err": "error syncing CronJobController example/controller, requeuing: Operation cannot be fulfilled on cronjobs.batch \"example\": the object has been modified; please apply your changes to the latest version and try again", "logger": "UnhandledError"}
2026-03-28 17:14:15	INFO	commandwriter/commandwriter.go:128	Unhandled Error	{"component": "vcluster", "component": "controller-manager", "location": "cronjob_controllerv2.go:174", "err": "error syncing CronJobController example/controller, requeuing: Operation cannot be fulfilled on cronjobs.batch \"example\": the object has been modified; please apply your changes to the latest version and try again", "logger": "UnhandledError"}
2026-03-28 17:14:18	INFO	commandwriter/commandwriter.go:128	Unhandled Error	{"component": "vcluster", "component": "controller-manager", "location": "cronjob_controllerv2.go:174", "err": "error syncing CronJobController example/controller, requeuing: Operation cannot be fulfilled on cronjobs.batch \"example\": the object has been modified; please apply your changes to the latest version and try again", "logger": "UnhandledError"}
2026-03-28 17:14:22	INFO	commandwriter/commandwriter.go:128	Unhandled Error	{"component": "vcluster", "component": "controller-manager", "location": "cronjob_controllerv2.go:174", "err": "error syncing CronJobController example/controller, requeuing: Operation cannot be fulfilled on cronjobs.batch \"example\": the object has been modified; please apply your changes to the latest version and try again", "logger": "UnhandledError"}
2026-03-28 17:15:19	INFO	commandwriter/commandwriter.go:128	Unhandled Error	{"component": "vcluster", "component": "controller-manager", "location": "cronjob_controllerv2.go:174", "err": "error syncing CronJobController example/controller, requeuing: Operation cannot be fulfilled on cronjobs.batch \"example\": the object has been modified; please apply your changes to the latest version and try again", "logger": "UnhandledError"}

cronjobs working as expected

What did you expect to happen?

vcluster does not log continuosly unhandled errors about cronjobs

How can we reproduce it (as minimally and precisely as possible)?

installed latest vcluster on a kubeadm kubernetes cluster 1.33.7

Anything else we need to know?

No response

Host cluster Kubernetes version

1.33.7

vcluster version

0.33.1

VCluster Config

controlPlane:
  advanced:
    virtualScheduler:
      enabled: false
  backingStore:
    etcd:
      deploy:
        enabled: true
        statefulSet:
          highAvailability:
            replicas: 3
      embedded:
        enabled: false
  coredns:
    deployment:
      replicas: 2
    embedded: false
    enabled: true
  distro:
    k8s:
      enabled: true
      resources:
        limits:
          memory: 4Gi
  hostPathMapper:
    enabled: true
  ingress:
    enabled: true
  service:
    enabled: true
    spec:
      type: ClusterIP
  statefulSet:
    highAvailability:
      replicas: 2
    persistence:
      volumeClaim:
        enabled: auto
        size: 1Gi
        storageClass: gpc16
    resources:
      limits:
        ephemeral-storage: 8Gi
        memory: 4Gi
    scheduling:
      podManagementPolicy: Parallel
integrations:
  certManager:
    enabled: false
  externalSecrets:
    enabled: false
  kubeVirt:
    enabled: false
  metricsServer:
    enabled: false
    nodes: false
    pods: false
sync:
  fromHost:
    csiDrivers:
      enabled: auto
    csiNodes:
      enabled: auto
    csiStorageCapacities:
      enabled: auto
    events:
      enabled: true
    ingressClasses:
      enabled: false
    nodes:
      clearImageStatus: true
      enabled: true
      syncBackChanges: true
    runtimeClasses:
      enabled: false
    secrets:
      enabled: false
    storageClasses:
      enabled: true
    volumeSnapshotClasses:
      enabled: true
  toHost:
    configMaps:
      all: false
      enabled: true
    endpoints:
      enabled: true
    persistentVolumeClaims:
      enabled: true
    persistentVolumes:
      enabled: true
    podDisruptionBudgets:
      enabled: true
    pods:
      enabled: true
    secrets:
      all: false
      enabled: true
    services:
      enabled: true
    storageClasses:
      enabled: false
    volumeSnapshotContents:
      enabled: true
    volumeSnapshots:
      enabled: true

Source: loft-sh/vcluster

View original on GitHubView discussion on GitHub