Upgrade Error: 6.2.0.1 to 6.4.x

Community Support Upgrade
1

Greetings,

I currently possess ONE CE 6.2.0.1 and am seeking to upgrade to ONE CE 6.4. However, I encountered an error during the onedb upgrade steps.

To address this issue, I have been following the instructions outlined in the following documentation: Upgrading Single Front-end Deployments — OpenNebula 6.4.3 documentation

Please find below the results of the encountered error:

onedb upgrade -v

Database is not correctly bootstraped.
/usr/lib/one/ruby/onedb/onedb_backend.rb:101:in `rescue in read_db_version'
/usr/lib/one/ruby/onedb/onedb_backend.rb:58:in `read_db_version'
/usr/lib/one/ruby/onedb/onedb.rb:268:in `upgrade'
/usr/bin/onedb:471:in `block (2 levels) in <main>'
/usr/lib/one/ruby/cli/command_parser.rb:482:in `call'
/usr/lib/one/ruby/cli/command_parser.rb:482:in `run'
/usr/lib/one/ruby/cli/command_parser.rb:84:in `initialize'
/usr/bin/onedb:357:in `new'
/usr/bin/onedb:357:in `<main>'


There was a failure retrieving the DB version.

List of OpenNebula package:

rpm -qa|grep opennebula
opennebula-provision-data-6.4.0.1-1.el7.noarch
opennebula-common-onecfg-6.4.0.1-1.el7.noarch
opennebula-6.4.0.1-1.el7.x86_64
opennebula-libs-6.4.0.1-1.el7.noarch
opennebula-sunstone-6.4.0.1-1.el7.noarch
opennebula-guacd-6.4.0.1-1.2.0+1.el7.x86_64
opennebula-flow-6.4.0.1-1.el7.noarch
opennebula-rubygems-6.4.0.1-1.el7.x86_64
opennebula-gate-6.4.0.1-1.el7.noarch
docker-machine-opennebula-6.4.0.1-1.el7.x86_64
opennebula-migration-community-6.4.0-1.el7_9.noarch
opennebula-common-6.4.0.1-1.el7.noarch
opennebula-fireedge-6.4.0.1-1.el7.x86_64
opennebula-tools-6.4.0.1-1.el7.noarch

Check OpenNebula service

systemctl list-units|grep opennebula
● opennebula.service                             loaded failed failed    OpenNebula Cloud Controller Daemon
● opennebula-showback.timer                             loaded failed failed    OpenNebula's periodic showback calculation
● opennebula-ssh-socks-cleaner.timer         loaded failed failed    OpenNebula SSH persistent connection cleaner

Regards,
Harry

2

Oh, I almost forgot to mention something important.

To resolve the issue, I needed to supply the DB backend configuration in oned.conf.
Once I did that, the problem was solved. Thank you so much, everyone! Case closed.