diff --git a/content/software/release_information/release_notes/resolved_issues_741.md b/content/software/release_information/release_notes/resolved_issues_741.md index 153e98720..66a3d0344 100644 --- a/content/software/release_information/release_notes/resolved_issues_741.md +++ b/content/software/release_information/release_notes/resolved_issues_741.md @@ -5,6 +5,12 @@ date: "2026-10-01" A complete list of solved issues for 7.4.1 are listed in the [project development portal](https://github.com/OpenNebula/one/milestone/94). +## Upgrading to 7.4.1 + +{{< alert title="Important" type="warning" >}} +Unlike most maintenance releases, OpenNebula 7.4.1 includes changes to the stock configuration files and ships `onecfg` migrators from 7.4.0 to 7.4.1. After upgrading the packages you **must run `onecfg upgrade`** on the Front-end to migrate your configuration, as described in the [upgrade guide]({{% relref "software/upgrade_process/upgrade_guide/upgrading_single#step-7-update-configuration-files" %}}). +{{< /alert >}} + ## Backported Issues The following new features have been backported to 7.4.1: diff --git a/content/software/upgrade_process/upgrade_guide/start_here.md b/content/software/upgrade_process/upgrade_guide/start_here.md index da000d3bb..f5db21150 100644 --- a/content/software/upgrade_process/upgrade_guide/start_here.md +++ b/content/software/upgrade_process/upgrade_guide/start_here.md @@ -34,6 +34,10 @@ ERROR: Configurations metadata are outdated. ``` {{< /alert >}} +{{< alert title="Note" type="info" >}} +Maintenance releases (`X.Y.Z`) usually do not change the configuration files, so `onecfg upgrade` simply confirms that the configuration is up to date. **OpenNebula 7.4.1 is an exception**: it ships `onecfg` migrators from 7.4.0 to 7.4.1, and `onecfg upgrade` must be run to migrate the configuration to the new version. See [Step 7 of the upgrade guide]({{% relref "upgrading_single#step-7-update-configuration-files" %}}) for details. +{{< /alert >}} + ## Upgrade OpenNebula