Bug 617305
| Summary: | db-control returns 1 on success | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Rob Marti <robmartiwork> |
| Component: | Usability | Assignee: | Jan Pazdziora (Red Hat) <jpazdziora> |
| Status: | CLOSED ERRATA | QA Contact: | Jiri Kastner <jkastner> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 530 | CC: | cperry, jhutar, jkastner, jpazdziora, mmraka, psklenar |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | spacewalk-web-1.2.7-9 | Doc Type: | Bug Fix |
| Doc Text: |
When running db-control with the "start" or "stop" command, the utility incorrectly returned 1, even though the operation actually succeeded. This error no longer occurs, and the db-control utility now always returns a proper exit status.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-12-21 12:25:21 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: | 462714 | ||
|
Description
Rob Marti
2010-07-22 18:29:31 UTC
Taking. *** Bug 527200 has been marked as a duplicate of this bug. *** Fixed in Spacewalk master, 23d89f5b302f2a0ed55249f2cfd0b6be2e31f74d. Cherry picked to SATELLITE-5.4 as
commit 5d457754dad8444f04b034b1e9f0d3788ca3335c
617305 - make sure exit value 0 is returned by all db-control commands by default.
Without explicit return 0, the result of last command is returned,
which for print is generaly 1.
(cherry picked from commit 23d89f5b302f2a0ed55249f2cfd0b6be2e31f74d)
The db-control status returns 0 when the database is running. Since you've initiated stop, it's correct that it does not return 0. Moving back to ON_QA.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
When running db-control with the "start" or "stop" command, the utility incorrectly returned 1 (operation not permitted), even though the operation actually succeeded. This error no longer occurs, and the db-control utility now always returns a proper exit status.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-When running db-control with the "start" or "stop" command, the utility incorrectly returned 1 (operation not permitted), even though the operation actually succeeded. This error no longer occurs, and the db-control utility now always returns a proper exit status.+When running db-control with the "start" or "stop" command, the utility incorrectly returned 1, even though the operation actually succeeded. This error no longer occurs, and the db-control utility now always returns a proper exit status.
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/RHBA-2010-1001.html *** Bug 673049 has been marked as a duplicate of this bug. *** |