René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Unable to migrate instance that came from an external KVM host","articleBody":"\u003c!--\r\nVerify first that your issue/request is not already reported on GitHub.\r\nAlso test if the latest release and main branch are affected too.\r\nAlways add information AFTER of these HTML comments, but no need to delete the comments.\r\n--\u003e\r\n\r\n##### ISSUE TYPE\r\n\u003c!-- Pick one below and delete the rest --\u003e\r\n * Bug Report\r\n\r\n##### COMPONENT NAME\r\n\u003c!--\r\nCategorize the issue, e.g. API, VR, VPN, UI, etc.\r\n--\u003e\r\n~~~\r\nMigration to other host\r\n~~~\r\n\r\n##### CLOUDSTACK VERSION\r\n\u003c!--\r\nNew line separated list of affected versions, commit ID for issues on main branch.\r\n--\u003e\r\n\r\n~~~\r\n4.19.0\r\n~~~\r\n\r\n##### CONFIGURATION\r\n\u003c!--\r\nInformation about the configuration if relevant, e.g. basic network, advanced networking, etc.  N/A otherwise\r\n--\u003e\r\nLocal storage on VM hosts\r\n\r\n##### OS / ENVIRONMENT\r\n\u003c!--\r\nInformation about the environment if relevant, N/A otherwise\r\n--\u003e\r\nUbuntu 22.04 on all hosts\r\n\r\n##### SUMMARY\r\n\u003c!-- Explain the problem/feature briefly --\u003e\r\nWhen trying to migrate an instance to a different host that was migrated from an external KVM host before, it errors out and won't migrate.\r\n\r\n##### STEPS TO REPRODUCE\r\n\u003c!--\r\nFor bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.\r\n\r\nFor new features, show how the feature would be used.\r\n--\u003e\r\n\r\n\u003c!-- Paste example playbooks or commands between quotes below --\u003e\r\n~~~\r\nMigrate a VM from an external KVM host to Cloudstack, and then try to migrate that same instance to a different host.\r\n~~~\r\n\r\n\u003c!-- You can also paste gist.github.com links for larger files --\u003e\r\n\r\n##### EXPECTED RESULTS\r\n\u003c!-- What did you expect to happen when running the steps above? --\u003e\r\n\r\n~~~\r\nThat it migrates without issues\r\n~~~\r\n\r\n##### ACTUAL RESULTS\r\n\u003c!-- What actually happened? --\u003e\r\n\r\n\u003c!-- Paste verbatim command output between quotes below --\u003e\r\n~~~\r\nIt errors out on \"Failed to migrate VM [VM instance {\"id\":116,\"instanceName\":\"i-8-115-VM\",\"type\":\"User\",\"uuid\":\"5056c82d-e436-408f-b4c7-e0be8229a1cd\"}] along with its volumes due to [java.lang.NullPointerException].\"\r\n\r\nHere is the log for this action: https://gist.github.com/pcfriek1987/ba7bb24a8a373e5c2abaa22e802316ec\r\n\r\nIt seems to have something to do with the template it gets assigned when migrated is my assumption, as all migrated vm's get the: kvm-default-vm-import-dummy-template or VM default import template as listed on the side.  \r\n\r\nWhen trying to migrate it, it says:\r\nCopying template [212] of volume [122] from source storage pool [5] to target storage pool [3].\r\n2024-03-24 00:28:17,788 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl] (Work-Job-Executor-73:ctx-6a8adbf6 job-980/job-981 ctx-23d85860) (logid:61b73463) template 212 is not in store:2, type:Image\r\n\r\nTemplate 212 is the dummy template according to MySQL.\r\n\r\nThis is kind of an issue since when migrating you cannot specify which server is should go too so instances you want to divide between physical servers you cannot move now. Instances created directly from CS work without issues.\r\n~~~\r\n","author":{"url":"https://github.com/pcfriek1987","@type":"Person","name":"pcfriek1987"},"datePublished":"2024-03-25T12:46:56.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/8827/cloudstack/issues/8827"}