-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-9.6, rhel-10.0
-
None
-
pcp-6.3.2-2.el10
-
No
-
Low
-
1
-
rhel-sst-pt-pcp
-
ssg_platform_tools
-
21
-
2
-
QE ack, Dev ack
-
False
-
-
No
-
Red Hat Enterprise Linux
-
PCP Sprint 13
-
Pass
-
Automated
-
Unspecified Release Note Type - Unknown
-
-
All
-
None
What were you trying to do that didn't work?
This is a follow-up of RHEL-56836. When pcp-xsos is run with an invalid argument, it correctly returns an error message (since pcp-6.3.2-1 build). However the exit/return code is "0". Similar utilities (like pcp-atop ) returns in such a situation an error code "1".
What is the impact of this issue to you?
If the pcp-xsos is used in a script, the invalid command seems to succeed even it failed.
Please provide the package NVR for which the bug is seen:
- pcp-6.3.2-1.el10
- pcp-6.3.2-1.el9
How reproducible is this bug?
Always
Steps to reproduce
- Install pcp-zeroconf
# yum install -y pcp-zeroconf
- Run the pcp-xsos with an invalid argument
# pcp xsos unknown_arg
- Check the error code
# echo $?
Expected results
The returned error code is != 0
Actual results
The returned error code == 0
- links to
-
RHSA-2024:142621 pcp bug fix and enhancement update