Bug 1001986
| Summary: | User has no information that service ovirt-scheduler-proxy is not running, thus his scheduler is not used. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Ondra Machacek <omachace> | ||||
| Component: | ovirt-scheduler-proxy | Assignee: | Martin Sivák <msivak> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Artyom <alukiano> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.3.0 | CC: | acathrow, dfediuck, eedri, gchaplik, iheim, mavital | ||||
| Target Milestone: | --- | Keywords: | Triaged | ||||
| Target Release: | 3.3.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | sla | ||||||
| Fixed In Version: | is25 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-02-05 07:22:46 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Ondra Machacek
2013-08-28 09:19:37 UTC
Checked on is18 Vm is failed to run with message "Failed to run VM vm_proxy (User: admin@internal)." In engine log "Could not communicate with the external scheduler while running weight modules" Please add appropriate message to events. If no internal scoring function was selected and the external scheduler returned no results a situation occured where no host would be selected at all Added a fix Checked on is21 After reproducing steps in description: Vm success to run with ovirt-scheduler-proxy stopped Created attachment 818141 [details]
engine.log
(In reply to Artyom from comment #5) > Created attachment 818141 [details] > engine.log Artyom, a VM should be scheduled even if the the external proxy is down, since we can use which ever internal policy parts we have. So this is working be design. he question is if you got an indication on the scheduler being down. for example, are the external policy elements marked as disabled? There seems to be no indication of this in the engine. Moreover the user has a limited chance of spotting this as we do not use the external scheduler in canDoAction. Verified on is27, Cluster policy with external cost and filter functions, ovirt-scheduler-proxy stopped, vm run fine and also error message in engine events: "Failed to connect to external scheduler proxy. External filters, scoring functions and load balancing will not be performed." |