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

Failed to apply StressChaos in minikube with qemu driver: controller is not supported #4406

Open
Tracked by #4405
kaaass opened this issue Apr 28, 2024 · 1 comment · May be fixed by #4407
Open
Tracked by #4405

Failed to apply StressChaos in minikube with qemu driver: controller is not supported #4406

kaaass opened this issue Apr 28, 2024 · 1 comment · May be fixed by #4407

Comments

@kaaass
Copy link

kaaass commented Apr 28, 2024

Bug Report

What version of Kubernetes are you using?

v1.28.3

What version of Chaos Mesh are you using?

Controller manager Version: version.Info{GitVersion:"chart-2.6.3", GitCommit:"b159d1c5a361ca350ca7789c9eb7fc917479db39", BuildDate:"2024-01-23T15:04:54Z", GoVersion:"go1.19.7", Compiler:"gc", Platform:"linux/arm64"}

What did you do? / Minimal Reproducible Example

  1. Start cluster using minikube start --driver=qemu --network=socket_vmnet
  2. Install with helm charts: helm install chaos-mesh chaos-mesh/chaos-mesh -n=chaos-mesh --version 2.6.3 --create-namespace
  3. Start a StressChaos experiment

What did you expect to see?
The experiment started and the stress been injected.

What did you see instead?
The experiment keeps in "Injecting" state. And the error messages in Event says Failed to apply chaos: rpc error: code = Unknown desc = load cgroup v1 manager, pid 48805, ...: controller is not supported

$ kubectl describe -n my-namespace stresschaos.chaos-mesh.org
Name:         cpu-2024-04-28t16.55.42z
Namespace:    my-namespace
Labels:       <none>
Annotations:  <none>
API Version:  chaos-mesh.org/v1alpha1
Kind:         StressChaos
Metadata:
  Creation Timestamp:  2024-04-28T16:55:43Z
  Finalizers:
    chaos-mesh/records
  Generation:        24
  Resource Version:  2088
  UID:               a9f517d0-1f36-4c92-b78e-54fcf56a7550
Spec:
  Duration:  5m
  Mode:      all
  Selector:
    Label Selectors:
      App:  nginx
    Namespaces:
      my-namespace
  Stressors:
    Cpu:
      Load:     5
      Workers:  1
Status:
  Conditions:
    Status:  True
    Type:    Selected
    Status:  False
    Type:    AllInjected
    Status:  True
    Type:    AllRecovered
    Status:  False
    Type:    Paused
  Experiment:
    Container Records:
      Events:
        Message:        rpc error: code = Unknown desc = load cgroup v1 manager, pid 31390, cpu path /kubepods/besteffort/pod936b79d1-f6cf-4716-82e8-d302aef341d2/fc121824c882c4280adf95010c74233e8420c4eec617433f4029b0fd3477aed2, memory path /kubepods/besteffort/pod936b79d1-f6cf-4716-82e8-d302aef341d2/fc121824c882c4280adf95010c74233e8420c4eec617433f4029b0fd3477aed2: controller is not supported
        Operation:      Apply
        Timestamp:      2024-04-28T16:55:43Z
        Type:           Failed
      Id:               my-namespace/nginx-deployment-7c79c4bf97-rzrqd/nginx
      Injected Count:   0
      Phase:            Not Injected
      Recovered Count:  0
      Selector Key:     .
    Desired Phase:      Run
Events:
  Type     Reason           Age   From            Message
  ----     ------           ----  ----            -------
  Normal   FinalizerInited  118s  initFinalizers  Finalizer has been inited
  Normal   Updated          118s  initFinalizers  Successfully update finalizer of resource
  Normal   Started          118s  desiredphase    Experiment has started
  Normal   Updated          118s  desiredphase    Successfully update desiredPhase of resource
  Warning  Failed           118s  records         Failed to apply chaos: rpc error: code = Unknown desc = load cgroup v1 manager, pid 31390, cpu path /kubepods/besteffort/pod936b79d1-f6cf-4716-82e8-d302aef341d2/fc121824c882c4280adf95010c74233e8420c4eec617433f4029b0fd3477aed2, memory path /kubepods/besteffort/pod936b79d1-f6cf-4716-82e8-d302aef341d2/fc121824c882c4280adf95010c74233e8420c4eec617433f4029b0fd3477aed2: controller is not supported
  Normal   Updated          118s  records         Successfully update records of resource

Output of chaosctl

@kaaass
Copy link
Author

kaaass commented Apr 28, 2024

I have already found the bug and will PR for it soon! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant