Failed Upgrade from 4.12 to 5.2

Community Support
1

Am trying to do a test upgrade of nebula from 4.12 to 5.2…The fsck doesnt report any errors but the upgrade fails with the following message

cat /etc/redhat-release
CentOS Linux release 7.1.1503 (Core)
ruby -v
2.0.0p598 (2014-11-13) [x86_64-linux]

Version read:
Shared tables 4.11.80 : OpenNebula 4.12.1 daemon bootstrap
Local tables 4.11.80 : OpenNebula 4.12.1 daemon bootstrap

MySQL dump stored in /var/lib/one/mysql_localhost_opennebula_2016-11-1_14:31:17.sql
Use ‘onedb restore’ or restore the DB using the mysql command:
mysql -u user -h server -P port db_name < backup_file

Running migrators for shared tables
Running migrator /usr/lib/one/ruby/onedb/shared/4.11.80_to_4.90.0.rb
Done in 1.51s

Running migrator /usr/lib/one/ruby/onedb/shared/4.90.0_to_5.2.0.rb
Done in 0.35s

Database migrated from 4.11.80 to 5.2.0 (OpenNebula 5.2.0) by onedb command.

Running migrators for local tables
Running migrator /usr/lib/one/ruby/onedb/local/4.11.80_to_4.13.80.rb

  • WARNING WARNING WARNING WARNING WARNING WARNING WARNING *

OpenNebula 4.13.80 improves the management of FAILED VMs
Please remove (onevm delete) any FAILED VM before continuing.

  • WARNING WARNING WARNING WARNING WARNING WARNING WARNING *

The scheduler (and oned) has been update to enforce access
rights on system datastores. This new version also checks that
the user can access the System DS.
This may require to update system DS rights of your cloud

Do you want to proceed ? [y/N]

Error while upgrading from 4.11.80 to 4.13.80
/usr/lib/one/ruby/onedb/onedb.rb:238:in apply_migrators' /usr/lib/one/ruby/onedb/onedb.rb:179:in upgrade’
/usr/bin/onedb:313
/usr/lib/one/ruby/cli/command_parser.rb:449:in call' /usr/lib/one/ruby/cli/command_parser.rb:449:in run’
/usr/lib/one/ruby/cli/command_parser.rb:76:in initialize' /usr/bin/onedb:222:in new’
/usr/bin/onedb:222

The database will be restored

MySQL DB opennebula at localhost restored.

Is there anything obvious that am missing ?

Imran

2

I think the problem is much more basic…I am not able to upgrade to 4.14 itself although no issues reported by fsck

Imran

3

Hi!
assuming that no VM is in FAILED state as the script suggests, something in the 4.11.80_to_4.13.80.rb script is not working for you but I have no idea at what point.

Are you using a MySQL HA deployment?

If you’re upgrading from 4.12 to 4.14, what’s the output of the onedb upgrade command?

Cheers!

4

Hi Miguel

Thanks for your reply…i made a couple of fixes which seems to have solved the upgrade issue for me

  1. A few vms which were in failed state which i fixed and the fsck completed…
  2. had to patch encode line on one script as per this http://dev.opennebula.org/projects/opennebula/repository/revisions/0bc5ff31d28a659258bd73b42c2c1e841967614a/diff/src/cloud/common/CloudAuth/EC2CloudAuth.rb

Would be trying to re-run the test upgrades a couple of times with a backup copy to see if i can reproduce the exact sequence
Thanks again for the reply

Imran