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

Sunstone initiate new VM with wrong placement (wrong HOST_ID) #6845

Open
3 tasks
Franco-Sparrow opened this issue Jan 6, 2025 · 0 comments
Open
3 tasks

Comments

@Franco-Sparrow
Copy link

Description

FSunstone is not placing the new VMs on a specified HOST_ID.

To Reproduce

Instantiate a new VM and place it on a specific host. Try it at least twice to confirm the issue.

Selecting a specific host and cluster:

400224318-49393723-0161-4124-8a09-84182f260cd3

The VM is placed on different host:

400224475-d3750455-eb73-417d-bf1a-ac24f841e33c

This introduce another issue. Check here please.

Expected behavior

The VM should be placed on the specified HOST_ID.

Details

  • Affected Component: [FSunstone, Scheduler]
  • Hypervisor: [KVM]
  • Version: [6.10.2]

Additional context
Add any other context about the problem here.

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant