Uploaded image for project: 'Migration Toolkit for Virtualization'
  1. Migration Toolkit for Virtualization
  2. MTV-4581

forklift-controller error "Could not set migration owner reference."

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 2.11.0
    • Controller
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False

      Description of problem:

      The issue occur when creating NAD and in different NS other than the provider and pointing in the networkmap to that NAD

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

      ├── OCP version: 4.20.14
      ├── MTV version: 2.11.0 (redhat-osbs-on-pr-1c468833dd2e1cce3ebd2d882ecfdc21a22f87be)
      └── CNV version: 4.20.6

      How reproducible:

      Always / N%
      

      Steps to Reproduce:

      1. oc new-project mtv-ameen
      2. oc apply -f ../scripts/networkattachmentdefinition-mybridge1.yaml 
      3. oc new-project mtv-test
      4. oc mtv create provider --name host --type openshift
      5. oc mtv create provider vmware-7 --type vsphere --url https://x.x.x.x/sdk --username 'user' --password 'password' --vddk-init-image 'vddk-image' --cacert "$(echo | openssl s_client -showcerts -connect x.x.x.x:443 2>/dev/null | openssl x509)"
      6. oc mtv create plan --name plan-ameen-win2019-multi-ips-2nics --source vmware-7 --vms "ameen-WIN2019_multi_IPs_2nics" --warm   --network-pairs "VM Network:default, Mgmt Network:mtv-ameen/mybridge1"

      Actual results:

      New error appear in the forklift-controller
      {   "level": "error",   "ts": "2026-02-18 13:42:51.382",   "logger": "migration|7lnv2",   "msg": "Could not set migration owner reference.",   "migration": {     "name": "plan-ameen-win2019-multi-ips-2nics-fjghm",     "namespace": "mtv-test"   },   "error": "Operation cannot be fulfilled on migrations.forklift.konveyor.io \"plan-ameen-win2019-multi-ips-2nics-fjghm\": the object has been modified; please apply your changes to the latest version and try again",   "stacktrace": "github.com/kubev2v/forklift/pkg/controller/migration.Reconciler.Reconcile\n\t/app/pkg/controller/migration/controller.go:138\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Reconcile\n\t/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:119\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler\n\t/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:334\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem\n\t/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:294\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.2\n\t/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:255"

      Expected results:

      No errors

      Additional info:

      This behavior keeps the Plan in "NotReady" status (due to having the NAD and the Plan in different Namespaces) - which is expected 

       

              yzamir@redhat.com Yaacov Zamir
              rh-ee-abarakat Ameen Barakat
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: