| Summary: | remote command worked with expected output, but event history returned error | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | DzungDo <ddo> |
| Component: | API | Assignee: | Tomas Lestach <tlestach> |
| Status: | CLOSED NOTABUG | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 550 | CC: | cperry |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-03 11:13:26 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: | |
| Bug Depends On: | |||
| Bug Blocks: | 462714 | ||
|
Description
DzungDo
2013-08-29 20:59:14 UTC
Well, the status of the return command depends on the return code of the remote command. On my machine: * if there're no updates: # yum check-update > /dev/null; echo $? 0 * if there're updates available: # yum check-update > /dev/null; echo $? 100 So, if your script returns a non-zero value, the remote command is considered as failed. Recommended usage: ======================================================= #!/bin/sh yum check-update RET=$? if [ $RET -eq 100 ]; then exit 0; else exit $RET; fi ======================================================= Closing as NOTABUG. |