Description of problem: When manila configuration is changed and overcloud-deploy command is run to update the overcloud, the manila share service running under pacemaker control is not restarted and does not get the new configuration. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Update manila configuration in THT. 2. Run overcloud-deploy.sh referencing an env file with the new configuration. 3. On overcloud controllers use 'docker exec' to inspect /etc/manila/manila.conf in the manila-share service container. Actual results: Old configuration is present. Expected results: Updated configuration is present. Additional info: /var/lib/config-data/manila/etc/manila/manila.conf and /var/lib/config-data/puppet-generated/manila/etc/manila/manila.conf are updated with the new config; 'docker ps | grep openstack-manila-share' shows that the service was not recently restarted (Up for hours).
580821 and 580879 fix issues with the naming of the manila-share service and resource that prevented the fixes for LP #1775196 from working properly for manila.
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible. If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-". To add draft documentation text: * Select the documentation type from the "Doc Type" drop down field. * A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.
Using the 2018-08-08.2 puddle I was able to verify that when the puppet configuration for Manila is change and when the overcloud is redeployed the Manila Share container is restarted along with the API and Scheduler services and the /etc/manila/manila.conf file is updated with the changes made in the puppet configuration. Marking as verified.
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://access.redhat.com/errata/RHBA-2018:2574