Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1372608

Summary: Correcting return value to needs_action for services/openldap module
Product: Red Hat Enterprise Linux 6 Reporter: Jakub Mazanek <jmazanek>
Component: preupgrade-assistant-el6toel7Assignee: Jakub Mazanek <jmazanek>
Status: CLOSED ERRATA QA Contact: Alois Mahdal <amahdal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.7CC: jmazanek, phracek, pstodulk
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: preupgrade-assistant-el6toel7-0.6.57-1.el6 Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 09:02:06 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1335038, 1376678    

Description Jakub Mazanek 2016-09-02 08:14:04 UTC
Description of problem:
Missing log_*_risk value caused the module to default to fail status. I have corrected this to needs_inspection

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Jakub Mazanek 2016-09-20 10:49:38 UTC
included in new version 0.6.57

Comment 5 Alois Mahdal 2016-09-21 14:31:58 UTC
To reproduce this bug, just install openldap and run the module:  even with default openldap configuration the result should be 'needs_action', i.e. log_high_risk + exit_fail.

Previously, the result would be 'fail' because of missing log_high_risk, which is an invalid API usage.

Comment 6 Alois Mahdal 2016-10-19 10:37:52 UTC
(In reply to Alois Mahdal from comment #5)
> To reproduce this bug, just install openldap and run the module:  even with
> default openldap configuration the result should be 'needs_action', i.e.
> log_high_risk + exit_fail.
> 
> Previously, the result would be 'fail' because of missing log_high_risk,
> which is an invalid API usage.

Correction: the module is relevant to openldap-servers, not openldap.

Comment 7 Alois Mahdal 2016-10-19 10:40:23 UTC
Tested with preupgrade-assistant-el6toel7-0.6.59-4.el6:

Instaling openldap-servers and leaving it with default configuration leads to expected behavior: the module ends with needs_action.

Comment 9 errata-xmlrpc 2016-11-04 09:02:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2618.html