VMware Cloud Community
EGV
Contributor
Contributor

Failures during upgrade openstack 2.5 to 3.0

Hi,

We are having some issues with upgrading vio version 2.5 to 3.0.

1) When we install the patch with the command: viopatch install -p vio-upgrade-3.0 -v 3.0.0.4345506 it fails on the installation of 3 python libraries:

installing patch vio-upgrade-3.0 version 3.0.0.4345506

patch-install failed on the following nodes: ['localhost'].

We can workaround this issue by overwriting the file /opt/vmware/vio/cli/requirements.txt constantly via a while-true loop.

We delete te following lines from this file:

python-neutronclient

python-openstackclient

oslo.vmware

On all three python libraries we get the error in /var/log/viocli/viocli.log: Could not find a version that satisfies the requirement pbr>=1.6

It is a nasty workaround but the only way to continue.

2) When we finally start to upgrade en install a new 3.0 environment the upgrade fails on migrating data with the following error in the ansible.log on the OMS:

stdout: error: There are still 90 unmigrated flavor records. Migration cannot continue until all instance flavor records have been migrated to the new format. Please run ' nova-manage db migrate_flavor_data' first.

We do a rollback and run the command, with the root user, nova-manage db migrate_flavor_data on one of the controllers. This fails because it is missing a root.key file in /etc/fernet. I cannot run the command with the nova user because this user doesn't have a shell in /etc/passwd. We copied the nova.key file in /etc/fernet to root.key and runs the command nova-manage db migrate_flavor_data again with succes: 6 instances matched query, 6 completed.

We start the migrate all over again and it fails: stdout: error: There are still 84 unmigrated flavor records. Migration cannot continue until all instance flavor records have been migrated to the new format. Please run ' nova-manage db migrate_flavor_data' first. This is exactly 6 less then before.

Does anybody have an idea?

We upgrade all the way from vio version 1.0.0, maybe there is some old stuff/data bothering us?!

0 Kudos
6 Replies
lserpietri
Enthusiast
Enthusiast

Just curious: how much space you have left on the OMS before performing the upgrade?

Also, what is dpkg.log saying about the failed installation of the python libraries?

Thanks!
Luca

0 Kudos
EGV
Contributor
Contributor

Hi,

Space left is almost 3.5GB and  the dpkg log is empty.

Instead of the workaround i mentioned it is sufficient to just unistall pbr before upgrading. So perform a " pip uninstall pbr" and then the upgrade of the patch in OMS works fine!

0 Kudos
EGV
Contributor
Contributor

Does anybody has any clue on item nr 2?

0 Kudos
devino99
Contributor
Contributor

Can someone share the link for downloading the debian patch to upgrade VIO 2.5 to 3.0?

0 Kudos
rpellet
VMware Employee
VMware Employee

Can you get back to the point before you started making changes to files and attempting an upgrade?  You have backups right?  I ask because the first piece is a known issue.  It would only impact people who have installed from 1.x -> 2.x -> 3.x.

0 Kudos