k8scoder192

Hi @awels and @mhenriks any progress on this? Looks like Kubevirt added support for this https://github.com/kubevirt/kubevirt/pull/5563

@mhenriks thanks for looking into this. I would vote for option C, it's more secure and one less thing CDI has to manage/do with respect to secret replication.

@qinqon did you look at the full logs? It's **NOT** due to the probes. The probes come back extremely quick. Something else is wrong. **Edit** I also noticed this is...

@awels looking at my example above, the request SRC = DST size **DV clone** ``` apiVersion: cdi.kubevirt.io/v1beta1 kind: DataVolume metadata: name: ubuntu22-trident-v2 namespace: test1 spec: source: pvc: name: ubuntu22-trident namespace:...

@akalenyu Understood, thanks for the clarification. However, as mentioned I see no reason why CDI reverted to using network cloning. I am able to do csi-clone manually with no issues,...

> Only 2.2.13 has the `NETLINK_GET_STRICT_CHK` fix. The 2.2.12 and .11 is still using old nispor 1.2.10. :( I haven't release that to OCP yet. @cathay4t can we please expedite...

@qinqon yes in the morning. Please let's not close until validated.

@qinqon **Still seeing the issue; loops multiple times** `` {"level":"info","ts":"2023-07-25T19:16:17.428Z","logger":"probe","msg":"default gw missing","path":"routes.running.next-hop-address","table-id":254} {"level":"error","ts":"2023-07-25T19:16:17.428Z","logger":"probe","msg":"failed to retrieve default gw","error":"default gw missing","errorVerbose":"default gw missing\ngithub.com/nmstate/kubernetes-nmstate/pkg/probe.defaultGw\n\t/opt/app-root/src/pkg/probe/probes.go:167\ngithub.com/nmstate/kubernetes-nmstate/pkg/probe.runPing\n\t/opt/app-root/src/pkg/probe/probes.go:184\ngithub.com/nmstate/kubernetes-nmstate/pkg/probe.pingCondition.func1\n\t/opt/app-root/src/pkg/probe/probes.go:174\nk8s.io/apimachinery/pkg/util/wait.ConditionFunc.WithContext.func1\n\t/opt/app-root/src/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:220\nk8s.io/apimachinery/pkg/util/wait.runConditionWithCrashProtectionWithContext\n\t/opt/app-root/src/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:233\nk8s.io/apimachinery/pkg/util/wait.WaitForWithContext\n\t/opt/app-root/src/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:660\nk8s.io/apimachinery/pkg/util/wait.poll\n\t/opt/app-root/src/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:594\nk8s.io/apimachinery/pkg/util/wait.PollImmediateWithContext\n\t/opt/app-root/src/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:526\nk8s.io/apimachinery/pkg/util/wait.PollImmediate\n\t/opt/app-root/src/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:512\ngithub.com/nmstate/kubernetes-nmstate/pkg/probe.Select\n\t/opt/app-root/src/pkg/probe/probes.go:277\ngithub.com/nmstate/kubernetes-nmstate/pkg/client.ApplyDesiredState\n\t/opt/app-root/src/pkg/client/client.go:159\ngithub.com/nmstate/kubernetes-nmstate/controllers/handler.(*NodeNetworkConfigurationPolicyReconciler).Reconcile\n\t/opt/app-root/src/controllers/handler/nodenetworkconfigurationpolicy_controller.go:226\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/opt/app-root/src/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:121\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/opt/app-root/src/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:320\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/opt/app-root/src/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:273\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/opt/app-root/src/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:234\nruntime.goexit\n\t/usr/lib/golang/src/runtime/asm_amd64.s:1571","stacktrace":"github.com/nmstate/kubernetes-nmstate/pkg/probe.runPing\n\t/opt/app-root/src/pkg/probe/probes.go:186\ngithub.com/nmstate/kubernetes-nmstate/pkg/probe.pingCondition.func1\n\t/opt/app-root/src/pkg/probe/probes.go:174\nk8s.io/apimachinery/pkg/util/wait.ConditionFunc.WithContext.func1\n\t/opt/app-root/src/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:220\nk8s.io/apimachinery/pkg/util/wait.runConditionWithCrashProtectionWithContext\n\t/opt/app-root/src/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:233\nk8s.io/apimachinery/pkg/util/wait.WaitForWithContext\n\t/opt/app-root/src/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:660\nk8s.io/apimachinery/pkg/util/wait.poll\n\t/opt/app-root/src/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:594\nk8s.io/apimachinery/pkg/util/wait.PollImmediateWithContext\n\t/opt/app-root/src/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:526\nk8s.io/apimachinery/pkg/util/wait.PollImmediate\n\t/opt/app-root/src/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:512\ngithub.com/nmstate/kubernetes-nmstate/pkg/probe.Select\n\t/opt/app-root/src/pkg/probe/probes.go:277\ngithub.com/nmstate/kubernetes-nmstate/pkg/client.ApplyDesiredState\n\t/opt/app-root/src/pkg/client/client.go:159\ngithub.com/nmstate/kubernetes-nmstate/controllers/handler.(*NodeNetworkConfigurationPolicyReconciler).Reconcile\n\t/opt/app-root/src/controllers/handler/nodenetworkconfigurationpolicy_controller.go:226\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/opt/app-root/src/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:121\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/opt/app-root/src/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:320\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/opt/app-root/src/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:273\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/opt/app-root/src/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:234"} `` exec into the handler pod; I see new...

@cathay4t can you **please** look into this? It's still failing with the kernel version listed

Sure but the problem still exists in the latest nmstate release. Please have someone look into this On Wed, Aug 23, 2023, 8:50 AM Gris Ge ***@***.***> wrote: > The...