vexxhost / vexxhost/migratekit
Wrong endpoint
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 138
- Forks
- 40
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Hello, I'm testing migratekit on OVH Public Cloud; I set the variables in openrc.sh and I can connect from cli with openstack client; when I perform a migration, the process starts correctly, runs the snapshot on esxi, connects to the openstack instance but then gives me this error:
Creating snapshot 100% [=================================================================================] (100/100) [0s:0s]
WARN[0004] Change ID mismatch, full copy needed currentChangeId= snapshotChangeId="52 ca 91 a0 75 e3 bf 62-d0 0a 94 f0 fe 13 c0 e3/65"
INFO[0004] Attaching volume volume_id=***
INFO[0006] Detected instance UUID, attaching volume... instance_uuid=xyzzy***
Removing snapshot 100% [=================================================================================] (100/100) [1s:0s]
Error: Expected HTTP response code [200] when accessing [POST https://compute.uk1.cloud.ovh.net/v2.1//servers/a/os-volume_attachments], but got 404 instead: {"itemNotFound": {"code": 404, "message": "Instance xyzzy** could not be found."}}
The problem is that the region is SBG7 and the correct url is: https://compute.sbg7.cloud.ovh.net/v2.1/******/servers/a*****/os-volume_attachments. For now, I haven't found a way to fix.
Thank you.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the migration's OpenStack endpoint and region handling after the variables in openrc.sh are loaded, comparing the failing uk1 URL with the required sbg7 URL. Confirm completion by reproducing the migration against OVH Public Cloud and verifying that volume attachment uses the instance's regional endpoint without the 404 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100