Bug 1150295
| Summary: | Schedule System Reboot does not complete | ||
|---|---|---|---|
| Product: | [Community] Spacewalk | Reporter: | Matthew <mattmadey> |
| Component: | WebUI | Assignee: | Stephen Herr <sherr> |
| Status: | CLOSED WONTFIX | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.2 | CC: | redhat, tlestach |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-31 14:13:50 UTC | Type: | Bug |
| 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: | 1484117 | ||
|
Description
Matthew
2014-10-07 20:53:32 UTC
What I see is: ====================================================================== Summary: System reboot scheduled by admin Details: This action will be executed after 10/30/14 6:00:00 AM EDT This action's status is: Completed. The client picked up this action on 10/30/14 11:02 AM The client completed this action on 10/30/14 4:48 PM Client execution returned "null" (code null) Time: 10/30/14 6:00:00 AM EDT ====================================================================== I scheduled the reboot action on WebUI at: 10/30/14 6:00:00 AM EDT I manually run rhn_check on the client at: 10/30/14 11:02 AM (we need to unify the timestamp format), so the reboot action was picked up and the reboot happened within 3 minutes Next rhn_check was run by the rhnsd daemon at: 10/30/14 4:48 PM (when the action was marked as completed.) The action completes. Unfortunately not right after the reboot, but with the upcoming rhn_check. The situation is not ideal, we know about the behavior, but we have no better solution for that. See https://www.redhat.com/archives/spacewalk-list/2014-October/msg00259.html for more information. For now I'm closing the BZ as WONTFIX. (As a workaround you may decrease the INTERVAL value in /etc/sysconfig/rhn/rhnsd file on the client machine and restart rhnsd service. The value represents number of minutes, how often rhn_check shall be run. But be careful with changing the value. The more client machines you have registered to the Spacewalk server, the bigger should be the value.) This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug. |