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

Error: open /dev/disk/by-id/: no such file or directory #48

Open
igorfilipovic opened this issue Nov 7, 2024 · 3 comments
Open

Error: open /dev/disk/by-id/: no such file or directory #48

igorfilipovic opened this issue Nov 7, 2024 · 3 comments

Comments

@igorfilipovic
Copy link

Hi, I'm trying to test migratekit but I'm stuck when running migrate phase with message:
"Error: open /dev/disk/by-id/: no such file or directory", it happens after Removing snapshot 100%.

Can you please advise ?

Thank you in advance and best regards,

Igor

@igorfilipovic
Copy link
Author

I can pass this step if I manually attach volume (which was created by migratekit) to instance on which migratekit is started, but shouldn't this mount be done automatically? Or am I mistaking or missing something? I can't find nothing in readme which is related to openstack configuration or requirements.
BR, Igor

@doskelion
Copy link

Maybe the same case. I had the same issue and knowing that migratekit tool has to run on a VM thats running in openstack environment. Same as you, couldn't find that documentation anywhere.

@igorfilipovic
Copy link
Author

Ok, I managed to finish the migration for two test virtual machines. In short, openstack client and OS environment (with admin rights) must be configured on instance which is running on openstack. On that same instance files from VMware-vix-disklib-8.0.3-23950268.x86_64.tar.gz must be unpacked and copied in /usr/lib64/vmware-vix-disklib. Be sure to use version 8.0.3, I had a problem with 8.0 release (missing support for GLIBCXX_3.4.30). Besides that, on the same instance docker must be installed. Virtual machine on vmware which is subject for migration must have CTK enabled globaly and for all disks. After those settings, migration and cutover phases were succesfull. After powering on migrated instance on openstack, you should manually adjust network configuration via console (tested on ubuntu, maybe for some other distribution cloud-init do the job, still not sure).
Good luck.
BR, Igor

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

No branches or pull requests

2 participants