Bug 236595
Summary: | Guest Reboot Fails, 30 Second Shutdown Timeout | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Devan Goodwin <dgoodwin> | ||||
Component: | xen | Assignee: | Daniel Berrangé <berrange> | ||||
Status: | CLOSED ERRATA | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5.0 | CC: | chuck.morrison, xen-maint | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | RHEA-2007-0635 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-11-07 17:10:18 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: | |||||||
Attachments: |
|
Description
Devan Goodwin
2007-04-16 17:41:19 UTC
I searched for the 'shutdown timeout expired' message and found it in ./python/xen/xend/XendDomainInfo.py It checks to see if the domain has been shutting down for > SHUTDOWN_TIMEOUT, and if so kills it. if self.shutdownStartTime: timeout = (SHUTDOWN_TIMEOUT - time.time() + self.shutdownStartTime) if timeout < 0: log.info( "Domain shutdown timeout expired: name=%s id=%s", self.info['name'], self.domid) self.destroy() SHUTDOWN_TIMEOUT is set to '30' at the top of the file. I reckon we need to bump this up to 60 seconds at least. Flagging the bug as proposed for RHEL 5.1. Seems like easy modification. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. *** Bug 248942 has been marked as a duplicate of this bug. *** Upstream Xen has removed the shutdown timer completely, allowing the admin to deal with non-responsive guests as they see fit. They can run a 'destroy' manually if desirable, or take other action. changeset: 15179:152dc0d812b2 user: kfraser date: Wed May 30 10:06:23 2007 +0100 summary: xend: Don't destroy domains on shutdown timeout. Created attachment 159606 [details]
Don't destroy guests on reboot timeout
This patch is a copy of upstream code ported to RHEL-5 tree
Patch applied in: * Mon Aug 27 2007 Daniel P. Berrange <berrange> - 3.0.3-37.el5 - Don't destroy guest after shutdown timeout (rhbz #236595) 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 the 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-2007-0635.html |