Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1429770
Crash for Non-existing user Description of problem: ds-logpipe.py crashes and throws exception when its executed with non-existing users and users who don't have write access to the log files. Version-Release number of selected component (if applicable): 389-ds-base-1.3.5.10-18 How reproducible: Consistently with 389-ds-base-1.3.5.10-18 builds. Steps to Reproduce: 1. Run namedPipeLog tests or dsGeneric categorized tests from Jenkins. 2. Check for crash reports 3. Crash occurs for NamedPipe_12 and NamedPipe_13 tests. Actual results: NamedPipe_12 and NamedPipe_13 tests crashes. Expected results: No crash for NamedPipe tests.
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1429770
Metadata Update from @mreynolds: - Issue assigned to mreynolds
<img alt="0001-Issue-49157-ds-logpipe.py-crashes-for-non-existing-u.patch" src="/389-ds-base/issue/raw/files/6a1d218ca0af48c4595b02de00297bd84c72712a4a096e9a3db6b5217cfb6a34-0001-Issue-49157-ds-logpipe.py-crashes-for-non-existing-u.patch" />
Metadata Update from @mreynolds: - Custom field origin adjusted to QE - Custom field reviewstatus adjusted to review - Custom field type adjusted to defect
Ack,
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to ack (was: review)
eef2ee8..28e4be0 master -> master
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
798b7e0..3f4c67f 389-ds-base-1.3.5 -> 389-ds-base-1.3.5
Removed all the raises
<img alt="0001-Ticket-49157-ds-logpipe.py-crashes-for-non-existing-.patch" src="/389-ds-base/issue/raw/files/dfd29b5e6760629c85ce3170f8603fd89c158c785be3ebe7def035d3e150e185-0001-Ticket-49157-ds-logpipe.py-crashes-for-non-existing-.patch" />
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to review (was: ack) - Issue status updated to: Open (was: Closed)
Ack, the code is fine, but why sys.exit(1) instead?
QE doesn't want the script to just "crash" with an exception, but have a more graceful exit when things go wrong. And I agree :) It's just a cleaner user experience IMO.
6fc82a3..94ebab3 master -> master
470a30c..4e63c2b 389-ds-base-1.3.6 -> 389-ds-base-1.3.6
6b4a0b4..e2ee1c1 389-ds-base-1.3.5 -> 389-ds-base-1.3.5
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue set to the milestone: 1.3.5.0 (was: 0.0 NEEDS_TRIAGE) - Issue status updated to: Closed (was: Open)
Fix typo
adb18fa..15f5f6a master -> master
e392712..5d2b063 389-ds-base-1.3.6 -> 389-ds-base-1.3.6
56961be..34bc5ef 389-ds-base-1.3.5 -> 389-ds-base-1.3.5
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2216
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.