Bug 1373597

Summary:	"include" keepalived.conf statement not working
Product:	Red Hat Enterprise Linux 7	Reporter:	daryl herzmann <akrherz>
Component:	keepalived	Assignee:	Ryan O'Hara <rohara>
Status:	CLOSED WONTFIX	QA Contact:	Brandon Perkins <bperkins>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	cluster-maint
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-15 07:45:32 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:

Description daryl herzmann 2016-09-06 16:50:42 UTC

Description of problem:
Usage of "include" statements in keepalived.conf either does not work or is silently ignored / unsupported.


Version-Release number of selected component (if applicable):
keepalived-1.2.13-7.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. add include statement in keepalived.conf
2. keepalived starts and does not report errors
3.

Actual results:
information in the include file is ignored

Expected results:
A) information in include file is included or
B) a warning / error that "include" is unknown

Additional info:
I tested with keepalived-1.2.22-1.el7.x86_64.rpm from r2d2.marmotte.net and the include statement works properly.  Sadly, I am having other issues with that version, so I can't just start using it :(

thank you!

Comment 1 daryl herzmann 2016-09-06 18:02:06 UTC

Uffties, I spoke too soon :(, so the silent failure here is when the conf path is double quoted.

include "/etc/keepalived/bah.conf"  <-- silently fails

include /etc/keepalived/bah.conf  <-- works as expected.

Up to you folks if you think this is a bug or not :/

Comment 4 RHEL Program Management 2020-12-15 07:45:32 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.