Oh, yes, thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755475
Title:
Cold migration with destination host
To manage notifications about this bug go to:
Yes upgrading from Ocata to Pike is supported. The process might be
different depending on how you're deployed. If your deployment was
automated using a project such as juju, ansible, kolla, puppet, the
process may be different for each of those and you'll want to read the
documentation from those
Is there any official document for upgrading from Ocata to Pike?
Is it safe to update?
My setup is pretty basic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755475
Title:
Cold migration with
You're welcome Marcio. Good luck.
** Changed in: nova (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755475
Title:
Cold migration with destination host
To
Oh yeah, I get it.
Thank you for the explanation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755475
Title:
Cold migration with destination host
To manage notifications about this bug go to:
Hi Marcio,
Unfortunately there's not a way to upgrade the api only. I took a look
at the code and if you are able to upgrade to Pike versions of the nova
package you'll be able to specify the host parameter as you'll be >=
2.56 at that point.
ocata: _MAX_API_VERSION = "2.42"
pike:
Currently when I try to migrate using:
{
"migrate": null
}
The following errors appear:
Remember that live migration is working ...
2018-03-13 10:04:35.522 2081 INFO nova.compute.resource_tracker
[req-d05e2191-6b75-4af9-8da2-a62e3edc99c0 - - - - -] Final resource view:
