Bug 1526184

Summary:	perl-IPTables-Parse returns undef instead of good status on default_log() success
Product:	[Fedora] Fedora EPEL	Reporter:	Ric Anderson <ric>
Component:	perl-IPTables-Parse	Assignee:	Adam Miller <admiller>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	el6	CC:	admiller, perl-devel, tremble
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-30 14:56:41 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:

Description Ric Anderson 2017-12-14 21:32:06 UTC

Description of problem: perl-IPTables-Parse returns undef instead of good status on default_log() success

Version-Release number of selected component (if applicable): perl-IPTables-Parse-0.7-4.el6.noarch


How reproducible: always


Steps to Reproduce:
1. install perl-IPTables-Parse-0.7-4.el6.noarch
2. Call the default_log() function.
3. Upon scanning iptables output for LOG statements (which are present), display_log() should return a table of data, along with a status of 1 for a successful operation.  The EPEL version does a
  return \%log_rules;
instead of return \%log_rules, 1;, which results in the calling application getting seeing that as an error return.
Version 1.8 of IPTables::Parse has corrected that return line to 
  return \%log_rules, 1;
which would make display_log() users much happier.

Actual results:
display_log() returns table of results, with UNDEF for status


Expected results:
display_log() returns table of results, with 1 for status


Additional info:
This bug causes false positive errors in psad startup because /usr/sbin/fwcheck_psad depends on display_log().

Comment 1 Ben Cotton 2020-11-05 16:48:24 UTC

This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 2 Ben Cotton 2020-11-30 14:56:41 UTC

EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.