Bug 1685968 - ovirt-aaa-jdbc-tool return code 0 on failure
Summary: ovirt-aaa-jdbc-tool return code 0 on failure
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-extension-aaa-jdbc
Classification: oVirt
Component: General
Version: 1.1.9
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.3.2
: 1.1.10
Assignee: Martin Perina
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-06 12:08 UTC by Petr Matyáš
Modified: 2019-03-19 10:05 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-extension-aaa-jdbc-1.1.10
Clone Of:
Environment:
Last Closed: 2019-03-19 10:05:26 UTC
oVirt Team: Infra
Embargoed:
mperina: ovirt-4.3?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 98297 0 master MERGED core: Fix ovirt-aaa-jdbc-tool return code 2019-03-07 14:05:39 UTC
oVirt gerrit 98348 0 ovirt-engine-extension-aaa-jdbc-1.1 MERGED core: Fix ovirt-aaa-jdbc-tool return code 2019-03-08 09:18:49 UTC

Description Petr Matyáš 2019-03-06 12:08:52 UTC 
Description of problem:
When running ovirt-aaa-jdbc-tool expecting a failure I'm getting the failure in stderr, however the return code is 0 which means everything is OK.

Version-Release number of selected component (if applicable):
ovirt-engine-extension-aaa-jdbc-1.1.9-1.el7ev.noarch

How reproducible:
always

Steps to Reproduce:
1. ovirt-aaa-jdbc-tool group-manage useradd grupa --user=nope
2.
3.

Actual results:
return code 0

Expected results:
return code 1 or anything other than 0

Additional info:
Comment 1 Petr Matyáš 2019-03-18 11:47:36 UTC 
Verified on ovirt-engine-extension-aaa-jdbc-1.1.10-1.el7ev.noarch
Comment 2 Sandro Bonazzola 2019-03-19 10:05:26 UTC 
This bugzilla is included in oVirt 4.3.2 release, published on March 19th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.