Update the OS version definition for each server

[jouvin]

The changes in this PR fix the problem identified in quattor/template-library-core#237 after the structure change of grid/OS repositories (main branch instead of one branch per major version). The problem was caused by the fact that the (obsolete) default OS version is not part of the main branch.

[jrha]

Ah, failing due to quattor/configuration-modules-core#1787

[jouvin]

The remaining error is caused by quattor/configuration-modules-core#1787. I'm reluctant to workaround the problem in the affected profiles.

The problem comes from that the fact systemd/legacy/chkconfig is loaded as part of the OS configuration but no systemd unit is defined in the systemd component for some profiles, which is a valid use case.

[jouvin]

@jrha the test is still failing because merging quattor/configuration-modules-core#1787 is not enough, I forgot! The test uses the configuration module templates in template-libary-core, not in the source repository (configuration-module-core). The only way to fix this failing test is to update template-library-core (components/systemd/schema) manually with the last version (or implementing the fix). Do you agree?

[jrha]

That does remind me that I'd like to discuss options for not having template-libary-core be a mix of manually maintained and automatically generated content.

[jrha]

I suppose manually fixing the schema for now is fine.

[jouvin]

That does remind me that I'd like to discuss options for not having template-libary-core be a mix of manually maintained and automatically generated content.

I agree it is not ideal but I don't have any idea on how avoiding it. Except moving the manually maintained content in another repo and importing it the same way as we do for configuration module templates. But at the price that it is much more difficult to test modifications in example profiles, as we do in test-library script, as this script rely on template-library-core and it may be unnecessarily complex to try to have it merging modifications from another repo... but may be I'm missing something...

[jrha]

Indeed, I don't see any obviously good options.