Bug 1026490

Summary:	my.cnf generated incorrectly after migration
Product:	OpenShift Online	Reporter:	Stefanie Forrester <dakini>
Component:	Containers	Assignee:	Jhon Honce <jhonce>
Status:	CLOSED NOTABUG	QA Contact:	libra bugs <libra-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.x	CC:	dmace
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-04 21:28:51 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 Stefanie Forrester 2013-11-04 19:14:42 UTC

Description of problem:

Mysql is unable to start on this gear, due to an incorrectly-generated my.cnf. This could be caused by an erb templating error in the migration script.

When I try to fix the config file manually, it's immediately replaced with the incorrect version again, so manual intervention isn't an option.

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

2.0.34

How reproducible:

Not sure. I've only encountered one instance of this.

Steps to Reproduce:

The error can be confirmed on one host:

[root ~]# grep mysql_error.log /var/lib/openshift/520bd8895973ca3977000196/mysql/conf/my.cnf
log-error=/mysql_error.log

Actual results:

log-error=/mysql_error.log

Expected results:

The correct path is
log-error=/var/lib/openshift/520bd8895973ca3977000196/mysql/log/mysql_error.log

Additional info:

Comment 1 Dan Mace 2013-11-04 21:28:51 UTC

The gear's OPENSHIFT_MYSQL_DB_LOG_DIR variable was manually repaired, and no general problem was identified with other gears. Going to close this one.