Feature #3638
Make clear when a VM can't be deployed because a system DS is missing
| Status: | Closed | Start date: | 02/26/2015 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Scheduler | |||
| Target version: | Release 4.14 | |||
| Resolution: | fixed | Pull request: |
Description
If a VM has a vnet and image DS in different clusters, it can't even be instantiated.
If there isn't a host with enough capacity, the sched adds a message to the VM template:
Thu Feb 26 11:03:03 2015 : No host with enough capacity to deploy the VM
But when there isn't a system DS, the scheduler just says so in the sched.log file. There isn't a warning anywhere in the VM template or VM log
VM 2: No suitable System DS found for Host: 0. Filtering out host.
History
#1
Updated by Ruben S. Montero over 6 years ago
- Target version set to Release 4.14
#2
Updated by Ruben S. Montero over 6 years ago
- Tracker changed from Backlog to Feature
#3
Updated by Ruben S. Montero over 6 years ago
- Status changed from Pending to New
#4
Updated by Carlos Martín about 6 years ago
This is fixed, at lest in master. Now the VM contains:
SCHED_MESSAGE="Tue Apr 21 16:35:09 2015 : No system datastore meets SCHED_DS_REQUIREMENTS: !(PUBLIC_CLOUD = YES)"
#5
Updated by Carlos Martín about 6 years ago
- Status changed from New to Closed
- Resolution set to fixed