Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0
On Tue, Jun 28, 2016 at 5:24 PM, Dan Kenigsberg wrote: > On Tue, Jun 28, 2016 at 04:08:51PM +0200, Simone Tiraboschi wrote: >> On Tue, Jun 28, 2016 at 3:02 PM, Dan Kenigsberg wrote: >> > On Mon, Jun 27, 2016 at 10:08:33AM +0200, Stefano Danzi wrote: >> >> Hi! >> > >> > >> > Thanks for the detailed logging! >> > >> >> >> >> The broker error is: >> >> >> >> ==> /var/log/ovirt-hosted-engine-ha/agent.log <== >> >> MainThread::INFO::2016-06-27 >> >> 09:27:03,311::brokerlink::140::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) >> >> Success, id 140293563619152 >> >> >> >> ==> /var/log/ovirt-hosted-engine-ha/broker.log <== >> >> Thread-25::ERROR::2016-06-27 >> >> 09:27:03,314::listener::182::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle) >> >> Error while serving connection >> >> Traceback (most recent call last): >> >> File >> >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py", >> >> line 166, in handle >> >> data) >> >> File >> >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py", >> >> line 299, in _dispatch >> >> .set_storage_domain(client, sd_type, **options) >> >> File >> >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", >> >> line 66, in set_storage_domain >> >> self._backends[client].connect() >> >> File >> >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", >> >> line 400, in connect >> >> volUUID=volume.volume_uuid >> >> File >> >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", >> >> line 245, in _get_volume_path >> >> volUUID >> > >> > We have two issues here. First is that >> > https://gerrit.ovirt.org/gitweb?p=ovirt-hosted-engine-ha.git;a=blob;f=ovirt_hosted_engine_ha/lib/storage_backends.py;h=f2fbdc43d0e4afd7539a3a1de75de0cb07bdca9d;hb=HEAD#l271 >> > is still using vdscli to contact vdsm, instead of the preferred >> > jsonrpccli. >> >> We already have this one: >> https://bugzilla.redhat.com/show_bug.cgi?id=1101554 >> > Bug 1101554 - [RFE] HE-setup: use vdsm api instead of vdsClient > > It does not seem to be the same thing; here I'm referring to > ovirt-hosted-engine-ha (not -setup). -ha *is* using vdsm API, but in one > condition it's the soon-to-be-deprecated xmlrpc. ovirt-hosted-engine-setup is already using just API via jsonrpc. The issue is that ovirt-hosted-engine-ha somewhere uses vdsClient which AFAIK internally still uses xmlrpc ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Create a Virtual Disk failed
I used yum to update the lastest 3.6 version. And have installed ovirt-engine-webadmin-portal-debuginfo ovirt-engine-userportal-debuginfo. But it seems that there's no more stack trace log. $ tailf /var/log/ovirt-engine/ui.log 2016-06-28 23:50:30,076 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-1) [] Permutation name: 4F7357E226A20F21D89332F184D6C272 2016-06-28 23:50:30,076 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-1) [] Uncaught exception: : com.google.gwt.core.client.JavaScriptException: (TypeError) __gwt$exception: : a is undefined at Unknown._kj(Unknown Source) at Unknown.JUq(Unknown Source) at Unknown.Fbr(Unknown Source) at Unknown.Hno(Unknown Source) at Unknown.t0n(Unknown Source) at Unknown.w0n(Unknown Source) at Unknown.q3n(Unknown Source) at Unknown.t3n(Unknown Source) at Unknown.S2n(Unknown Source) at Unknown.V2n(Unknown Source) at Unknown.bMe(Unknown Source) at Unknown.V7(Unknown Source) at Unknown.k8(Unknown Source) at Unknown.czf/c.onreadystatechange<(Unknown Source) at Unknown.Ux(Unknown Source) at Unknown.Yx(Unknown Source) at Unknown.Xx/<(Unknown Source) at Unknown.anonymous(Unknown Source) On Mon, Jun 27, 2016 at 8:37 PM, Alexander Wels wrote: > On Monday, June 27, 2016 11:56:12 AM Liron Aravot wrote: > > > Thanks Dewey, > > > > > > What exact 3.6 version do you use? > > > Elad - have you encountered that issue? can you see if it happens on your > > > env as well? > > > > > > thanks. > > > > > > > Also to get a de-obfuscated stack trace in the UI.log please install the > ui debug package: > > > > > yum install ovirt-engine-webadmin-portal-debuginfo > ovirt-engine-userportal-debuginfo > > > > Then recreate the issue and look in the UI.log again, it should > > now at least give you a better readable stack trace. > > > > > On Sun, Jun 26, 2016 at 6:40 PM, Dewey Du wrote: > > > > the content attached above is ui.log, and there is no logs in > server.log > > > > and engine.log. > > > > > > > > I'm using oVirt 3.6. Finally I found out I can create the disk from the > > > > edit page of the vm. > > > > > > > > On Sun, Jun 26, 2016 at 8:40 PM, Yaniv Dary wrote: > > > >> Adding Tal. > > > >> What version are you using? Can you attach logs? > > > >> > > > >> Yaniv Dary > > > >> Technical Product Manager > > > >> Red Hat Israel Ltd. > > > >> 34 Jerusalem Road > > > >> Building A, 4th floor > > > >> Ra'anana, Israel 4350109 > > > >> > > > >> Tel : +972 (9) 7692306 > > > >> > > > >> 8272306 > > > >> > > > >> Email: yd...@redhat.com > > > >> IRC : ydary > > > >> > > > >> On Sat, Jun 25, 2016 at 12:26 PM, Dewey Du wrote: > > > >>> I use glusterfs as storage. When I tried to create a virtual disk > for a > > > >>> vm, I got the following error in UI logs. > > > >>> > > > >>> ERROR > > > >>> [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] > > > >>> (default task-48) [] Permutation name: > B003B5EDCB6FC4308644D5D001F65B4C > > > >>> ERROR > > > >>> [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] > > > >>> (default task-48) [] Uncaught exception: : > > > >>> com.google.gwt.core.client.JavaScriptException: (TypeError) > > > >>> > > > >>> __gwt$exception: : a is undefined > > > >>> > > > >>> at Unknown._kj(Unknown Source) > > > >>> at Unknown.JUq(Unknown Source) > > > >>> at Unknown.Fbr(Unknown Source) > > > >>> at Unknown.Hno(Unknown Source) > > > >>> at Unknown.t0n(Unknown Source) > > > >>> at Unknown.w0n(Unknown Source) > > > >>> at Unknown.q3n(Unknown Source) > > > >>> at Unknown.t3n(Unknown Source) > > > >>> at Unknown.S2n(Unknown Source) > > > >>> at Unknown.V2n(Unknown Source) > > > >>> at Unknown.bMe(Unknown Source) > > > >>> at Unknown.V7(Unknown Source) > > > >>> at Unknown.k8(Unknown Source) > > > >>> at Unknown.czf/c.onreadystatechange<(Unknown Source) > > > >>> at Unknown.Ux(Unknown Source) > > > >>> at Unknown.Yx(Unknown Source) > > > >>> at Unknown.Xx/<(Unknown Source) > > > >>> at Unknown.anonymous(Unknown Source) > > > >>> > > > >>> ___ > > > >>> Users mailing list > > > >>> Users@ovirt.org > > > >>> http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > ___ > > > > Users mailing list > > > > Users@ovirt.org > > > > http://lists.ovirt.org/mailman/listinfo/users > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] cannot change cluster compatibility version from 3.6 to 4.0
Dne 28.6.2016 v 17:19 Alexander Wels napsal(a): On Tuesday, June 28, 2016 05:11:14 PM Jiří Sléžka wrote: I forgot attach the screenshot... Jiri The label that has the dotted line under it should have a tooltip explaining the issue. But some of the most likely issues are: you are righ, there is a tooltip explaining tha I have to shutdown all vms before changing compatibility version (I suppose this is valid only for 3->4 upgrade because minor upgrades were possible without downtime) 1. DC is at 3.6 and you can't have 4.0 clusters in 3.6 DC. but when I try to change DC version from 3.6 to 4.0 I got "Error while executing action: Cannot update Data Center compatibility version to a value that is greater than its Cluster's version. The following clusters should be upgraded CIT-oVirt." 2. Active host on 3.6 in the cluster. You can put the hosts in maintenance and upgrade the cluster, you will obviously also have to upgrade the hosts after that before you can activate them again. ok, thanks for help. I have to schedule maintenance window. Cheers, Jiri Dne 28.6.2016 v 17:06 Jiří Sléžka napsal(a): Hi all, I have just upgraded engine from 3.6.6 to 4.0 (all worked fine except custom certificate problem which is described and solved here https://bugzilla.redhat.com/show_bug.cgi?id=1336838). Then I upgraded all hosts in cluster and I would like to change cluster compatibility level but it fails in a way there is a red border around "Compatibility Version" dropdown box but no explanation why. There are no entries in logs... What are prerequisities to change cluster compatibility level to 4.0? Do I missing something? Engine (standalone) and hosts are CentOS 7.2 btw. dashboard looks really nice! Cheers, Jiri ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users <> smime.p7s Description: Elektronicky podpis S/MIME ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0
On Tue, Jun 28, 2016 at 04:08:51PM +0200, Simone Tiraboschi wrote: > On Tue, Jun 28, 2016 at 3:02 PM, Dan Kenigsberg wrote: > > On Mon, Jun 27, 2016 at 10:08:33AM +0200, Stefano Danzi wrote: > >> Hi! > > > > > > Thanks for the detailed logging! > > > >> > >> The broker error is: > >> > >> ==> /var/log/ovirt-hosted-engine-ha/agent.log <== > >> MainThread::INFO::2016-06-27 > >> 09:27:03,311::brokerlink::140::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) > >> Success, id 140293563619152 > >> > >> ==> /var/log/ovirt-hosted-engine-ha/broker.log <== > >> Thread-25::ERROR::2016-06-27 > >> 09:27:03,314::listener::182::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle) > >> Error while serving connection > >> Traceback (most recent call last): > >> File > >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py", > >> line 166, in handle > >> data) > >> File > >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py", > >> line 299, in _dispatch > >> .set_storage_domain(client, sd_type, **options) > >> File > >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", > >> line 66, in set_storage_domain > >> self._backends[client].connect() > >> File > >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", > >> line 400, in connect > >> volUUID=volume.volume_uuid > >> File > >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", > >> line 245, in _get_volume_path > >> volUUID > > > > We have two issues here. First is that > > https://gerrit.ovirt.org/gitweb?p=ovirt-hosted-engine-ha.git;a=blob;f=ovirt_hosted_engine_ha/lib/storage_backends.py;h=f2fbdc43d0e4afd7539a3a1de75de0cb07bdca9d;hb=HEAD#l271 > > is still using vdscli to contact vdsm, instead of the preferred > > jsonrpccli. > > We already have this one: > https://bugzilla.redhat.com/show_bug.cgi?id=1101554 > Bug 1101554 - [RFE] HE-setup: use vdsm api instead of vdsClient It does not seem to be the same thing; here I'm referring to ovirt-hosted-engine-ha (not -setup). -ha *is* using vdsm API, but in one condition it's the soon-to-be-deprecated xmlrpc. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0
Il 28/06/2016 15.02, Dan Kenigsberg ha scritto: On Mon, Jun 27, 2016 at 10:08:33AM +0200, Stefano Danzi wrote: Hi! Thanks for the detailed logging! The broker error is: ==> /var/log/ovirt-hosted-engine-ha/agent.log <== MainThread::INFO::2016-06-27 09:27:03,311::brokerlink::140::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Success, id 140293563619152 ==> /var/log/ovirt-hosted-engine-ha/broker.log <== Thread-25::ERROR::2016-06-27 09:27:03,314::listener::182::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle) Error while serving connection Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py", line 166, in handle data) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py", line 299, in _dispatch .set_storage_domain(client, sd_type, **options) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", line 66, in set_storage_domain self._backends[client].connect() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 400, in connect volUUID=volume.volume_uuid File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 245, in _get_volume_path volUUID We have two issues here. First is that https://gerrit.ovirt.org/gitweb?p=ovirt-hosted-engine-ha.git;a=blob;f=ovirt_hosted_engine_ha/lib/storage_backends.py;h=f2fbdc43d0e4afd7539a3a1de75de0cb07bdca9d;hb=HEAD#l271 is still using vdscli to contact vdsm, instead of the preferred jsonrpccli. The second is that vdscli.connect's heuristic ends up reading the local server address from vdsm config, where it finds the default ipv6-local address of "::". Please try setting [addresses] management_ip='0.0.0.0' in your /etc/vdsm/vdsm.conf instead of the crontab hacks. this solve the issue, but I still to haven't default gateway on ovirtmgmt inteface. Would you please open a bug about the two issues (ovirt-hosted-engine-ha and vdsm networking)? Here: https://bugzilla.redhat.com/show_bug.cgi?id=1350883 Would you report the output of `netstats -nltp` on your host, as I do not completely understand why no interface (not even the loopback one) was listening on ipv6? Here: [root@ovirt01 ~]# netstat -nltp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 0.0.0.0:39373 0.0.0.0:* LISTEN 2200/rpc.statd tcp0 0 0.0.0.0:111 0.0.0.0:* LISTEN 969/rpcbind tcp0 0 0.0.0.0:54322 0.0.0.0:* LISTEN 943/python tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1571/sshd tcp0 0 0.0.0.0:858 0.0.0.0:* LISTEN 1946/glusterfs tcp0 0 0.0.0.0:49152 0.0.0.0:* LISTEN 1929/glusterfsd tcp0 0 0.0.0.0:49153 0.0.0.0:* LISTEN 1968/glusterfsd tcp0 0 0.0.0.0:20490.0.0.0:* LISTEN 1946/glusterfs tcp0 0 0.0.0.0:38465 0.0.0.0:* LISTEN 1946/glusterfs tcp0 0 0.0.0.0:38466 0.0.0.0:* LISTEN 1946/glusterfs tcp0 0 0.0.0.0:16514 0.0.0.0:* LISTEN 1603/libvirtd tcp0 0 0.0.0.0:38468 0.0.0.0:* LISTEN 1946/glusterfs tcp0 0 0.0.0.0:38469 0.0.0.0:* LISTEN 1946/glusterfs tcp0 0 0.0.0.0:24007 0.0.0.0:* LISTEN 1585/glusterd tcp6 0 0 :::54321:::* LISTEN 1893/python tcp6 0 0 :::22 :::* LISTEN 1571/sshd tcp6 0 0 :::16514:::* LISTEN 1603/libvirtd Regards, Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] cannot change cluster compatibility version from 3.6 to 4.0
On Tuesday, June 28, 2016 05:11:14 PM Jiří Sléžka wrote: > I forgot attach the screenshot... > > Jiri > The label that has the dotted line under it should have a tooltip explaining the issue. But some of the most likely issues are: 1. DC is at 3.6 and you can't have 4.0 clusters in 3.6 DC. 2. Active host on 3.6 in the cluster. You can put the hosts in maintenance and upgrade the cluster, you will obviously also have to upgrade the hosts after that before you can activate them again. > Dne 28.6.2016 v 17:06 Jiří Sléžka napsal(a): > > Hi all, > > > > I have just upgraded engine from 3.6.6 to 4.0 (all worked fine except > > custom certificate problem which is described and solved here > > https://bugzilla.redhat.com/show_bug.cgi?id=1336838). > > > > Then I upgraded all hosts in cluster and I would like to change cluster > > compatibility level but it fails in a way there is a red border around > > "Compatibility Version" dropdown box but no explanation why. There are > > no entries in logs... > > > > What are prerequisities to change cluster compatibility level to 4.0? Do > > I missing something? > > > > Engine (standalone) and hosts are CentOS 7.2 > > > > btw. dashboard looks really nice! > > > > Cheers, Jiri > > > > > > ___ > > Users mailing list > > Users@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] cannot change cluster compatibility version from 3.6 to 4.0
I forgot attach the screenshot... Jiri Dne 28.6.2016 v 17:06 Jiří Sléžka napsal(a): Hi all, I have just upgraded engine from 3.6.6 to 4.0 (all worked fine except custom certificate problem which is described and solved here https://bugzilla.redhat.com/show_bug.cgi?id=1336838). Then I upgraded all hosts in cluster and I would like to change cluster compatibility level but it fails in a way there is a red border around "Compatibility Version" dropdown box but no explanation why. There are no entries in logs... What are prerequisities to change cluster compatibility level to 4.0? Do I missing something? Engine (standalone) and hosts are CentOS 7.2 btw. dashboard looks really nice! Cheers, Jiri ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users <> smime.p7s Description: Elektronicky podpis S/MIME ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VDI experience to share?
Hi everybody, thank you for taking the time to share your experiences. It seems we have now some stuff to digest and to do our tests. I think I'll report back when things will settle down. Best regards, Giorgio. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] cannot change cluster compatibility version from 3.6 to 4.0
Hi all, I have just upgraded engine from 3.6.6 to 4.0 (all worked fine except custom certificate problem which is described and solved here https://bugzilla.redhat.com/show_bug.cgi?id=1336838). Then I upgraded all hosts in cluster and I would like to change cluster compatibility level but it fails in a way there is a red border around "Compatibility Version" dropdown box but no explanation why. There are no entries in logs... What are prerequisities to change cluster compatibility level to 4.0? Do I missing something? Engine (standalone) and hosts are CentOS 7.2 btw. dashboard looks really nice! Cheers, Jiri <> smime.p7s Description: Elektronicky podpis S/MIME ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0
On Tue, Jun 28, 2016 at 3:02 PM, Dan Kenigsberg wrote: > On Mon, Jun 27, 2016 at 10:08:33AM +0200, Stefano Danzi wrote: >> Hi! > > > Thanks for the detailed logging! > >> >> The broker error is: >> >> ==> /var/log/ovirt-hosted-engine-ha/agent.log <== >> MainThread::INFO::2016-06-27 >> 09:27:03,311::brokerlink::140::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) >> Success, id 140293563619152 >> >> ==> /var/log/ovirt-hosted-engine-ha/broker.log <== >> Thread-25::ERROR::2016-06-27 >> 09:27:03,314::listener::182::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle) >> Error while serving connection >> Traceback (most recent call last): >> File >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py", >> line 166, in handle >> data) >> File >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py", >> line 299, in _dispatch >> .set_storage_domain(client, sd_type, **options) >> File >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", >> line 66, in set_storage_domain >> self._backends[client].connect() >> File >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", >> line 400, in connect >> volUUID=volume.volume_uuid >> File >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", >> line 245, in _get_volume_path >> volUUID > > We have two issues here. First is that > https://gerrit.ovirt.org/gitweb?p=ovirt-hosted-engine-ha.git;a=blob;f=ovirt_hosted_engine_ha/lib/storage_backends.py;h=f2fbdc43d0e4afd7539a3a1de75de0cb07bdca9d;hb=HEAD#l271 > is still using vdscli to contact vdsm, instead of the preferred > jsonrpccli. We already have this one: https://bugzilla.redhat.com/show_bug.cgi?id=1101554 > The second is that vdscli.connect's heuristic ends up reading the local > server address from vdsm config, where it finds the default ipv6-local > address of "::". > > Please try setting > > [addresses] > management_ip='0.0.0.0' > > in your /etc/vdsm/vdsm.conf instead of the crontab hacks. > > > Would you please open a bug about the two issues > (ovirt-hosted-engine-ha and vdsm networking)? > > Would you report the output of `netstats -nltp` on your host, as I do > not completely understand why no interface (not even the loopback one) > was listening on ipv6? > > Regards, > Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] 3.6 to 4.0 upgrade cert issue
On Mon, Jun 27, 2016 at 1:16 AM, Matt Haught wrote: > On Fri, Jun 24, 2016 at 2:58 PM, Martin Perina wrote: > > > > > > This is not a correct solution although it's working for now. Correct > steps are described at [1]. > > > > Thanks > > > > Martin Perina > > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1336838 > > > > So I followed the bug report and put my CA cert into > /etc/pki/ca-trust/source/anchors/ and ran update-ca-trust. I created a > /etc/ovirt-engine/engine.conf.d/99-custom-truststore.conf as shown, > but after restarting ovirt-engine I got > > Keystore was tampered with, or password was incorrect > > when trying to log in. So I ended up doing a > > keytool -storepasswd -keystore /etc/pki/ca-trust/extracted/java/cacerts > > using "changeit" and set a password and put that in > 99-custom-truststore.conf . Things appear to be working now. > Unfortunately we have a bug there and it will be fixed in oVirt 4.0.1. Until then we support only truststores with password. Sorry for your troubles. Martin Perina > > Thanks, > > Matt Haught > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0
> [.. cutting all bogus as it is unreadable, even with html mails..] > > On Tue, Jun 28, 2016 at 4:00 PM, Yaniv Dary wrote: > > > Do you have any 3.5 clusters? You can only upgrade to 4.0, if all the > > cluster are 3.6 compatibility. > >> > >> #engine-backup --mode=restore --no-restore-permissions --provision-db > >> --provision-dwh-db --provision-reports-db --file=engine-backup.tar.gz > >> --log=engine-backup-restore.log > >> > >> Success with the restore! > >> > >> Thanks for pointing me out. What I did was just following the > >> documentation, right or wrong. > >> > >> But when I run "Engine-setup" I got stucked with > >> > >> "[ INFO ] Stage: Setup validation > >> [WARNING] Less than 16384MB of memory is available > >> [ ERROR ] Failed to execute stage 'Setup validation': Trying to upgrade > >> from unsupported versions: 3.5 > >> [ INFO ] Stage: Clean up > >> Log file is located at > >> /var/log/ovirt-engine/setup/ovirt-engine-setup-20160628120936-ix7pb8.log > >> [ INFO ] Generating answer file > >> '/var/lib/ovirt-engine/setup/answers/20160628121149-setup.conf' > >> [ INFO ] Stage: Pre-termination > >> [ INFO ] Stage: Termination > >> [ ERROR ] Execution of setup failed" > >> 3.6 EL6 migration to 4.0 EL7 works OK for me with following steps: 1. 3.6 EL6 engine (3.6 dc/clstr level) 2. 3.6 EL6 engine-backup and do backup 3. 4.0 EL7 clean install 4. 4.0 EL7 engine-backup and do restore 5. 4.0 EL7 engine-setup What are the problematic steps on other side? Do we have a problem if 3.6 EL6 engine does have dc/clstr level set to '3.5'? j. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0
Adding Jiri. Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: yd...@redhat.com IRC : ydary On Tue, Jun 28, 2016 at 4:00 PM, Yaniv Dary wrote: > Do you have any 3.5 clusters? You can only upgrade to 4.0, if all the > cluster are 3.6 compatibility. > > Yaniv Dary > Technical Product Manager > Red Hat Israel Ltd. > 34 Jerusalem Road > Building A, 4th floor > Ra'anana, Israel 4350109 > > Tel : +972 (9) 7692306 > 8272306 > Email: yd...@redhat.com > IRC : ydary > > > On Tue, Jun 28, 2016 at 1:22 PM, Ricky Schneberger > wrote: > >> On 2016-06-28 10:21, Yedidyah Bar David wrote: >> > On Tue, Jun 28, 2016 at 10:53 AM, Ricky Schneberger >> > wrote: >> >> On 2016-06-27 19:15, Fernando Fuentes wrote: >> >> >> >> Ricky, >> >> >> >> I am under the impression that the DB migration was implemented in >> >> release 3.6.6. >> >> >> >> I might be wrong. >> >> >> >> https://www.ovirt.org/release/3.6.6/ >> >> >> >> What's New in 3.6.6? >> >> Enhancement >> >> oVirt Engine >> >> >> >> BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts >> from >> >> el6->el7. >> >> BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored >> >> on 3.6 on el7 >> >> Feature: >> >> >> >> Allow engine-backup on el7 to restore backups taken on el6. >> >> >> >> Reason: >> >> >> >> engine 4.0 does not support el6. Users that want to upgrade from 3.6 on >> >> el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 >> >> and restore on 4.0/el7. >> >> >> >> This feature, backported from 4.0, allows to do such a migration also >> in >> >> 3.6. >> >> >> >> Result: >> >> >> >> Using this flow, it's possible to migrate a el6 setup to el7: >> >> >> >> On the existing engine machine run: >> >> 1. engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log >> >> >> >> On a new el7 machine: >> >> 2. Install engine, including dwh if it was set up on el6. >> >> 3. Copy engine-3.6.bck to the el7 machine >> >> 4. engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log >> >> --provision-db --no-restore-permissions >> >> 5. engine-setup >> >> >> >> Check engine-backup documentation for other options, including using >> >> remote databases, extra grants/permissions, etc. >> >> >> >> >> >> One step forward, two backward >> >> >> >> - upgrade the old EL6 to ovirt 3.6.6 >> >> - engine-backup --mode=backup --file=engine-backup.tar.gz >> --log=backup.log >> >> - install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm, >> to >> >> have ovirt-engine 4.0.0.6. >> >> - yum install ovirt-engine >> >> - engine-backup --mode=restore --no-restore-permissions --provision-db >> >> --file=engine-backup.tar.gz --log=engine-backup-restore.log >> >> >> >> Then I got this error... >> >> >> >> "Preparing to restore: >> >> - Unpacking file 'engine-backup.tar.gz' >> >> Restoring: >> >> - Files >> >> >> -- >> >> Please note: >> >> >> >> Operating system is different from the one used during backup. >> >> Current operating system: centos7 >> >> Operating system at backup: centos6 >> >> >> >> Apache httpd configuration will not be restored. >> >> You will be asked about it on the next engine-setup run. >> >> >> -- >> >> Provisioning PostgreSQL users/databases: >> >> - user 'engine', database 'engine' >> >> Restoring: >> >> FATAL: Can't connect to database 'ovirt_engine_history'. Please see >> >> '/usr/bin/engine-backup --help'." >> >> >> > The backup/restore here is just like normal ones, so for details you >> can read >> > the output of 'engine-backup --help' or [1]. >> > >> > In your specific case, you seem to have dwh in your backup. >> > >> > To restore it, you have to either prepare a database with the same >> credentials >> > as the one used in the old machine, or, if it was >> automatically-provisioned by >> > engine-setup, you can pass the option '--provision-dwh-db' to make >> engine-backup >> > create it for you. >> > >> > I think I should add an option '--provision-all-databases' or something >> like >> > that. Didn't feel very good about it so never done, and no-one asked >> for it... >> > >> > Best regards, >> > >> > [1] >> http://www.ovirt.org/develop/release-management/features/engine/engine-backup/ >> > >> > >> >> #engine-backup --mode=restore --no-restore-permissions --provision-db >> --provision-dwh-db --provision-reports-db --file=engine-backup.tar.gz >> --log=engine-backup-restore.log >> >> Success with the restore! >> >> Thanks for pointing me out. What I did was just following the >> documentation, right or wrong. >> >> But when I run "Engine-setup" I got stucked with >> >> "[ INFO ] Stage: Setup validation >> [WARNING] Less than 16384MB of memory is available >> [ ERROR ] Failed to execute stage 'Setup validatio
Re: [ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0
On Mon, Jun 27, 2016 at 10:08:33AM +0200, Stefano Danzi wrote: > Hi! Thanks for the detailed logging! > > The broker error is: > > ==> /var/log/ovirt-hosted-engine-ha/agent.log <== > MainThread::INFO::2016-06-27 > 09:27:03,311::brokerlink::140::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) > Success, id 140293563619152 > > ==> /var/log/ovirt-hosted-engine-ha/broker.log <== > Thread-25::ERROR::2016-06-27 > 09:27:03,314::listener::182::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle) > Error while serving connection > Traceback (most recent call last): > File > "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py", > line 166, in handle > data) > File > "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py", > line 299, in _dispatch > .set_storage_domain(client, sd_type, **options) > File > "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", > line 66, in set_storage_domain > self._backends[client].connect() > File > "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", > line 400, in connect > volUUID=volume.volume_uuid > File > "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", > line 245, in _get_volume_path > volUUID We have two issues here. First is that https://gerrit.ovirt.org/gitweb?p=ovirt-hosted-engine-ha.git;a=blob;f=ovirt_hosted_engine_ha/lib/storage_backends.py;h=f2fbdc43d0e4afd7539a3a1de75de0cb07bdca9d;hb=HEAD#l271 is still using vdscli to contact vdsm, instead of the preferred jsonrpccli. The second is that vdscli.connect's heuristic ends up reading the local server address from vdsm config, where it finds the default ipv6-local address of "::". Please try setting [addresses] management_ip='0.0.0.0' in your /etc/vdsm/vdsm.conf instead of the crontab hacks. Would you please open a bug about the two issues (ovirt-hosted-engine-ha and vdsm networking)? Would you report the output of `netstats -nltp` on your host, as I do not completely understand why no interface (not even the loopback one) was listening on ipv6? Regards, Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0
Do you have any 3.5 clusters? You can only upgrade to 4.0, if all the cluster are 3.6 compatibility. Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: yd...@redhat.com IRC : ydary On Tue, Jun 28, 2016 at 1:22 PM, Ricky Schneberger wrote: > On 2016-06-28 10:21, Yedidyah Bar David wrote: > > On Tue, Jun 28, 2016 at 10:53 AM, Ricky Schneberger > > wrote: > >> On 2016-06-27 19:15, Fernando Fuentes wrote: > >> > >> Ricky, > >> > >> I am under the impression that the DB migration was implemented in > >> release 3.6.6. > >> > >> I might be wrong. > >> > >> https://www.ovirt.org/release/3.6.6/ > >> > >> What's New in 3.6.6? > >> Enhancement > >> oVirt Engine > >> > >> BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from > >> el6->el7. > >> BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored > >> on 3.6 on el7 > >> Feature: > >> > >> Allow engine-backup on el7 to restore backups taken on el6. > >> > >> Reason: > >> > >> engine 4.0 does not support el6. Users that want to upgrade from 3.6 on > >> el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 > >> and restore on 4.0/el7. > >> > >> This feature, backported from 4.0, allows to do such a migration also in > >> 3.6. > >> > >> Result: > >> > >> Using this flow, it's possible to migrate a el6 setup to el7: > >> > >> On the existing engine machine run: > >> 1. engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log > >> > >> On a new el7 machine: > >> 2. Install engine, including dwh if it was set up on el6. > >> 3. Copy engine-3.6.bck to the el7 machine > >> 4. engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log > >> --provision-db --no-restore-permissions > >> 5. engine-setup > >> > >> Check engine-backup documentation for other options, including using > >> remote databases, extra grants/permissions, etc. > >> > >> > >> One step forward, two backward > >> > >> - upgrade the old EL6 to ovirt 3.6.6 > >> - engine-backup --mode=backup --file=engine-backup.tar.gz > --log=backup.log > >> - install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm, > to > >> have ovirt-engine 4.0.0.6. > >> - yum install ovirt-engine > >> - engine-backup --mode=restore --no-restore-permissions --provision-db > >> --file=engine-backup.tar.gz --log=engine-backup-restore.log > >> > >> Then I got this error... > >> > >> "Preparing to restore: > >> - Unpacking file 'engine-backup.tar.gz' > >> Restoring: > >> - Files > >> > -- > >> Please note: > >> > >> Operating system is different from the one used during backup. > >> Current operating system: centos7 > >> Operating system at backup: centos6 > >> > >> Apache httpd configuration will not be restored. > >> You will be asked about it on the next engine-setup run. > >> > -- > >> Provisioning PostgreSQL users/databases: > >> - user 'engine', database 'engine' > >> Restoring: > >> FATAL: Can't connect to database 'ovirt_engine_history'. Please see > >> '/usr/bin/engine-backup --help'." > >> > > The backup/restore here is just like normal ones, so for details you can > read > > the output of 'engine-backup --help' or [1]. > > > > In your specific case, you seem to have dwh in your backup. > > > > To restore it, you have to either prepare a database with the same > credentials > > as the one used in the old machine, or, if it was > automatically-provisioned by > > engine-setup, you can pass the option '--provision-dwh-db' to make > engine-backup > > create it for you. > > > > I think I should add an option '--provision-all-databases' or something > like > > that. Didn't feel very good about it so never done, and no-one asked for > it... > > > > Best regards, > > > > [1] > http://www.ovirt.org/develop/release-management/features/engine/engine-backup/ > > > > > > #engine-backup --mode=restore --no-restore-permissions --provision-db > --provision-dwh-db --provision-reports-db --file=engine-backup.tar.gz > --log=engine-backup-restore.log > > Success with the restore! > > Thanks for pointing me out. What I did was just following the > documentation, right or wrong. > > But when I run "Engine-setup" I got stucked with > > "[ INFO ] Stage: Setup validation > [WARNING] Less than 16384MB of memory is available > [ ERROR ] Failed to execute stage 'Setup validation': Trying to upgrade > from unsupported versions: 3.5 > [ INFO ] Stage: Clean up > Log file is located at > /var/log/ovirt-engine/setup/ovirt-engine-setup-20160628120936-ix7pb8.log > [ INFO ] Generating answer file > '/var/lib/ovirt-engine/setup/answers/20160628121149-setup.conf' > [ INFO ] Stage: Pre-termination > [ INFO ] Stage: Termination > [ ERROR ] Execution of setup failed" > > Seems to be something missing fr
Re: [ovirt-users] Security Groups
We are looking to add support for OVN in coming versions of oVirt and with that support of overlay networking. Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: yd...@redhat.com IRC : ydary On Mon, Jun 27, 2016 at 8:45 PM, Pavel Gashev wrote: > Hello, > > Currently oVirt supports network security groups for OpenStack network > provider only. Are there plans to implement Security Groups for native > networks? > > Technically, I can configure a vNic profile with some Security Groups > UUID, and apply it in before_device_create and before_update_device VDSM > hooks as filterref to some custom nwfilter. The only issue is that I have > to manually edit and distribute nwfilter xml among hardware nodes. If I > want isolate set of VMs, I have to manually maintain MAC addresses of VMs > in that xml. > > It would be great if oVirt web interface had a nwfilter editor. Are there > plans for it? > > Thanks > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VDI experience to share?
>On that same note... I would love to deploy several Thin clients around my >house using a single Centos Server for my kids to use. >Is this still not possible? >Do I still have to assign each of my kids a vm? >Regards, >-- >Fernando Fuentes >ffuen...@txweather.org >http://www.txweather.org >On Wed, Jun 15, 2016, at 12:20 PM, Gianluca Cecchi wrote: This depend on what you implement on server side and how you configure it. If you thought about a centos server with ovirt, then you can do as you want : assign each kid a VM, or makes VM they can both access. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0
On 2016-06-28 10:21, Yedidyah Bar David wrote: > On Tue, Jun 28, 2016 at 10:53 AM, Ricky Schneberger > wrote: >> On 2016-06-27 19:15, Fernando Fuentes wrote: >> >> Ricky, >> >> I am under the impression that the DB migration was implemented in >> release 3.6.6. >> >> I might be wrong. >> >> https://www.ovirt.org/release/3.6.6/ >> >> What's New in 3.6.6? >> Enhancement >> oVirt Engine >> >> BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from >> el6->el7. >> BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored >> on 3.6 on el7 >> Feature: >> >> Allow engine-backup on el7 to restore backups taken on el6. >> >> Reason: >> >> engine 4.0 does not support el6. Users that want to upgrade from 3.6 on >> el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 >> and restore on 4.0/el7. >> >> This feature, backported from 4.0, allows to do such a migration also in >> 3.6. >> >> Result: >> >> Using this flow, it's possible to migrate a el6 setup to el7: >> >> On the existing engine machine run: >> 1. engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log >> >> On a new el7 machine: >> 2. Install engine, including dwh if it was set up on el6. >> 3. Copy engine-3.6.bck to the el7 machine >> 4. engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log >> --provision-db --no-restore-permissions >> 5. engine-setup >> >> Check engine-backup documentation for other options, including using >> remote databases, extra grants/permissions, etc. >> >> >> One step forward, two backward >> >> - upgrade the old EL6 to ovirt 3.6.6 >> - engine-backup --mode=backup --file=engine-backup.tar.gz --log=backup.log >> - install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm, to >> have ovirt-engine 4.0.0.6. >> - yum install ovirt-engine >> - engine-backup --mode=restore --no-restore-permissions --provision-db >> --file=engine-backup.tar.gz --log=engine-backup-restore.log >> >> Then I got this error... >> >> "Preparing to restore: >> - Unpacking file 'engine-backup.tar.gz' >> Restoring: >> - Files >> -- >> Please note: >> >> Operating system is different from the one used during backup. >> Current operating system: centos7 >> Operating system at backup: centos6 >> >> Apache httpd configuration will not be restored. >> You will be asked about it on the next engine-setup run. >> -- >> Provisioning PostgreSQL users/databases: >> - user 'engine', database 'engine' >> Restoring: >> FATAL: Can't connect to database 'ovirt_engine_history'. Please see >> '/usr/bin/engine-backup --help'." >> > The backup/restore here is just like normal ones, so for details you can read > the output of 'engine-backup --help' or [1]. > > In your specific case, you seem to have dwh in your backup. > > To restore it, you have to either prepare a database with the same credentials > as the one used in the old machine, or, if it was automatically-provisioned by > engine-setup, you can pass the option '--provision-dwh-db' to make > engine-backup > create it for you. > > I think I should add an option '--provision-all-databases' or something like > that. Didn't feel very good about it so never done, and no-one asked for it... > > Best regards, > > [1] > http://www.ovirt.org/develop/release-management/features/engine/engine-backup/ > > #engine-backup --mode=restore --no-restore-permissions --provision-db --provision-dwh-db --provision-reports-db --file=engine-backup.tar.gz --log=engine-backup-restore.log Success with the restore! Thanks for pointing me out. What I did was just following the documentation, right or wrong. But when I run "Engine-setup" I got stucked with "[ INFO ] Stage: Setup validation [WARNING] Less than 16384MB of memory is available [ ERROR ] Failed to execute stage 'Setup validation': Trying to upgrade from unsupported versions: 3.5 [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160628120936-ix7pb8.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20160628121149-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed" Seems to be something missing from an earlier db-upgrade? -- Ricky Schneberger Use PGP to protect your own privacy! Key fingerprint = 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63 signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0
On Tue, Jun 28, 2016 at 10:53 AM, Ricky Schneberger wrote: > On 2016-06-27 19:15, Fernando Fuentes wrote: > > Ricky, > > I am under the impression that the DB migration was implemented in > release 3.6.6. > > I might be wrong. > > https://www.ovirt.org/release/3.6.6/ > > What's New in 3.6.6? > Enhancement > oVirt Engine > > BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from > el6->el7. > BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored > on 3.6 on el7 > Feature: > > Allow engine-backup on el7 to restore backups taken on el6. > > Reason: > > engine 4.0 does not support el6. Users that want to upgrade from 3.6 on > el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 > and restore on 4.0/el7. > > This feature, backported from 4.0, allows to do such a migration also in > 3.6. > > Result: > > Using this flow, it's possible to migrate a el6 setup to el7: > > On the existing engine machine run: > 1. engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log > > On a new el7 machine: > 2. Install engine, including dwh if it was set up on el6. > 3. Copy engine-3.6.bck to the el7 machine > 4. engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log > --provision-db --no-restore-permissions > 5. engine-setup > > Check engine-backup documentation for other options, including using > remote databases, extra grants/permissions, etc. > > > One step forward, two backward > > - upgrade the old EL6 to ovirt 3.6.6 > - engine-backup --mode=backup --file=engine-backup.tar.gz --log=backup.log > - install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm, to > have ovirt-engine 4.0.0.6. > - yum install ovirt-engine > - engine-backup --mode=restore --no-restore-permissions --provision-db > --file=engine-backup.tar.gz --log=engine-backup-restore.log > > Then I got this error... > > "Preparing to restore: > - Unpacking file 'engine-backup.tar.gz' > Restoring: > - Files > -- > Please note: > > Operating system is different from the one used during backup. > Current operating system: centos7 > Operating system at backup: centos6 > > Apache httpd configuration will not be restored. > You will be asked about it on the next engine-setup run. > -- > Provisioning PostgreSQL users/databases: > - user 'engine', database 'engine' > Restoring: > FATAL: Can't connect to database 'ovirt_engine_history'. Please see > '/usr/bin/engine-backup --help'." > The backup/restore here is just like normal ones, so for details you can read the output of 'engine-backup --help' or [1]. In your specific case, you seem to have dwh in your backup. To restore it, you have to either prepare a database with the same credentials as the one used in the old machine, or, if it was automatically-provisioned by engine-setup, you can pass the option '--provision-dwh-db' to make engine-backup create it for you. I think I should add an option '--provision-all-databases' or something like that. Didn't feel very good about it so never done, and no-one asked for it... Best regards, [1] http://www.ovirt.org/develop/release-management/features/engine/engine-backup/ > I have attached the engine-backup-restore.log. > > //Ricky > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0
On 2016-06-27 19:15, Fernando Fuentes wrote: > Ricky, > > I am under the impression that the DB migration was implemented in > release 3.6.6. > > I might be wrong. > > https://www.ovirt.org/release/3.6.6/ > > What's New in 3.6.6? > Enhancement > oVirt Engine > > BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from > el6->el7. > BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored > on 3.6 on el7 > Feature: > > Allow engine-backup on el7 to restore backups taken on el6. > > Reason: > > engine 4.0 does not support el6. Users that want to upgrade from 3.6 on > el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 > and restore on 4.0/el7. > > This feature, backported from 4.0, allows to do such a migration also in > 3.6. > > Result: > > Using this flow, it's possible to migrate a el6 setup to el7: > > On the existing engine machine run: > 1. engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log > > On a new el7 machine: > 2. Install engine, including dwh if it was set up on el6. > 3. Copy engine-3.6.bck to the el7 machine > 4. engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log > --provision-db --no-restore-permissions > 5. engine-setup > > Check engine-backup documentation for other options, including using > remote databases, extra grants/permissions, etc. > One step forward, two backward - upgrade the old EL6 to ovirt 3.6.6 - engine-backup --mode=backup --file=engine-backup.tar.gz --log=backup.log - install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm, to have ovirt-engine 4.0.0.6. - yum install ovirt-engine - |engine-backup --mode=restore --no-restore-permissions --provision-db --file=engine-backup.tar.gz --log=engine-backup-restore.log Then I got this error... "Preparing to restore: - Unpacking file 'engine-backup.tar.gz' Restoring: - Files -- Please note: Operating system is different from the one used during backup. Current operating system: centos7 Operating system at backup: centos6 Apache httpd configuration will not be restored. You will be asked about it on the next engine-setup run. -- Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' Restoring: FATAL: Can't connect to database 'ovirt_engine_history'. Please see '/usr/bin/engine-backup --help'." I have attached the engine-backup-restore.log. //Ricky | 2016-06-28 09:42:01 20260: Start of engine-backup mode restore scope all file engine-backup.tar.gz 2016-06-28 09:42:01 20260: OUTPUT: Preparing to restore: 2016-06-28 09:42:01 20260: OUTPUT: - Unpacking file 'engine-backup.tar.gz' 2016-06-28 09:42:01 20260: Opening tarball engine-backup.tar.gz to /tmp/engine-backup.YuNYQaC9J3 2016-06-28 09:42:02 20260: Verifying md5 2016-06-28 09:42:02 20260: Verifying version 2016-06-28 09:42:02 20260: Reading config 2016-06-28 09:42:02 20260: OUTPUT: Restoring: 2016-06-28 09:42:02 20260: OUTPUT: - Files 2016-06-28 09:42:02 20260: Restoring files 2016-06-28 09:42:02 20260: Reloading configuration 2016-06-28 09:42:02 20260: OUTPUT: Provisioning PostgreSQL users/databases: 2016-06-28 09:42:02 20260: provisionDB: user engine host localhost port 5432 database engine secured False secured_host_validation False 2016-06-28 09:42:02 20260: OUTPUT: - user 'engine', database 'engine' [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf', '/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf', '/tmp/engine-backup.YuNYQaC9J3/pg-provision-answer-file'] Log file: /var/log/ovirt-engine/setup/ovirt-engine-provisiondb-20160628094202-nwcp21.log Version: otopi-1.5.0 (otopi-1.5.0-1.el7.centos) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment customization [ INFO ] Stage: Setup validation [ INFO ] Stage: Transaction setup [ INFO ] Stage: Misc configuration [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Creating PostgreSQL 'engine' database [ INFO ] Configuring PostgreSQL [ INFO ] Stage: Transaction commit [ INFO ] Stage: Closing up [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-provisiondb-20160628094202-nwcp21.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ INFO ] Execution of provisiondb completed successfully 2016-06-28 09:42:08 20260: OUTPUT: Restoring: 2016-06-28 09:42:08 20260: Generating pgpass 2016-06-28 09:42:08 20260: Verifying connection 2016-06-28 09:42:08 20260: pg_cmd running: psql -w -U engine -h localhost -p 5432 engine -c select 1 ?column? -- 1 (1 row) 2016-06-28 09:42:08 20260: pg_cmd running: psql -w -U
Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0
On 2016-06-28 08:37, Ricky Schneberger wrote: > On 2016-06-27 23:52, Simone Tiraboschi wrote: >> >> >> Il 27 Giu 2016 18:18, "Ricky Schneberger" ha >> scritto: >> > >> > On 2016-06-27 17:44, Simone Tiraboschi wrote: >> > > On Mon, Jun 27, 2016 at 5:05 PM, Ricky Schneberger >> mailto:ri...@schneberger.se>> wrote: >> > >> Hi, >> > >> >> > >> I ran my oVirt 3.6 on Centos6 and because of that I had to do a >> manual >> > >> migration when trying to move to oVirt 4.0. >> > >> >> > >> http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/ >> > >> >> > >> Everything went OK until I did the restore, >> > >> >> > >> ## engine-backup --mode=restore --no-restore-permissions >> --provision-db >> > >> --file=engine-backup.tar.gz --log=engine-backup-restore.log >> > >> >> > >> Preparing to restore: >> > >> - Unpacking file 'engine-backup.tar.gz' >> > >> FATAL: Backup was created by version '3.6' and can not be >> restored using >> > >> the installed version 4.1 >> > > This looks pretty strange: it should be 4.0 and it should work. >> > > >> > > Can you please share the list of oVirt packages you installed on the >> > > engine server? >> > > Can you please share your oVirt repo details? >> > > >> > >> and then I got stucked. Is there something I need to do when I >> do the >> > >> backup? >> > >> >> > >> My old oVirt-engine was version ovirt-engine-3.6.3.4-1.el6.noarch >> > >> >> > >> regards >> > >> >> > >> -- >> > >> Ricky Schneberger >> > >> > I attached my repo files and below you find parts of my yum.log. >> >> OK, the issue is here: ovirt-master-snapshot is the nightly build >> repo from the development branch. >> If you want something stable, please downgrade to 4.0. >> >> > The ovirt-master-snapshot is enabled by default when following the > migration documentation. I don't think this is an good idea. > > Regards //Ricky > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users OK, when using the right repos, http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm, I got ovirt-engine 4.0.0.6. Thanks. -- Ricky Schneberger Use PGP to protect your own privacy! Key fingerprint = 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63 signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
