Comment 3 for bug 1800980

Hi Xav, it is normal for the openstack charms to render config whether it is needed or not. The service restart checker looks for a change and only restart the services if the associated config file has changed. I think there are potentially two issues here:

1) Something is changing in the file(s) that shouldn't be. Lets find what it is and fix it.
2) update-status is doing more work than it needs to. I think other charms have a fix to this so I'll see if I can dig it out.

TBH I'm not convinced that the correct solution is to create a state that blocks rendering of config.