Bug 1558961

Summary: MySQL Open Files Limit validation still checks pre-containerization config file
Product: Red Hat OpenStack Reporter: Florian Fuchs <flfuchs>
Component: openstack-tripleo-validationsAssignee: Florian Fuchs <flfuchs>
Status: CLOSED ERRATA QA Contact: Udi <ukalifon>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: augol, jjoyce, jschluet, slinaber, tvignaud, ukalifon
Target Milestone: betaKeywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-tripleo-validations-8.4.0-1.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:48:15 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 Florian Fuchs 2018-03-21 12:18:28 UTC
Description of problem:

The MySQL Open Files Limit validation still checks the mysql config path that was used before the service was containerized, which is making the validation fail.

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

How reproducible:

Steps to Reproduce:
1. Deploy an overcloud
2. Run the MySQL Files Limit validation

Actual results:
Validation fails

Expected results:
Validation passes

Additional info:

Comment 1 Udi 2018-03-28 13:15:10 UTC
A fix is already available.

Comment 4 Udi 2018-04-24 07:44:16 UTC
Verified in: openstack-tripleo-validations-8.4.0-2.el7ost.noarch

Comment 6 errata-xmlrpc 2018-06-27 13:48:15 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.