PLEASE HELP - oVirt 4.0.5 Instability + Best way to rollback to 4.0.4
Hi oVirt ObiWan´s, Today i try to rollback 4.0.5 to 4.0.4 because some instability with the following method and i crash on a problem. :-( I shutdown oVirt Engine and make checkpoint on Engine VM ( Runs on Hyper-V, don´t ask me way ... ). Rollback vm checkpoint to point in time before 4.0.5 update process and power up ovirt engine vm. Everything ok but, six virtual machines that i create before this point in time does not exist on oVirt Engine Database and all came with external-VMNAME and i can not do nothing on them. I really think (only in my dreams ) that when ovirt engine goes up and talk with ovirt nodes, all new vm will be automatically discovered again. The worst thing are that i use SAN Storage Domain and oVirt use LVM to storage VM disks, so i don´t know how to find vm disks that ovirt engine does not recognize (external-VMNAME). After all that, i rollback again to 4.0.5 and every vm are ok now again, but i want to test this rollback process to 4.0.4 and do this on Production. I think the right steps are : 1. Run engine-backup /bin/engine-backup --mode=backup --scope=all --file=/root/ovirt/`hostname`.`date +%d%m%Y.%H%M%S`.ovirt-engine.bkp --log=/tmp/ovirt-engine_backup.log 2. Shutdown ovirt engine vm. 3. Make new checkpoint to rollback with something goes wrong 4. Rollback to checkpoint witch 4.0.4 5. Restore engine-backup (from version 4.0.5) 6. Start everything and check if all are ok This is the right way to rollback from one sub release to another ( 4.0.5 to 4.0.4 ) ??? This checkpoints/snapshots of ovirt-engine VM are the best way to rollback in time ??? Thanks in advance.
Hello oVirt Padawan, You can install new engine machine and import existing storage domains there. https://www.ovirt.org/develop/release-management/features/storage/importstor... Please read restrictions and limitations. I think it's more safe way to go in such kind of situations. On Wed, Jan 4, 2017 at 6:40 PM, Rogério Ceni Coelho < rogeriocenicoelho@gmail.com> wrote:
Hi oVirt ObiWan´s,
Today i try to rollback 4.0.5 to 4.0.4 because some instability with the following method and i crash on a problem. :-(
I shutdown oVirt Engine and make checkpoint on Engine VM ( Runs on Hyper-V, don´t ask me way ... ). Rollback vm checkpoint to point in time before 4.0.5 update process and power up ovirt engine vm. Everything ok but, six virtual machines that i create before this point in time does not exist on oVirt Engine Database and all came with external-VMNAME and i can not do nothing on them. I really think (only in my dreams ) that when ovirt engine goes up and talk with ovirt nodes, all new vm will be automatically discovered again. The worst thing are that i use SAN Storage Domain and oVirt use LVM to storage VM disks, so i don´t know how to find vm disks that ovirt engine does not recognize (external-VMNAME).
After all that, i rollback again to 4.0.5 and every vm are ok now again, but i want to test this rollback process to 4.0.4 and do this on Production.
I think the right steps are :
1. Run engine-backup /bin/engine-backup --mode=backup --scope=all --file=/root/ovirt/`hostname`.`date +%d%m%Y.%H%M%S`.ovirt-engine.bkp --log=/tmp/ovirt-engine_backup.log 2. Shutdown ovirt engine vm. 3. Make new checkpoint to rollback with something goes wrong 4. Rollback to checkpoint witch 4.0.4 5. Restore engine-backup (from version 4.0.5) 6. Start everything and check if all are ok
This is the right way to rollback from one sub release to another ( 4.0.5 to 4.0.4 ) ??? This checkpoints/snapshots of ovirt-engine VM are the best way to rollback in time ???
Thanks in advance.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Pavel Zhukov Software Engineer RHEV Devops IRC: landgraf
Oh my god ... This option means a lot of work ... But thanks anyway ... I think in this case are more easy to clone this six new VMs (that does not exist on ovirt engine database 4.0.4) to another Storage Domain with NFS or oVirt Production enviroment and recreate them after checkpoint rollback. Do you think ovirt-engine database restore are really not an option from 4.0.5 to 4.0.4 ? Thanks. Em qua, 4 de jan de 2017 às 15:55, Pavel Zhukov <pzhukov@redhat.com> escreveu:
Hello oVirt Padawan, You can install new engine machine and import existing storage domains there. https://www.ovirt.org/develop/release-management/features/storage/importstor... Please read restrictions and limitations. I think it's more safe way to go in such kind of situations.
On Wed, Jan 4, 2017 at 6:40 PM, Rogério Ceni Coelho < rogeriocenicoelho@gmail.com> wrote:
Hi oVirt ObiWan´s,
Today i try to rollback 4.0.5 to 4.0.4 because some instability with the following method and i crash on a problem. :-(
I shutdown oVirt Engine and make checkpoint on Engine VM ( Runs on Hyper-V, don´t ask me way ... ). Rollback vm checkpoint to point in time before 4.0.5 update process and power up ovirt engine vm. Everything ok but, six virtual machines that i create before this point in time does not exist on oVirt Engine Database and all came with external-VMNAME and i can not do nothing on them. I really think (only in my dreams ) that when ovirt engine goes up and talk with ovirt nodes, all new vm will be automatically discovered again. The worst thing are that i use SAN Storage Domain and oVirt use LVM to storage VM disks, so i don´t know how to find vm disks that ovirt engine does not recognize (external-VMNAME).
After all that, i rollback again to 4.0.5 and every vm are ok now again, but i want to test this rollback process to 4.0.4 and do this on Production.
I think the right steps are :
1. Run engine-backup /bin/engine-backup --mode=backup --scope=all --file=/root/ovirt/`hostname`.`date +%d%m%Y.%H%M%S`.ovirt-engine.bkp --log=/tmp/ovirt-engine_backup.log 2. Shutdown ovirt engine vm. 3. Make new checkpoint to rollback with something goes wrong 4. Rollback to checkpoint witch 4.0.4 5. Restore engine-backup (from version 4.0.5) 6. Start everything and check if all are ok
This is the right way to rollback from one sub release to another ( 4.0.5 to 4.0.4 ) ??? This checkpoints/snapshots of ovirt-engine VM are the best way to rollback in time ???
Thanks in advance.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Pavel Zhukov Software Engineer RHEV Devops IRC: landgraf
On Wed, Jan 4, 2017 at 8:09 PM, Rogério Ceni Coelho <rogeriocenicoelho@gmail.com> wrote:
Oh my god ... This option means a lot of work ... But thanks anyway ... I think in this case are more easy to clone this six new VMs (that does not exist on ovirt engine database 4.0.4) to another Storage Domain with NFS or oVirt Production enviroment and recreate them after checkpoint rollback.
Do you think ovirt-engine database restore are really not an option from 4.0.5 to 4.0.4 ?
I'd not say "really not an option", but no-one I know ever tested this or intended to support this. To get a feeling of what you are getting into, you can check the git log from 4.0.4 to 4.0.5 for the directory packaging/dbscripts. Looking at it, you can see e.g. [1]. This means that on upgrade to 4.0.5, engine-setup ran this code for you. It also remembers it did (that's saved in the db too). So if in 4.0.4 with a 4.0.5 db you then do some changes that this code should have affected, it will not run again against your changes when you eventually do upgrade. To see the git log, you can do something like this: git clone https://gerrit.ovirt.org/p/ovirt-engine.git cd ovirt-engine git log -u $(git merge-base ovirt-engine-4.0.4.4 ovirt-engine-4.0.5.5)..ovirt-engine-4.0.5.5 packaging/dbscripts Best, [1] https://gerrit.ovirt.org/#/q/I715082f267b5eaa325cc2bb8988b25ac89e3b043,n,z
Thanks.
Em qua, 4 de jan de 2017 às 15:55, Pavel Zhukov <pzhukov@redhat.com> escreveu:
Hello oVirt Padawan, You can install new engine machine and import existing storage domains there. https://www.ovirt.org/develop/release-management/features/storage/importstor... Please read restrictions and limitations. I think it's more safe way to go in such kind of situations.
On Wed, Jan 4, 2017 at 6:40 PM, Rogério Ceni Coelho <rogeriocenicoelho@gmail.com> wrote:
Hi oVirt ObiWan´s,
Today i try to rollback 4.0.5 to 4.0.4 because some instability with the following method and i crash on a problem. :-(
I shutdown oVirt Engine and make checkpoint on Engine VM ( Runs on Hyper-V, don´t ask me way ... ). Rollback vm checkpoint to point in time before 4.0.5 update process and power up ovirt engine vm. Everything ok but, six virtual machines that i create before this point in time does not exist on oVirt Engine Database and all came with external-VMNAME and i can not do nothing on them. I really think (only in my dreams ) that when ovirt engine goes up and talk with ovirt nodes, all new vm will be automatically discovered again. The worst thing are that i use SAN Storage Domain and oVirt use LVM to storage VM disks, so i don´t know how to find vm disks that ovirt engine does not recognize (external-VMNAME).
After all that, i rollback again to 4.0.5 and every vm are ok now again, but i want to test this rollback process to 4.0.4 and do this on Production.
I think the right steps are :
1. Run engine-backup /bin/engine-backup --mode=backup --scope=all --file=/root/ovirt/`hostname`.`date +%d%m%Y.%H%M%S`.ovirt-engine.bkp --log=/tmp/ovirt-engine_backup.log 2. Shutdown ovirt engine vm. 3. Make new checkpoint to rollback with something goes wrong 4. Rollback to checkpoint witch 4.0.4 5. Restore engine-backup (from version 4.0.5) 6. Start everything and check if all are ok
This is the right way to rollback from one sub release to another ( 4.0.5 to 4.0.4 ) ??? This checkpoints/snapshots of ovirt-engine VM are the best way to rollback in time ???
Thanks in advance.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Pavel Zhukov Software Engineer RHEV Devops IRC: landgraf
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Didi
participants (3)
-
Pavel Zhukov -
Rogério Ceni Coelho -
Yedidyah Bar David