Bug 525470
| Summary: | VM configuration status changes are not immediately visible in condor_status | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Luigi Toscano <ltoscano> |
| Component: | condor | Assignee: | Timothy St. Clair <tstclair> |
| Status: | CLOSED ERRATA | QA Contact: | Luigi Toscano <ltoscano> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 1.2 | CC: | lbrindle, matt, tstclair |
| Target Milestone: | 1.2 | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Fix should be in 7.4.0-0.1 | Doc Type: | Bug Fix |
| Doc Text: |
Grid bug fix
C: VM support disabled (xend/libvirtd not running) and then enabled again after the status interval has elapsed
C: The new status information will not be sent to the collector
F: Status updates of VM support are made immediately visible to the Collector.
R: Condor_status now reports the current status
If VM support was disabled (xend/libvirtd not running) and then enabled again after the status interval had elapsed, the new status information was not being sent to the collector. Status updates of VM support were changed, and made immediately visible to the Collector. The condor_status command now reports the current status correctly.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-12-03 09:20:07 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 497881, 527551 | ||
|
Description
Luigi Toscano
2009-09-24 14:05:13 UTC
Initial Investigation:
I've often found that the variables can be misleading and when searching through the manual and code I found the following
-------- Begin Manual Excerpt (Note the **)
VM_RECHECK_INTERVAL
An integer number of seconds that defaults to 600 (ten minutes), representing the amount of time the condor_startd waits after a virtual machine error as reported by the condor_starter, and before checking a final time on the status of the virtual machine. If the check fails, Condor disables starting any new vm universe jobs by removing the **VM_Type** attribute from the machine ClassAd.
-------- End Manual Excerpt
When I looked into the code and re-read the statement it is rather literal, it only adjusts the VM_Type attribute. It appears to me that HasVM will be updated the next time the classAd is "published", which it appears can happen for several reasons.
If we desire faster acknowledgement via this attribute, we can adjust, but as it stands I do not see a bug with the variable.
== Feedback is solicited ==
Patch went upstream on 10/4/09 Fix should be in 7.4.0-0.6 Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: please see bug summary. Status updates of VM support is immediately visible to Collector. Verified on RHEL 5.4, i386 Xen, x86_64 Xen, x86_64 KVM. condor-vm-gahp-7.4.1-0.4.el5 condor-7.4.1-0.4.el5 Changing the status to VERIFIED. Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1,8 @@ -please see bug summary.+Grid bug fix + +C: VM support disabled (xend/libvirtd not running) and then enabled again after the status interval has elapsed +C: The new status information will not be sent to the collector +F: Status updates of VM support are made immediately visible to the Collector. +R: Condor_status now reports the current status + +If VM support was disabled (xend/libvirtd not running) and then enabled again after the status interval had elapsed, the new status information was not being sent to the collector. Status updates of VM support were changed, and made immediately visible to the Collector. The condor_status command now reports the current status correctly. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1633.html |