vexxhost / vexxhost/migratekit
Availability Zone flag not working?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 138
- Forks
- 40
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
I have an availability zone in my OpenStack cluster called 'central-red-v0-linux'. but when I specify
--availability-zone central-red-v0-linux
or
--availability-zone "central-red-v0-linux"
in my cutover command, the VM does not come up in that AZ. I don't receive any errors, it just seems to ignore the AZ flag.
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 at the cutover command's handling of the --availability-zone flag and reproduce the migration with central-red-v0-linux in an OpenStack cluster. Trace the selected availability zone through VM creation and verify that the VM is placed there; done when the flag is honored or a clear error is returned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100