VM stuck in PENDING after upgrade 5.2 to 5.4

Community Support
1

Hi!

I’ve just upgraded our testing environment from 5.2 to 5.4 (in fact it still is really 5.3.80).

Upgrade was smooth. Previous VM are working and I can start and stop them.

But when I create a new VM, it stucks on PENDING.

Logs show:

Mon Jun 12 10:14:47 2017 [Z0][FRM][I]: Purging federated log
Mon Jun 12 10:14:50 2017 [Z0][ReM][D]: Req:8400 UID:0 one.zone.raftstatus invoked
Mon Jun 12 10:14:50 2017 [Z0][ONE][E]: SQL command was: SELECT body FROM zone_pool WHERE oid = 0, error: callback requested query abort
Mon Jun 12 10:14:50 2017 [Z0][ReM][E]: Req:8400 UID:0 one.zone.raftstatus result FAILURE [one.zone.raftstatus] Error getting zone [0].

==> /var/log/one/sched.log <==
Mon Jun 12 10:14:50 2017 [Z0][SCHED][E]: Cannot contact oned: [one.zone.raftstatus] Error getting zone [0].

Any idea?

It’s better to install from zero, being a development version?

Thanks!

2

Hi Andreu,

As mentioned here the upgrade path is incomplete in 5.3.80.

With clean install and this patch applied the beta is usable in my case. As storage addon developer I am focused mostly on the storage related part though.

BR,
Anton

3

Thank you!!

Finally I uninstalled (apt-get remove --purge) and installed again and now it’s running fine.

Thank you!

4

Great! Thanks for feedback Andreu. Next beta should include a working
migrator for testing.