QA (public) » openQA Project (public) » openQA Infrastructure (public)

manually reverting the config file from https://gitlab.suse.de/openqa/salt-states-openqa/-/jobs/1026706#L1434 and restarted the postgresql service. The file was shortly overwritten again, likely by salt, but nevermind because I will fix that soon in the salt repo. But in the broken state I called in psql select pg_reload_conf(); which still shows "t" despite the config being invalid. This is in line with https://stackoverflow.com/questions/16333319/how-to-syntax-check-postgresql-config-files#comment101836284_55758799 which also states that this does not work. Also https://stackoverflow.com/a/16340569 states that there is no separate check config command. One needs to try to restart the server which refuses to load an invalid config.

https://github.com/os-autoinst/salt-states-openqa/blob/master/openqa/server.sls#L330 is within a block {%- if not grains.get('noservices', False) %} so we won't see those rules effective in CI jobs.

Manually testing the changes on OSD in a separate file with
salt-call --local -l error --state-output=changes state.sls_id postgresql-work_mem2 openqa.postgresql test=True
which takes about 10s each run – why is salt so slow – but ok.

Trying out the pattern manually with grep or sed is fine but with salt the replacement ends up as tMB

https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/705

We crosschecked and it's all good