18.6.0-rc3

[jrha]

Top level issue tracker for any blocking issues discovered with 18.6.0-rc3.

[jouvin]

I deployed 18.6.0-rc3 on several pre-production/production machines wit a mix of grid/non-grid and EL6/EL7. No problem identified migrating from 17.7.0 (the new ncm-network caused no problem and no network interruption during upgrade). The only backward compatibility issue regarding the templates that I found are probably not new to this version and already documented: /system/network/interfaces/xxx/onboot is now a boolean instead of a string.

The only 2 problems identified with 18.6.0-rc3 are related to ncm-network:

• I have a machine (configured by Aquilon) where ncm-network complains about a missing address and netmask. This is suspect as this machine was running 18.6.0-rc1 without problem. I am troubleshooting this and will open an issue if I find something wrong.
• ncm-network is still suffering the unfixed https://github.com/quattor/configuration-modules-core/issues/1296 but it is not a blocker (probably a corner case as it is not a very common configuration at the moment).

[jrha]

The changes that made various broker generated field mandatory in quattor/template-library-core#177 are not compatible with our very old broker, as such I have marked the PR as backwards incompatible. This is likely to keep happening unless we can work out how to tie the schema to the broker version.

[jouvin]

After further troubleshooting, the first problem mentioned with ncm-network turned out to be a typo in our site configuration. Sorry for the noise.

[jrha]

phew!

[jouvin]

@jrha in reply to https://github.com/quattor/quattor.github.com/pull/255, I would suggest that you adopt the new schema in your plenary templates and that you t(temporarily until you upgrade your broker) redefine the Aquilon-related templates not matching your broker version in your site templates. It should be fairly easy now that we factored out the Aquilon parts in separate template (from what you mentioned you probably have only one to override). This doesn't remove the need for a proper fix to this, as discussed in https://github.com/quattor/aquilon/issues/118 but should provide a workaround making your life easier...

[jrha]

Sure, again just wanted to make sure it was flagged.

[jrha]

I'm sure this won't be of any use to anyone, but just for the record the changes we needed were:

diff …/quattor/types/aquilon/hardware.pan …/quattor/types/aquilon/hardware.pan
28c28
<     "country"    : string
---
>     "country"    ? string
30c30
<     "room"       : string
---
>     "room"       ? string
diff …/quattor/types/aquilon/system.pan …/quattor/types/aquilon/system.pan
55,57c55,57
<     "os"            : string # e.g. "linux"
<     "os_lifecycle"  : string
<     "model"         : string # e.g. "4.0.1-x86_64"
---
>     "os"            ? string # e.g. "linux"
>     "os_lifecycle"  ? string
>     "model"         ? string # e.g. "4.0.1-x86_64"
128c128
<     "stage"         : string
---
>     "stage"         ? string
129a130
>     "systemgrn"     ? list