Thank you both, do you think this should be fixed by the Puppet module or in the package itself? Regards Francesco On 7/22/24 16:22, thomas@goirand.fr wrote:
On Jul 22, 2024 8:56 PM, Radomir Dopieralski <rdopiera@redhat.com> wrote:
I think the most sensible thing to do would be to be consistent and
have symlinks for all configuration-related files, including local/local_settings.d, local/enabled, and the policy files.
There is code in the .spec file for at least some of that, but it seems to be conditional for some reason.
On Thu, Jul 11, 2024 at 9:12 AM Francesco Di Nucci <francesco.dinucci@na.infn.it> wrote:
Hello,
some time ago I found that on EL9 Horizon searches for extra Python
snippets in "/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.d", while puppet-horizon places dashboards snippets in "/etc/openstack-dashboard/local_settings.d", so these are not loaded. At the same time, "/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py" is a symlink to "/etc/openstack-dashboard/local_settings".
Of the following, what should be adopted as proper approach on a
machine?
Having symlinks to /etc/openstack-dashboard for both
local_settings.py and local_settings.d
Editing files in /usr/share/openstack-dashboard without having symlinks Using a symlink for local_settings.py but placing snippets under /usr/share/openstack-dashboard
Config files must be in /etc. Anything else is wrong...
Thomas