Re: RHEL9?
"'Nick Anderson' via help-cfengine" <[email protected]>
| Newsgroups | gmane.comp.sysutils.cfengine.general |
|---|---|
| Message-ID | <[email protected]> |
"[email protected]" <[email protected]> writes: Hi David, The message above from Vratislav (Nov 3) suggests that RHEL9 ie being backported to 3.18. Has this been done? (The message references a PR which appears to have been merged. But has this yet made it to the community RPMs?) If so that means that I can start my RH9 development at 3.18 rather than needing to start at 3.21, which eases somewhat the version "stretch" with masterfiles. Yes, there has been work towards bringing el9 to 3.18.x. `cf-remote' is a great way to keep an eye out for new packages. ,---- | + cf-remote --version 3.18.x list el9 | Available releases: master, 3.21.x, 3.21.0, 3.18.x, 3.18.3, 3.18.2, 3.18.1, 3.18.0 | Using 3.18.x LTS: | http://buildcache.cfengine.com/packages/testing-pr/jenkins-3.18.x-nightly-pipeline-395/PACKAGES_x86_64_linux_redhat_9/cfengine-nova-3.18.4a.5dd596487-24850.el9.x86_64.rpm | + cf-remote --version 3.18.x list --edition community el9 | Available releases: master, 3.21.x, 3.21.0, 3.18.x, 3.18.3, 3.18.2, 3.18.1, 3.18.0 | Using 3.18.x LTS: | http://buildcache.cfengine.com/packages/testing-pr/jenkins-community-nightly-3.18.x-228/PACKAGES_x86_64_linux_redhat_9/cfengine-community-3.18.4a.5dd596487-24846.el9.x86_64.rpm | + : `---- But within any machine, what about software version vs. MPF/masterfiles version? We are currently 3.15 software and 3.12 masterfiles. It seems OK. Nevertheless I plan to move masterfiles upwards. Can it go ahead of the software? Indeed, I suspect masterfiles probably should be ahead of the software. This becomes more important as we cross the 3.18 threshold (and look further ahead towards 3.21) because a quick test with very new RPM (3.18 and 3.21) showed issues about "rxdirs", which I suspect will be eased by having masterfiles significantly later than our current 3.12. As noted in the [upgrade documentation], upgrading the MPF is the second step in the process (behind taking a backup) we always recommend that you run MPF version greater than or equal to your binary versions. This is because MPF from 3.12 can't possibly know about how to handle some change in behavior for 3.15.x clients. A good recent example of this is the [rxdirs change]. If you are running 3.18.0 MPF and you install 3.18.3 binaries you are going to get a bunch of warnings about not having `rxdirs' explicitly set. If you upgrade to 3.21 binaries and run 3.18.0 MPF you will have a bunch of warnings AND a behavior change. This last point raises another thought. Given that our software version is 3.15 (and likely to stay like that for a few months), can I take the masterfiles version way up in a giant leap from 3.12 to 3.21? Or am I better doing masterfiles by a few smaller steps (3.12->3.15->3.18->3.21)? I would probably do a similar series of steps for the software, although they may not exactly rise in step with each other. As noted previously, if your running 3.15 binaries, you should be running at least 3.15 MPF. It's no surprise that it works OK for you but running binaries newer than the policy is not something we test. We maintain compatibility with the versions that are supported at the time of release. So, [when there is a PR to the MPF on the 3.21.x branch] the MPF is tested against the last release of 3.18 and 3.15. Your already in untested waters running older MPF with newer binaries, I would just work on getting to 3.21.0 or 3.21.x MPF. -- Nick Anderson | Doer of Things | (+1) 785-550-1767 | <https://northern.tech> [upgrade documentation] <https://docs.cfengine.com/docs/3.21/getting-started-installation-upgrading.html> [rxdirs change] <https://cfengine.com/blog/2022/rxdirs-default-changing-from-true-to-false/> [when there is a PR to the MPF on the 3.21.x branch] <https://github.com/cfengine/masterfiles/blob/31991ba7e257c01aa34fe2cd79c48c0148867332/.github/workflows/ci.yml#L7> -- You received this message because you are subscribed to the Google Groups "help-cfengine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/help-cfengine/878rifeo6v.fsf%40northern.tech.