Distribution EOLE » Modules » EOLE OpenNebula

Upgrade: switch Hâpy to Eolebase to upgrade to 2.6.2

• upgrade/Upgrade-Auto (main): execute “pre_download” before
  configuring Ubuntu upgrade tool.

• upgrade/pre_download/01-hapy: transform the Hâpy to an Eolebase
  before the upgrade.

Upgrade Hâpy: VMs data should not have references to cluster name

We will move the resources to the new default cluster in 2.6.2, the
VMs should not have references to the current 2.4.2 cluster.

So we “undeploy” the VMs instead of a simple “poweroff”

Ref: #27150

Upgrade Hâpy: switch from Eolebase during the upgrade

The upgrade from 2.4.2 can be detected with the configuration placed
under “/var/backups/eole/hapy/”.

• tmpl/eole.cfg: install eole-hapy-all and eole-hapy-module
  meta-packages when detecting Hâpy upgrade from 2.4.2.

Ref: #27150

Upgrade Hâpy: rename the current cluster

This way we can have the new 2.6.2 default cluster named as we want
without conflict.

Ref: #27150

Postservice: always declare “AUTH” variable when used

And normalise the casing of the variable.

Ref: #27150

Upgrade Hâpy: override buggy OpenNebula DB upgrade script

• override/4.11.80_to_4.13.80.rb: fixed script.

• posttemplate/90-one-db: override OpenNebula files.

• debsums-ignore.d/eole-hapy.conf: ignore the EOLE modified version of
  the DB upgrade script.

• eole-one-master.mk: install new files.

Ref: #27150

Upgrade Hâpy: properly use the exit code of the DB upgrade

The “exit” was done with the return code of the “echo” command and not
the “updateDB” one.

• posttemplate/90-one-db: use “set -e” to propagate errors.

Ref: #27150
Ref: #27156