Re: [Users] Problem with DWH installation
Hi Michael
The dwh version you are trying to install is unfortunately no longer compatible
with ovirt-engine-3.3. You will need ovirt-engine-dwh-3.3 for it to work.
Alex.
--
Best regards,
Alex Lourie
Software Developer in Integration
Red Hat
- Original Message -
> From: "Michael Wagenknecht"
> To: "users"
> Sent: Tuesday, November 5, 2013 4:12:34 PM
> Subject: [Users] Problem with DWH installation
>
> Hi,
>
> I cannot install the Ovirt DWH.
> Here is the logfile:
>
> 2013-11-05 15:00:12::DEBUG::ovirt-engine-dwh-setup::250::root:: starting
> main()
> 2013-11-05 15:00:12::DEBUG::common_utils::415::root:: found existing
> pgpass file, fetching DB host value
> 2013-11-05 15:00:12::DEBUG::common_utils::415::root:: found existing
> pgpass file, fetching DB port value
> 2013-11-05 15:00:12::DEBUG::common_utils::415::root:: found existing
> pgpass file, fetching DB admin value
> 2013-11-05 15:00:12::DEBUG::common_utils::415::root:: found existing
> pgpass file, fetching DB admin value
> 2013-11-05 15:00:12::DEBUG::common_utils::448::root:: getting DB
> password for postgres
> 2013-11-05 15:00:12::DEBUG::common_utils::457::root:: found password for
> username postgres
> 2013-11-05 15:00:12::DEBUG::common_utils::58::root:: getting vdc option
> MinimalETLVersion
> 2013-11-05 15:00:12::DEBUG::common_utils::512::root:: Executing command
> --> '['/usr/bin/engine-config', '-g', 'MinimalETLVersion',
> '--cver=general', '-p',
> '/usr/share/ovirt-engine/conf/engine-config-install.properties']'
> 2013-11-05 15:00:13::DEBUG::common_utils::551::root:: output =
> 2013-11-05 15:00:13::DEBUG::common_utils::552::root:: stderr = Files
> /usr/share/ovirt-engine/conf/engine-config-install.properties does not exist
>
> 2013-11-05 15:00:13::DEBUG::common_utils::553::root:: retcode = 1
> 2013-11-05 15:00:13::ERROR::ovirt-engine-dwh-setup::294::root::
> Exception caught!
> 2013-11-05 15:00:13::ERROR::ovirt-engine-dwh-setup::295::root::
> Traceback (most recent call last):
>File "/usr/bin/ovirt-engine-dwh-setup", line 255, in main
> minimalVersion = utils.getVDCOption("MinimalETLVersion")
>File "/usr/share/ovirt-engine-dwh/common_utils.py", line 60, in
> getVDCOption
> output, rc = execCmd(cmdList=cmd, failOnError=True, msg="Error:
> failed fetching configuration field %s" % key)
>File "/usr/share/ovirt-engine-dwh/common_utils.py", line 556, in execCmd
> raise Exception(msg)
> Exception: Error: failed fetching configuration field MinimalETLVersion
>
>
> This are the installed packages:
>
> ovirt-engine-dwh-3.2.0-1.el6.noarch
> ovirt-release-el6-8-1.noarch
> ovirt-engine-sdk-python-3.3.0.6-1.el6.noarch
> ovirt-host-deploy-java-1.1.1-1.el6.noarch
> ovirt-engine-dbscripts-3.3.0.1-1.el6.noarch
> ovirt-engine-reports-3.2.0-2.el6.noarch
> ovirt-engine-lib-3.3.0.1-1.el6.noarch
> ovirt-engine-setup-3.3.0.1-1.el6.noarch
> ovirt-log-collector-3.3.1-1.el6.noarch
> ovirt-image-uploader-3.3.1-1.el6.noarch
> ovirt-host-deploy-1.1.1-1.el6.noarch
> ovirt-engine-webadmin-portal-3.3.0.1-1.el6.noarch
> ovirt-engine-restapi-3.3.0.1-1.el6.noarch
> ovirt-engine-tools-3.3.0.1-1.el6.noarch
> ovirt-engine-backend-3.3.0.1-1.el6.noarch
> ovirt-engine-cli-3.3.0.4-1.el6.noarch
> ovirt-iso-uploader-3.3.1-1.el6.noarch
> ovirt-engine-userportal-3.3.0.1-1.el6.noarch
> ovirt-engine-3.3.0.1-1.el6.noarch
>
>
> Can you help me?
>
> Best regards,
> Michael
>
> ___
> 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: [Users] VMs and volumes disappearing
In order to upgrade, it would be 'engine-setup' :-) -- Best regards, Alex Lourie Software Developer in Integration Red Hat - Original Message - > From: "Itamar Heim" > To: "Yair Zaslavsky" > Cc: users@ovirt.org > Sent: Tuesday, October 1, 2013 3:21:36 PM > Subject: Re: [Users] VMs and volumes disappearing > > On 10/01/2013 03:04 PM, Yair Zaslavsky wrote: > >> > > >>>> > >>I think I have an idea about what happended now. > >>>> > >> > >>>> > >>The 2 disappeared VMs have been imported into oVirt using virt-v2v. > >>>> > >>The > >>>> > >>3rd one that's now missing a disk volume was not, but I have been > >>>> > >>playing with storage migration in the past. > >>> > > > >>> > >Then this is the reason, other users have complained about it at > >>> > >users@ovirt.org > >> > > >> >I have read the thread about disappearing VMs from August and indeed it > >> >sounds like this might me the same problem. > >> > > >>> > >Upgrade I just talked with Ofer (CC'ed), our release engineer, and he > >>> > >said that all packages should be 3.3.0-4 (notice ovirt-engine is > >>> > >not) I hope this helps you out, > >> > > >> >There are no updates, at least Yum doesn't give me any. I enabled the > >> >beta channel just now, but that doesn't make a difference. 3.3.0-1 is > >> >the latest version. What am I missing? > >> > > >> >martijn@ovirt:~> sudo yum list all|grep ovirt-engine.noarch > >> >ovirt-engine.noarch 3.3.0-1.el6@ovirt-beta > > I'll let ofer answer that. > > > > you should run ovirt-check-update and ovirt-engine-upgrade (or > ovirt-engine-setup) to get updates for engine. we use version lock to > prevent yum for updating the rpm without proper sync of db/backup/rollback. > ___ > 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: [Users] update from 3.3 beta to RC failed during db upgrade
I think we already have such a tool. Will check with Eli and update. -- Best regards, Alex Lourie Software Developer in Integration Red Hat - Original Message - > From: "Jakub Bittner" > To: "Alon Bar-Lev" > Cc: "Alex Lourie" , "Eli Mesika" , > users@ovirt.org > Sent: Tuesday, August 27, 2013 6:31:11 PM > Subject: Re: [Users] update from 3.3 beta to RC failed during db upgrade > > Dne 27.8.2013 16:13, Alon Bar-Lev napsal(a): > > > > - Original Message - > >> From: "Jakub Bittner" > >> Cc: users@ovirt.org > >> Sent: Tuesday, August 27, 2013 4:33:34 PM > >> Subject: Re: [Users] update from 3.3 beta to RC failed during db upgrade > >> > >> Dne 26.8.2013 15:13, Alex Lourie napsal(a): > >>> Sure, I'll investigate. > >>> > >> Maybe I found a problem which causes function owner to be postgre. I use > >> restore command as postgre (as on wiki: > >> http://wiki.ovirt.org/User:Adrian15/oVirt_engine_migration#Restore_Postgresql_database > >> ) > >> > >> cd /usr/share/ovirt-engine/dbscripts > >> ./restore.sh -u postgres -f /path/to/engine_sql_DATE.sql -r > > Nice! > > Thank you! > > > > Eli, can you please confirm, or suggest alternate way. > > > > We should probably provide a script to change ownership for users who made > > restore. > > > > Regards, > > Alon > That script would be perfect, because I dont know how to easily switch > owner of function. > > Last time I did it by exporting db, manually change owner postgre to > owner engine in sql backup file and restore db from it. > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] update from 3.3 beta to RC failed during db upgrade
Sure, I'll investigate. -- Best regards, Alex Lourie Software Developer in Integration Red Hat - Original Message - > From: "Alon Bar-Lev" > To: "Alex Lourie" > Cc: "Jakub Bittner" , users@ovirt.org > Sent: Monday, August 26, 2013 3:02:48 PM > Subject: Re: [Users] update from 3.3 beta to RC failed during db upgrade > > > > - Original Message - > > From: "Alex Lourie" > > To: "Alon Bar-Lev" > > Cc: "Jakub Bittner" , users@ovirt.org > > Sent: Monday, August 26, 2013 3:00:12 PM > > Subject: Re: [Users] update from 3.3 beta to RC failed during db upgrade > > > > Simple guess? An upgrade from 3.1; or early versions of 3.2; we had > > postgres > > as the owner of those objects then. Upgrade didn't change that. > > > > Alex, we must fix that. > Are you sure that 3.1 used postgres as owner? > I thought we always used the engine user to create the database. > Please confirm we have an issue, if we do, we need to add change ownership of > objects when upgrade from legacy. > > > -- > > > > Best regards, > > > > Alex Lourie > > Software Developer in Integration > > Red Hat > > > > > > - Original Message - > > > From: "Alon Bar-Lev" > > > To: "Jakub Bittner" > > > Cc: users@ovirt.org, "Alex Lourie" > > > Sent: Monday, August 26, 2013 2:06:53 PM > > > Subject: Re: [Users] update from 3.3 beta to RC failed during db upgrade > > > > > > > > > > > > - Original Message - > > > > From: "Jakub Bittner" > > > > To: "Alon Bar-Lev" > > > > Cc: users@ovirt.org > > > > Sent: Monday, August 26, 2013 2:04:58 PM > > > > Subject: Re: [Users] update from 3.3 beta to RC failed during db > > > > upgrade > > > > > > > > Dne 26.8.2013 12:40, Alon Bar-Lev napsal(a): > > > > > > > > > > - Original Message - > > > > >> From: "Jakub Bittner" > > > > >> To: users@ovirt.org > > > > >> Sent: Monday, August 26, 2013 1:37:24 PM > > > > >> Subject: Re: [Users] update from 3.3 beta to RC failed during db > > > > >> upgrade > > > > >> > > > > >> Dne 26.8.2013 12:18, Bittner Jakub napsal(a): > > > > >> > > > > >> > > > > >> > > > > >> On 26.8.2013 11:45, Alon Bar-Lev wrote: > > > > >> > > > > >> > > > > >> > > > > >> - Original Message - > > > > >> > > > > >> > > > > >> > > > > >> From: "Jakub Bittner" To: users@ovirt.org Sent: > > > > >> Monday, > > > > >> August 26, 2013 12:23:48 PM > > > > >> Subject: [Users] update from 3.3 beta to RC failed during db upgrade > > > > >> > > > > >> I tryed updating 3.3 fom beta to rc, but it failed during db > > > > >> upgrade. > > > > >> > > > > >> > > > > >> [ ERROR ] Failed to execute stage 'Misc configuration': Command > > > > >> '/usr/share/ovirt-engine/dbscripts/upgrade.sh' failed to execute > > > > >> > > > > >> and in log: > > > > >> > > > > >> 2013-08-26 08:33:01 DEBUG > > > > >> oto**FILTERED**i.**FILTERED**lugins.ovirt_engine_setu**FILTERED**.db.schema > > > > >> **FILTERED**lugin.execute:446 execute-out**FILTERED**ut: > > > > >> ['/usr/share/ovirt-engine/dbscri**FILTERED**ts/u**FILTERED**grade.sh', > > > > >> '-s', 'localhost', '-**FILTERED**', '5432', '-u', $ > > > > >> **FILTERED**sql:common_s**FILTERED**.sql:20: ERROR: must be owner > > > > >> of > > > > >> function fn_db_add_column > > > > >> Can you please provide full log? > > > > >> Of course. > > > > >> https://docs.google.com/file/d/0B7oyL6-mZeEDUW9GU3I0bkRfQ0U > > > > >> > > > > >> > > > > >> ___ > > > > >> Users mailing list Users@ovirt.org > > > > >> http://lists.ovirt.org/mailman/listinfo/users > > > > >> > > > > >> I changed all function owner from postgre to engine and upgrade > > > > >> works. > > > > >> The > > > > >> question is, why owner was postgre. ;-) > > > > > > > > > > Well, we create all objects at the ownership of the engine user. > > > > > > > > > > Can it be installation of 3.2 and upgrade? > > > > > > > > > >> ___ > > > > >> Users mailing list > > > > >> Users@ovirt.org > > > > >> http://lists.ovirt.org/mailman/listinfo/users > > > > >> > > > > Yes, it is 3.2 upgraded to 3.3beta and now 3.3rc. > > > > > > > > > > Oh... > > > > > > Alex, > > > Can you check in which sequence do we have database owned by postgres > > > user? > > > Maybe 3.2 upstream had some issue in setting up correct privileges? > > > > > > Thanks, > > > Alon > > > > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] update from 3.3 beta to RC failed during db upgrade
Simple guess? An upgrade from 3.1; or early versions of 3.2; we had postgres as the owner of those objects then. Upgrade didn't change that. -- Best regards, Alex Lourie Software Developer in Integration Red Hat - Original Message - > From: "Alon Bar-Lev" > To: "Jakub Bittner" > Cc: users@ovirt.org, "Alex Lourie" > Sent: Monday, August 26, 2013 2:06:53 PM > Subject: Re: [Users] update from 3.3 beta to RC failed during db upgrade > > > > - Original Message - > > From: "Jakub Bittner" > > To: "Alon Bar-Lev" > > Cc: users@ovirt.org > > Sent: Monday, August 26, 2013 2:04:58 PM > > Subject: Re: [Users] update from 3.3 beta to RC failed during db upgrade > > > > Dne 26.8.2013 12:40, Alon Bar-Lev napsal(a): > > > > > > - Original Message - > > >> From: "Jakub Bittner" > > >> To: users@ovirt.org > > >> Sent: Monday, August 26, 2013 1:37:24 PM > > >> Subject: Re: [Users] update from 3.3 beta to RC failed during db upgrade > > >> > > >> Dne 26.8.2013 12:18, Bittner Jakub napsal(a): > > >> > > >> > > >> > > >> On 26.8.2013 11:45, Alon Bar-Lev wrote: > > >> > > >> > > >> > > >> - Original Message - > > >> > > >> > > >> > > >> From: "Jakub Bittner" To: users@ovirt.org Sent: > > >> Monday, > > >> August 26, 2013 12:23:48 PM > > >> Subject: [Users] update from 3.3 beta to RC failed during db upgrade > > >> > > >> I tryed updating 3.3 fom beta to rc, but it failed during db upgrade. > > >> > > >> > > >> [ ERROR ] Failed to execute stage 'Misc configuration': Command > > >> '/usr/share/ovirt-engine/dbscripts/upgrade.sh' failed to execute > > >> > > >> and in log: > > >> > > >> 2013-08-26 08:33:01 DEBUG > > >> oto**FILTERED**i.**FILTERED**lugins.ovirt_engine_setu**FILTERED**.db.schema > > >> **FILTERED**lugin.execute:446 execute-out**FILTERED**ut: > > >> ['/usr/share/ovirt-engine/dbscri**FILTERED**ts/u**FILTERED**grade.sh', > > >> '-s', 'localhost', '-**FILTERED**', '5432', '-u', $ > > >> **FILTERED**sql:common_s**FILTERED**.sql:20: ERROR: must be owner of > > >> function fn_db_add_column > > >> Can you please provide full log? > > >> Of course. https://docs.google.com/file/d/0B7oyL6-mZeEDUW9GU3I0bkRfQ0U > > >> > > >> > > >> ___ > > >> Users mailing list Users@ovirt.org > > >> http://lists.ovirt.org/mailman/listinfo/users > > >> > > >> I changed all function owner from postgre to engine and upgrade works. > > >> The > > >> question is, why owner was postgre. ;-) > > > > > > Well, we create all objects at the ownership of the engine user. > > > > > > Can it be installation of 3.2 and upgrade? > > > > > >> ___ > > >> Users mailing list > > >> Users@ovirt.org > > >> http://lists.ovirt.org/mailman/listinfo/users > > >> > > Yes, it is 3.2 upgraded to 3.3beta and now 3.3rc. > > > > Oh... > > Alex, > Can you check in which sequence do we have database owned by postgres user? > Maybe 3.2 upstream had some issue in setting up correct privileges? > > Thanks, > Alon > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Fedora upgrading from 3.1 to 3.2
@Alon Upgrade from 3.1 to 3.2 doesn't work in upstream, that's why we are doing this. @Karli - are you keeping the keys/certificates from the 3.1 installation? -- Best regards, Alex Lourie Software Developer in Integration Red Hat - Original Message - > From: "Alon Bar-Lev" > To: "Karli Sjöberg" > Cc: users@ovirt.org > Sent: Thursday, August 1, 2013 2:20:06 PM > Subject: Re: [Users] Fedora upgrading from 3.1 to 3.2 > > > > - Original Message - > > From: "Karli Sjöberg" > > To: "Alon Bar-Lev" > > Cc: users@ovirt.org > > Sent: Thursday, August 1, 2013 12:50:11 PM > > Subject: Re: [Users] Fedora upgrading from 3.1 to 3.2 > > > > tor 2013-08-01 klockan 05:29 -0400 skrev Alon Bar-Lev: > > > > > > > > - Original Message - > > > From: "Karli Sjöberg" mailto:karli.sjob...@slu.se>> > > > To: "Alon Bar-Lev" mailto:alo...@redhat.com>> > > > Cc: "Alex Lourie" mailto:alou...@redhat.com>>, > > > users@ovirt.org<mailto:users@ovirt.org>, "Eli Mesika" > > > mailto:emes...@redhat.com>> > > > Sent: Thursday, August 1, 2013 12:24:57 PM > > > Subject: Re: [Users] Fedora upgrading from 3.1 to 3.2 > > > > > > Ah, my bad, I botched that when doing the patch for "engine-setup" and > > > hadn´t > > > made an original copy so I did "yum erase" and "yum install" again to get > > > back the original file, and yum was nice enough to erase and install > > > blank > > > files for me, heh. Now I´m back again and once more updated those option > > > values in the database, but I´m still not able to log in. The log is > > > attached. > > > > The engine.log you sent is too short for typical log... > > > > Can we start from scratch? > > What exactly are you doing? > > What sequence? > > > > > > OK, to make a long story a little shorter. I´m trying to go from oVirt-3.1 > > to > > oVirt-3.2 on Fedora, so this is what I have done so far: > > > > (After Fedora is up to 18, and the old engine is up and running, I was able > > to log in) > > - Erase all of the 3.1-packages > > - Install the new 3.2-packages > > - Have to go about the dbase upgrade like this: > > # psql -U postgres engine > > $ ALTER FUNCTION uuid_generate_v1() OWNER TO engine; > > $ \q > > Or the upgrade won´t work. After that it´s possible to: > > # cd /usr/share/ovirt-engine/dbscripts > > # ./upgrade.sh -s localhost -p 5432 -u engine -d engine > > (lots of output) > > # engine-cleanup --dont-drop-db > > > > - Had to make modifications to "/usr/bin/engine-setup" for the setup to > > complete OK. > > @@ -1142,8 +1142,8 @@ > > # Run db backup > > utils.backupDB( > > db=basedefs.DB_NAME, > > -backup_file=dbBackupFile, > > -env=utils.getPgPassEnv(), > > +backupFile=dbBackupFile, > > +#env=utils.getPgPassEnv(), > > user=getDbUser(), > > host=getDbHostName(), > > port=getDbPort(), > > > > # engine-setup > > # systemctl stop ovirt-engine > > # psql -U engine engine > > $ update vdc_options set option_value = > > '/etc/pki/ovirt-engine/keys/engine.p12' where option_name = 'keystoreUrl'; > > $ update vdc_options set option_value = > > '/etc/pki/ovirt-engine/certs/engine.cer' where option_name = > > 'CertificateFileName'; > > $ update vdc_options set option_value = '/etc/pki/ovirt-engine/.truststore' > > where option_name = 'TruststoreUrl'; > > $ \q > > # cat /dev/null > /var/log/ovirt-engine/engine.log > > # systemctl restart ovirt-engine; tail -f /var/log/ovirt-engine/engine.log > > | > > tee /tmp/engine_start.log > > > > That is the log you now have seen. > > And why don't you use engine-upgrade? > > I think that in this process you probably remove your existing keys from > /etc/pki/ovirt-engine > > > > > > > > > > > Thanks, > > Alon > > > > > > -- > > > > Med Vänliga Hälsningar > > --- > > Karli Sjöberg > > Swedish University of Agricultural Sciences > > Box 7079 (Visiting Address Kronåsvägen 8) > > S-750 07 Uppsala, Sweden > > Phone: +46-(0)18-67 15 66 > > karli.sjob...@slu.se<mailto:karli.sjob...@adm.slu.se> > > > ___ > 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: [Users] Fedora upgrading from 3.1 to 3.2
Hi Karli It's been awhile since we heard from you. Would you mind updating us on your status? Thanks -- Best regards, Alex Lourie Software Developer in Integration Red Hat - Original Message - > From: "Alex Lourie" > To: "Karli Sjöberg" > Cc: users@ovirt.org > Sent: Wednesday, July 10, 2013 7:16:02 PM > Subject: Re: [Users] Fedora upgrading from 3.1 to 3.2 > > Hi Karli > > 'Restore' certificates basically means taking the backup of > /etc/pki/ovirt-engine/certs and /keys and restoring them into 3.2 after > installation. > > --dont-drop-database will do exactly that - leave DB intact; that can be for > your benefit in some cases. > > I'll be happy to hear on your progress. > > -- > > Best regards, > > Alex Lourie > Software Developer in Integration > Red Hat > > > - Original Message - > > From: "Karli Sjöberg" > > To: "Alex Lourie" > > Cc: users@ovirt.org > > Sent: Friday, July 5, 2013 8:34:22 PM > > Subject: SV: [Users] Fedora upgrading from 3.1 to 3.2 > > > > Hi Alex, > > > > crappy MS webmail that can´t figure out indents while on vacation, just > > FYI. > > Yes, progress is always good:) I would like to have some pointers about nr. > > 4: Restore certificates. Then I can ask one of my co-workers to test the > > procedure and report back. So, restore certs; How to? > > > > Or! I saw in another thread there was a "engine-cleanup --dont-drop-dbase" > > something or other... Is there an equivalent for "engine-setup", like > > "--dont-touch-dbase"? Or "engine-cleanup --dbase-something" and then > > "engine-setup" again, and it´ll just play nice with the dbase that´s still > > there perhaps? > > > > /Karli > > > > > > Från: Alex Lourie [alou...@redhat.com] > > Skickat: den 30 juni 2013 17:29 > > Till: Karli Sjöberg > > Cc: users@ovirt.org > > Ämne: Re: [Users] Fedora upgrading from 3.1 to 3.2 > > > > Hi Karli > > > > On Wed, Jun 26, 2013 at 5:28 PM, Karli Sjöberg > > wrote: > > > Update! > > > > > > I have actually made some headway, I managed to get it passed the > > > database upgrade! As I was looking at the log, I drilled down into > > > the engine-upgrade script at looked at what it was trying to do, > > > which was a pythonic way of doing: > > > # cd /usr/share/ovirt-engine/dbscripts > > > # ./upgrade.sh -s localhost -p 5432 -u engine -d engine > > > > > > > Nice progress! > > > > > > > > So I first reinstalled everything (I´ve stopped counting) and an > > > hour later I was back at just before doing engine-upgrade again. What > > > I did then was to upgrade ovirt-engine-dbscripts first and ran the > > > upgrade.sh script manually (which went by smoothly, output also > > > attached), downgraded all of the ovirt packages back to 3.1.0-4 > > > (because engine-upgrade didn´t think there was any updating to act > > > upon otherwise), then updated ovirt-engine-setup to 3.2.2, lastly ran > > > engine-upgrade. That made it pass the database upgrade, yeay! But! > > > Now it stopped at doing the CA instead... Log is attached. > > > > > > What I find strange is the last line of output from the upgrade.sh: > > > ... > > > Refreshing materialized views... > > > Done. > > > /usr/share/ovirt-engine/dbscripts > > > > > > Where the last lines of upgrade.sh are like: > > > ... > > > run_upgrade_files > > > > > > ret=$? > > > printf "Done.\n" > > > exit $ret > > > > > > And I looked through run_upgrade_files and couldn´t figure out why > > > that function would exit with "/usr/share/ovirt-engine/dbscripts"? No > > > that doesn´t quite add up. Something just doesn´t smell right but I > > > haven´t figured it out what it is yet, > > > > > > > I think it is the output from another script that runs the upgrade.sh > > script. There's a pushd/popd action used in sh scripts to change > > working folder and then get back to the original one. I think that this > > is what you see here. > > > > > > > > About the second error, with handling the CA, it seems like it´s > > > having trouble connecting to the database after it´s upgrade, but > > > since the upgrade itself went by OK, I did engine-cleanup,
Re: [Users] Fedora upgrading from 3.1 to 3.2
Hi Karli 'Restore' certificates basically means taking the backup of /etc/pki/ovirt-engine/certs and /keys and restoring them into 3.2 after installation. --dont-drop-database will do exactly that - leave DB intact; that can be for your benefit in some cases. I'll be happy to hear on your progress. -- Best regards, Alex Lourie Software Developer in Integration Red Hat - Original Message - > From: "Karli Sjöberg" > To: "Alex Lourie" > Cc: users@ovirt.org > Sent: Friday, July 5, 2013 8:34:22 PM > Subject: SV: [Users] Fedora upgrading from 3.1 to 3.2 > > Hi Alex, > > crappy MS webmail that can´t figure out indents while on vacation, just FYI. > Yes, progress is always good:) I would like to have some pointers about nr. > 4: Restore certificates. Then I can ask one of my co-workers to test the > procedure and report back. So, restore certs; How to? > > Or! I saw in another thread there was a "engine-cleanup --dont-drop-dbase" > something or other... Is there an equivalent for "engine-setup", like > "--dont-touch-dbase"? Or "engine-cleanup --dbase-something" and then > "engine-setup" again, and it´ll just play nice with the dbase that´s still > there perhaps? > > /Karli > > > Från: Alex Lourie [alou...@redhat.com] > Skickat: den 30 juni 2013 17:29 > Till: Karli Sjöberg > Cc: users@ovirt.org > Ämne: Re: [Users] Fedora upgrading from 3.1 to 3.2 > > Hi Karli > > On Wed, Jun 26, 2013 at 5:28 PM, Karli Sjöberg > wrote: > > Update! > > > > I have actually made some headway, I managed to get it passed the > > database upgrade! As I was looking at the log, I drilled down into > > the engine-upgrade script at looked at what it was trying to do, > > which was a pythonic way of doing: > > # cd /usr/share/ovirt-engine/dbscripts > > # ./upgrade.sh -s localhost -p 5432 -u engine -d engine > > > > Nice progress! > > > > > So I first reinstalled everything (I´ve stopped counting) and an > > hour later I was back at just before doing engine-upgrade again. What > > I did then was to upgrade ovirt-engine-dbscripts first and ran the > > upgrade.sh script manually (which went by smoothly, output also > > attached), downgraded all of the ovirt packages back to 3.1.0-4 > > (because engine-upgrade didn´t think there was any updating to act > > upon otherwise), then updated ovirt-engine-setup to 3.2.2, lastly ran > > engine-upgrade. That made it pass the database upgrade, yeay! But! > > Now it stopped at doing the CA instead... Log is attached. > > > > What I find strange is the last line of output from the upgrade.sh: > > ... > > Refreshing materialized views... > > Done. > > /usr/share/ovirt-engine/dbscripts > > > > Where the last lines of upgrade.sh are like: > > ... > > run_upgrade_files > > > > ret=$? > > printf "Done.\n" > > exit $ret > > > > And I looked through run_upgrade_files and couldn´t figure out why > > that function would exit with "/usr/share/ovirt-engine/dbscripts"? No > > that doesn´t quite add up. Something just doesn´t smell right but I > > haven´t figured it out what it is yet, > > > > I think it is the output from another script that runs the upgrade.sh > script. There's a pushd/popd action used in sh scripts to change > working folder and then get back to the original one. I think that this > is what you see here. > > > > > About the second error, with handling the CA, it seems like it´s > > having trouble connecting to the database after it´s upgrade, but > > since the upgrade itself went by OK, I did engine-cleanup, > > engine-setup, stopped engine, restored the database and started > > engine again, and it worked. Which should point more to something > > like a configuration being missed, or improperly handled at the > > upgrade that makes engine-config fail to connect. > > Could be; but the fact that reimport of the DB worked is a very good > sign. > > > Maybe some old configurations lying around that shouldn´t be, that > > hinders it, I don´t know. Is there anything handling configuration > > changes, like "rpmconf -a" in the upgrade process, after updating the > > rpms? > > > > No, we do not have rpmconf in ovirt. > > Now, if you have a working engine, that's good. Remember though that > you started with clean DB. When DB has entries, the upgrade.sh run may > not be as fluent as it was before. But, if it works, I guess you could > use the same s
Re: [Users] Fedora upgrading from 3.1 to 3.2
Hi Karli On Wed, Jun 26, 2013 at 5:28 PM, Karli Sjöberg wrote: Update! I have actually made some headway, I managed to get it passed the database upgrade! As I was looking at the log, I drilled down into the engine-upgrade script at looked at what it was trying to do, which was a pythonic way of doing: # cd /usr/share/ovirt-engine/dbscripts # ./upgrade.sh -s localhost -p 5432 -u engine -d engine Nice progress! So I first reinstalled everything (I´ve stopped counting) and an hour later I was back at just before doing engine-upgrade again. What I did then was to upgrade ovirt-engine-dbscripts first and ran the upgrade.sh script manually (which went by smoothly, output also attached), downgraded all of the ovirt packages back to 3.1.0-4 (because engine-upgrade didn´t think there was any updating to act upon otherwise), then updated ovirt-engine-setup to 3.2.2, lastly ran engine-upgrade. That made it pass the database upgrade, yeay! But! Now it stopped at doing the CA instead... Log is attached. What I find strange is the last line of output from the upgrade.sh: ... Refreshing materialized views... Done. /usr/share/ovirt-engine/dbscripts Where the last lines of upgrade.sh are like: ... run_upgrade_files ret=$? printf "Done.\n" exit $ret And I looked through run_upgrade_files and couldn´t figure out why that function would exit with "/usr/share/ovirt-engine/dbscripts"? No that doesn´t quite add up. Something just doesn´t smell right but I haven´t figured it out what it is yet, I think it is the output from another script that runs the upgrade.sh script. There's a pushd/popd action used in sh scripts to change working folder and then get back to the original one. I think that this is what you see here. About the second error, with handling the CA, it seems like it´s having trouble connecting to the database after it´s upgrade, but since the upgrade itself went by OK, I did engine-cleanup, engine-setup, stopped engine, restored the database and started engine again, and it worked. Which should point more to something like a configuration being missed, or improperly handled at the upgrade that makes engine-config fail to connect. Could be; but the fact that reimport of the DB worked is a very good sign. Maybe some old configurations lying around that shouldn´t be, that hinders it, I don´t know. Is there anything handling configuration changes, like "rpmconf -a" in the upgrade process, after updating the rpms? No, we do not have rpmconf in ovirt. Now, if you have a working engine, that's good. Remember though that you started with clean DB. When DB has entries, the upgrade.sh run may not be as fluent as it was before. But, if it works, I guess you could use the same strategy for upgrading the complete working environment: 1. Backup DB and certificates 2. Upgrade DB in a stand-alone mode and save it aside. 3. Install 3.2, restore the engine DB from upgraded backup. 4. Restore certificates. 5. Start the engine. 6. Enjoy? Let me know what your status is. /Karli ons 2013-06-26 klockan 13:33 + skrev Karli Sjöberg: tis 2013-06-25 klockan 16:02 +0003 skrev Alex Lourie: On Tue, Jun 25, 2013 at 5:03 PM, Karli Sjöberg wrote: > tis 2013-06-25 klockan 15:35 +0200 skrev Gianluca Cecchi: On Tue, > Jun 25, 2013 at 2:58 PM, Karli Sjöberg wrote: > >>> >>> > Yes, I had much better success following that article, and managed > to upgrade fedora to 18, had to tune my kernel parameters a little > for the postgres upgrade to work, but then engine-upgrade fails just > as it did the last time we tried. The log is attached. Hoping to hear > back from you soon with ideas on what to try next. > >>> >>> >>> > >> >> > But now the error seems different from the original one in March > (if I remember correctly the original post). >> > > They are quite the same: > > Then > psql:drop_old_uuid_functions.sql:25: ERROR: cannot drop function > uuid_nil() because extension uuid-ossp requires it > > Now > 2013-06-25 14:52:16::DEBUG::common_utils::473::root:: stderr = > psql:drop_old_uuid_functions.sql:25: ERROR: cannot drop function > uuid_nil() because extension uuid-ossp requires it > >> Could it be somehow related with this rhev one bug: > https://bugzilla.redhat.com/show_bug.cgi?id=923614 >> >> > and that changing permissions for the impacted objects in db before > running upgrade could help? I have now tried that and it did no change in success there unfortunately, so it´s probably not anything permissions related in the database. dbmodify: #!/bin/sh export PGPASSFILE=/root/.pgpass for tbl in `psql -U postgres -wqAt -c "select tablename from pg_tables where schemaname = 'public';"
Re: [Users] all in one error
Hi there First, it is much more useful to ask this kind of questions in users@ovirt.org list. On Fri, Jun 28, 2013 at 11:50 AM, 王翼飞 <419399...@qq.com> wrote: Hello! alex I use Fedora-18-i686-Live-Desktop.iso and ovirt-live-el6.iso install on IBM x3650 m3 failed，so I used ovirt-engine-setup-plugin-allinone-3.2.2-1.1.el6.noarch.rpm package, but it also failed. I think maybe cause by network config error. Can you tell me What can i do? Second, you should provide more details, such as logs of the installation and specific errors you had. thank you! i'm chinese,shy for my English . That's ok. O.O Alex Lourie, Redhat. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-update problem
Hi Juan On Fri, Jun 28, 2013 at 10:00 PM, Juan Pablo Lorier wrote: Hi Sandro, I don't know if it's not better just to start over, because I'm wasting your time and it's not even a production environment. Maybe it's better just to cleanup everything and start over. Other idea I had is to cleanup the database and then import the backup that the upgrade made before rolling back. I don't know if that can lead to an inconsistent database or not. Regards, That could work. Regarding your initial problem - it was fixed in later version, and should be working now. In any case - I would recommend reinstalling with 3.2, as it is indeed a better chance to have less issues. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Fedora upgrading from 3.1 to 3.2
On Tue, Jun 25, 2013 at 7:07 PM, Matthew Curry wrote: Has anyone tried 3.1 to 3.2 in CentOS? or even 3.1 to 3.3rc/beta/etc?? I am going to be forced down that path soon; so I am wondering what kind of hurt I am in for... Lol... Hi Matthew I suspect your mileage will be much smoother due to much smaller changes between CentOS released compared to Fedora :-) Thanks, Matthew Curry On 6/25/13 8:40 AM, Alex Lourie wrote: > Hi Eli > > The following is the error we're getting when upgrading upstream 3.1 > to 3.2: > > 2013-06-25 14:52:11::DEBUG::common_utils::434::root:: Executing > command --> '/usr/share/ovirt-engine/dbscripts/upgrade.sh -s localhost > -p 5432 -u engine -d engine_2013_06_25_14_49_31' > 2013-06-25 14:52:16::DEBUG::common_utils::472::root:: output = > /usr/share/ovirt-engine/dbscripts /usr/share/ovirt-engine/dbscripts > upgrade script detected a change in Config, View or Stored Procedure... > > 2013-06-25 14:52:16::DEBUG::common_utils::473::root:: stderr = > psql:drop_old_uuid_functions.sql:25: ERROR: cannot drop function > uuid_nil() because extension uuid-ossp requires it > HINT: You can drop extension uuid-ossp instead. > CONTEXT: SQL statement "drop function if exists uuid_nil()" > PL/pgSQL function __temp_drop_old_uuid_functions() line 10 at SQL > statement > psql:create_functions.sql:671: ERROR: must be owner of function > uuid_generate_v1 > > > Any idea how can we fix it manually? > > Thanks, > Alex. > > On Tue, Jun 25, 2013 at 3:58 PM, Karli Sjöberg > wrote: >> tis 2013-06-25 klockan 14:59 +0300 skrev Moran Goldboim: On >> 06/25/2013 02:52 PM, Alex Lourie wrote: >>> > >>> > On Tue, Jun 25, 2013 at 1:31 PM, Karli Sjöberg >>> > wrote: >>> >> mån 2013-06-24 klockan 12:35 +0003 skrev Alex Lourie: >>> >>> On Mon, Jun 24, 2013 at 2:09 PM, Karli Sjöberg >>> >>> wrote: >>> >>> > mån 2013-06-24 klockan 10:54 +0003 skrev Alex Lourie: >>> >>> >> On Mon, Jun 24, 2013 at 1:26 PM, Karli Sjöberg >> >>> >>> >> wrote: >>> >>> >> > sön 2013-06-23 klockan 09:38 +0003 skrev Alex Lourie: Hi >>> Karli >>> >>> >> >> >> >> I've written up all we know at [1], please try to >>> follow >>> it (if >> you >> >> haven't yet) and let us know how it >>> goes. If >>> anything goes wrong, >> we >> >> will look for the ways >>> to resolve it. >>> >>> >> >> >> > >> > Hi Alex! >>> >>> >> > >> > Awesome job, I´m going to test this right away and let >>> you >>> know >> how >> > it goes. Wish me luck;) >>> >>> >> > >> >> Good luck! May the force be with you. >>> >>> >> > > No no, the source Alex, the source:) >>> >>> > > /K >>> >>> > >>> >>> Sure, that one too. >>> >>> >>> >>> >>> > >>> > Hi Karli >>> > >>> >> >>> >> Well, it wasn´t with me for long, I have hit BZ 911939 and >>> 901786, >> where fedup fails to find my LVM volumes. In the dracut >>> shell (to >> where it gets dropped), I have good output from blkid >>> and lvm >> pvs|vgs|lvs but no nodes created in /dev/mapper and so >>> the system >> cannot boot and upgrade fails. Do you have any >>> suggestions there that >> might help? In the mean time, I´ll try >>> upgrading using >> >>> http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum instead, >>> see >> if that gives better success. >>> >> >>> > >>> > Sorry to hear that. Different people have experienced multiple > >>> problems upgrading lvm-based F17 systems to F18. I don't think that >>> > there's a magic solution that would just work, each case is >>> usually > solved on its own. >>> > >>> > Let us know how you progress with upgrading with yum. >>> > >>> > Alex. >>> >>> i used same article [1] and had a successful go with it - good luck... >>> >>> [1] >>> https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_17_-.3E_Fedora_18 >>> >>> >>> > >>> >> >>> >> -- >>
Re: [Users] Fedora upgrading from 3.1 to 3.2
On Tue, Jun 25, 2013 at 5:03 PM, Karli Sjöberg wrote: tis 2013-06-25 klockan 15:35 +0200 skrev Gianluca Cecchi: On Tue, Jun 25, 2013 at 2:58 PM, Karli Sjöberg wrote: Yes, I had much better success following that article, and managed to upgrade fedora to 18, had to tune my kernel parameters a little for the postgres upgrade to work, but then engine-upgrade fails just as it did the last time we tried. The log is attached. Hoping to hear back from you soon with ideas on what to try next. But now the error seems different from the original one in March (if I remember correctly the original post). They are quite the same: Then psql:drop_old_uuid_functions.sql:25: ERROR: cannot drop function uuid_nil() because extension uuid-ossp requires it Now 2013-06-25 14:52:16::DEBUG::common_utils::473::root:: stderr = psql:drop_old_uuid_functions.sql:25: ERROR: cannot drop function uuid_nil() because extension uuid-ossp requires it Could it be somehow related with this rhev one bug: https://bugzilla.redhat.com/show_bug.cgi?id=923614 and that changing permissions for the impacted objects in db before running upgrade could help? Very interesting, thanks for the hint! That is definitely worth trying out. Will try that first thing tomorrow:) Hi Karli If it helps, let me know - I will add a troubleshooting section to the wiki. BTW: is your environment directly created in 3.1 or did it come from a further upgrade? Started with a minimal Fedora 17 install, added the oVirt-3.1 repo, ran yum upgrade -y first, then yum install -y ovirt-engine and lastly engine-setup. Nothing more. So it´s just an empty engine that I´m trying to upgrade at this point. When that works, I´ll add hosts, VMs, Templates, etc. HIH, Gianluca -- Med Vänliga Hälsningar --- Karli Sjöberg Swedish University of Agricultural Sciences Box 7079 (Visiting Address Kronåsvägen 8) S-750 07 Uppsala, Sweden Phone: +46-(0)18-67 15 66 karli.sjob...@slu.se ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Fedora upgrading from 3.1 to 3.2
Hi Eli The following is the error we're getting when upgrading upstream 3.1 to 3.2: 2013-06-25 14:52:11::DEBUG::common_utils::434::root:: Executing command --> '/usr/share/ovirt-engine/dbscripts/upgrade.sh -s localhost -p 5432 -u engine -d engine_2013_06_25_14_49_31' 2013-06-25 14:52:16::DEBUG::common_utils::472::root:: output = /usr/share/ovirt-engine/dbscripts /usr/share/ovirt-engine/dbscripts upgrade script detected a change in Config, View or Stored Procedure... 2013-06-25 14:52:16::DEBUG::common_utils::473::root:: stderr = psql:drop_old_uuid_functions.sql:25: ERROR: cannot drop function uuid_nil() because extension uuid-ossp requires it HINT: You can drop extension uuid-ossp instead. CONTEXT: SQL statement "drop function if exists uuid_nil()" PL/pgSQL function __temp_drop_old_uuid_functions() line 10 at SQL statement psql:create_functions.sql:671: ERROR: must be owner of function uuid_generate_v1 Any idea how can we fix it manually? Thanks, Alex. On Tue, Jun 25, 2013 at 3:58 PM, Karli Sjöberg wrote: tis 2013-06-25 klockan 14:59 +0300 skrev Moran Goldboim: On 06/25/2013 02:52 PM, Alex Lourie wrote: > > On Tue, Jun 25, 2013 at 1:31 PM, Karli Sjöberg > wrote: >> mån 2013-06-24 klockan 12:35 +0003 skrev Alex Lourie: >>> On Mon, Jun 24, 2013 at 2:09 PM, Karli Sjöberg >>> wrote: >>> > mån 2013-06-24 klockan 10:54 +0003 skrev Alex Lourie: >>> >> On Mon, Jun 24, 2013 at 1:26 PM, Karli Sjöberg >> >>> >> wrote: >>> >> > sön 2013-06-23 klockan 09:38 +0003 skrev Alex Lourie: Hi Karli >>> >> >> >> >> I've written up all we know at [1], please try to follow >>> it (if >> you >> >> haven't yet) and let us know how it goes. If >>> anything goes wrong, >> we >> >> will look for the ways to resolve it. >>> >> >> >> > >> > Hi Alex! >>> >> > >> > Awesome job, I´m going to test this right away and let you >>> know >> how >> > it goes. Wish me luck;) >>> >> > >> >> Good luck! May the force be with you. >>> >> > > No no, the source Alex, the source:) >>> > > /K >>> > >>> Sure, that one too. >>> >>> > > Hi Karli > >> >> Well, it wasn´t with me for long, I have hit BZ 911939 and 901786, >> where fedup fails to find my LVM volumes. In the dracut shell (to >> where it gets dropped), I have good output from blkid and lvm >> pvs|vgs|lvs but no nodes created in /dev/mapper and so the system >> cannot boot and upgrade fails. Do you have any suggestions there that >> might help? In the mean time, I´ll try upgrading using >> http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum instead, see >> if that gives better success. >> > > Sorry to hear that. Different people have experienced multiple > problems upgrading lvm-based F17 systems to F18. I don't think that > there's a magic solution that would just work, each case is usually > solved on its own. > > Let us know how you progress with upgrading with yum. > > Alex. i used same article [1] and had a successful go with it - good luck... [1] https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_17_-.3E_Fedora_18 > >> >> -- >> >> Med Vänliga Hälsningar >> --- >> >> Karli Sjöberg >> Swedish University of Agricultural Sciences >> Box 7079 (Visiting Address Kronåsvägen 8) >> S-750 07 Uppsala, Sweden >> Phone: +46-(0)18-67 15 66 >> karli.sjob...@slu.se > Yes, I had much better success following that article, and managed to upgrade fedora to 18, had to tune my kernel parameters a little for the postgres upgrade to work, but then engine-upgrade fails just as it did the last time we tried. The log is attached. Hoping to hear back from you soon with ideas on what to try next. -- Med Vänliga Hälsningar --- Karli Sjöberg Swedish University of Agricultural Sciences Box 7079 (Visiting Address Kronåsvägen 8) S-750 07 Uppsala, Sweden Phone: +46-(0)18-67 15 66 karli.sjob...@slu.se ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Fedora upgrading from 3.1 to 3.2
On Tue, Jun 25, 2013 at 1:31 PM, Karli Sjöberg wrote: mån 2013-06-24 klockan 12:35 +0003 skrev Alex Lourie: On Mon, Jun 24, 2013 at 2:09 PM, Karli Sjöberg wrote: > mån 2013-06-24 klockan 10:54 +0003 skrev Alex Lourie: >> On Mon, Jun 24, 2013 at 1:26 PM, Karli Sjöberg >> >> wrote: >> > sön 2013-06-23 klockan 09:38 +0003 skrev Alex Lourie: Hi Karli >> >> >> >> I've written up all we know at [1], please try to follow it (if >> you >> >> haven't yet) and let us know how it goes. If anything goes wrong, >> we >> >> will look for the ways to resolve it. >> >> >> > >> > Hi Alex! >> > >> > Awesome job, I´m going to test this right away and let you know >> how >> > it goes. Wish me luck;) >> > >> >> Good luck! May the force be with you. >> > > No no, the source Alex, the source:) > > /K > Sure, that one too. Hi Karli Well, it wasn´t with me for long, I have hit BZ 911939 and 901786, where fedup fails to find my LVM volumes. In the dracut shell (to where it gets dropped), I have good output from blkid and lvm pvs|vgs|lvs but no nodes created in /dev/mapper and so the system cannot boot and upgrade fails. Do you have any suggestions there that might help? In the mean time, I´ll try upgrading using http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum instead, see if that gives better success. Sorry to hear that. Different people have experienced multiple problems upgrading lvm-based F17 systems to F18. I don't think that there's a magic solution that would just work, each case is usually solved on its own. Let us know how you progress with upgrading with yum. Alex. -- Med Vänliga Hälsningar --- Karli Sjöberg Swedish University of Agricultural Sciences Box 7079 (Visiting Address Kronåsvägen 8) S-750 07 Uppsala, Sweden Phone: +46-(0)18-67 15 66 karli.sjob...@slu.se ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Fedora upgrading from 3.1 to 3.2
On Mon, Jun 24, 2013 at 2:09 PM, Karli Sjöberg wrote: mån 2013-06-24 klockan 10:54 +0003 skrev Alex Lourie: On Mon, Jun 24, 2013 at 1:26 PM, Karli Sjöberg wrote: > sön 2013-06-23 klockan 09:38 +0003 skrev Alex Lourie: Hi Karli >> >> I've written up all we know at [1], please try to follow it (if you >> haven't yet) and let us know how it goes. If anything goes wrong, we >> will look for the ways to resolve it. >> > > Hi Alex! > > Awesome job, I´m going to test this right away and let you know how > it goes. Wish me luck;) > Good luck! May the force be with you. No no, the source Alex, the source:) /K Sure, that one too. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Fedora upgrading from 3.1 to 3.2
On Mon, Jun 24, 2013 at 1:26 PM, Karli Sjöberg wrote: sön 2013-06-23 klockan 09:38 +0003 skrev Alex Lourie: Hi Karli I've written up all we know at [1], please try to follow it (if you haven't yet) and let us know how it goes. If anything goes wrong, we will look for the ways to resolve it. Hi Alex! Awesome job, I´m going to test this right away and let you know how it goes. Wish me luck;) Good luck! May the force be with you. Alex. /Karli Alex. [1] http://www.ovirt.org/OVirt_3.1_to_3.2_upgrade On Thu, Jun 20, 2013 at 8:05 PM, Alex Lourie wrote: > Hi Karli > > I am reviewing all the actions again, and hopefully will have > something > documented on Sunday. > > Alex. > > On Tue, Jun 18, 2013 at 10:46 AM, Karli Sjöberg > > wrote: > > tis 2013-06-18 klockan 10:06 +0300 skrev Moran Goldboim: On > > 06/17/2013 02:51 PM, Karli Sjöberg wrote: > >> > >> > > mån 2013-06-17 klockan 10:11 +0003 skrev Alex Lourie: On Fri, > > Jun 14, 2013 at 12:26 PM, Karli Sjöberg > >>>> wrote: > >>>> > Hi! > >>>> > > >>>> > >>>> Hi Karli, > >>>> > >>>> > > >>>> > More than two months have passed without any notices or > updates > >>>> on > >>>> > this issue, and looking at the bugreport absolutely nothing > has > >>>> been > >>>> > done since then. What´s confusing me is that the release > >>>> management > >>>> > for oVirt 3.2 has this clearly printed: > >>>> > "MUST: Upgrade from previous release" > >>>> > > >>>> > And you all seem too busy with getting the next release out of > >>>> the > >>>> > door before fixing the current... What gives? Don´t you care > >>>> about > >>>> > early adopters? > >>>> > > >>>> > >>>> I apologise that this issue wasn't taken care of yet. It is > clear > >>>> that > >>>> the priorities of developers shifted towards work on features in > >>>> 3.3 > >>>> release, which feature freeze is happening in about 2 weeks, so > >>>> you can > >>>> understand the time pressure they all have. There's no need to > be > >>>> angry > >>>> about that. It is an open source project and as resources for > the > >>>> development are limited, we're trying to do our best to cover as > >>>> much > >>>> issues as possible. This can lead to situations as this issue, > >>>> which > >>>> may be left behind for some time. > >>>> > >>> > >>> I´m not angry, as I stated before, I´m more confused, and maybe > a > >>> little disappointed that important(in my opinion) pieces of a > >>> projects continuum have been ignored like that. I´m having a > hard > >>> time understanding the reasoning behind the priorities that have > >>> made this issue appear. In my mind, making sure that users of any > >>> project are able to follow between minor upgrades is a given, > with > >>> a schedule like; 1) Feature freeze, 2) Fix release blockers > >>> (upgrading being one of them), 3) Release, in that order. Now > >>> what´s happening is that you are kind of hoping to drag this out > >>> until the problem goes away by itself when you decide it´s time > to > >>> stop supporting 3.1. > >>> > >>>> That said, the process for upgrading the oVirt 3.1 on Fedora 17 > to > >>>> oVirt 3.2 on Fedora 18 is complex and non-trivial, that's why it > >>>> is > >>>> taking time to resolve all the issues that come up in the > process. > >>>> > >>>> If this matter is not extremely urgent, we are currently working > >>>> on a > >>>> tool that may make this upgrade easier, albeit, maybe, not > >>>> completely > >>>> automatic. > >>>> > >>>> On the other hand, if this is a completely and utterly urgent, > we > >>>> may > >>>> try to guide you through possible manual attempts to perform the > >>>> upgrade. Mind though, that they weren't thoroughly tested, and > not > >>>> promised to go
Re: [Users] Fedora upgrading from 3.1 to 3.2
Hi Alfred On Sun, Jun 23, 2013 at 10:08 PM, Alfred Angelov wrote: Hey, This might sounds like a foolish question, but from the link you mentioned: oVirt 3.1 was released as Fedora 17 package while 3.2 is targeted Fedora 18. Due to the nature of this upgrade, we DO NOT recommend it, users are advised to do a 3.2 clean installation, and to import all VM's and template into the new installation. Is there anything special I would have to do to import all the VMs (around 40) from my ovirt 3.1.0-2 to another ovirt (which runs 3.2.2) ? No, just usual import should work. Mvh, Alfred Angelov On 06/23/2013 11:35 AM, Alex Lourie wrote: Hi Karli I've written up all we know at [1], please try to follow it (if you haven't yet) and let us know how it goes. If anything goes wrong, we will look for the ways to resolve it. Alex. [1] http://www.ovirt.org/OVirt_3.1_to_3.2_upgrade On Thu, Jun 20, 2013 at 8:05 PM, Alex Lourie wrote: Hi Karli I am reviewing all the actions again, and hopefully will have something documented on Sunday. Alex. On Tue, Jun 18, 2013 at 10:46 AM, Karli Sjöberg wrote: > tis 2013-06-18 klockan 10:06 +0300 skrev Moran Goldboim: On > 06/17/2013 02:51 PM, Karli Sjöberg wrote: >> >> > mån 2013-06-17 klockan 10:11 +0003 skrev Alex Lourie: On Fri, > Jun 14, 2013 at 12:26 PM, Karli Sjöberg >>>> wrote: >>>> > Hi! >>>> > >>>> >>>> Hi Karli, >>>> >>>> > >>>> > More than two months have passed without any notices or updates >>>> on >>>> > this issue, and looking at the bugreport absolutely nothing has >>>> been >>>> > done since then. What´s confusing me is that the release >>>> management >>>> > for oVirt 3.2 has this clearly printed: >>>> > "MUST: Upgrade from previous release" >>>> > >>>> > And you all seem too busy with getting the next release out of >>>> the >>>> > door before fixing the current... What gives? Don´t you care >>>> about >>>> > early adopters? >>>> > >>>> >>>> I apologise that this issue wasn't taken care of yet. It is clear >>>> that >>>> the priorities of developers shifted towards work on features in >>>> 3.3 >>>> release, which feature freeze is happening in about 2 weeks, so >>>> you can >>>> understand the time pressure they all have. There's no need to be >>>> angry >>>> about that. It is an open source project and as resources for the >>>> development are limited, we're trying to do our best to cover as >>>> much >>>> issues as possible. This can lead to situations as this issue, >>>> which >>>> may be left behind for some time. >>>> >>> >>> I´m not angry, as I stated before, I´m more confused, and maybe a >>> little disappointed that important(in my opinion) pieces of a >>> projects continuum have been ignored like that. I´m having a hard >>> time understanding the reasoning behind the priorities that have >>> made this issue appear. In my mind, making sure that users of any >>> project are able to follow between minor upgrades is a given, with >>> a schedule like; 1) Feature freeze, 2) Fix release blockers >>> (upgrading being one of them), 3) Release, in that order. Now >>> what´s happening is that you are kind of hoping to drag this out >>> until the problem goes away by itself when you decide it´s time to >>> stop supporting 3.1. >>> >>>> That said, the process for upgrading the oVirt 3.1 on Fedora 17 to >>>> oVirt 3.2 on Fedora 18 is complex and non-trivial, that's why it >>>> is >>>> taking time to resolve all the issues that come up in the process. >>>> >>>> If this matter is not extremely urgent, we are currently working >>>> on a >>>> tool that may make this upgrade easier, albeit, maybe, not >>>> completely >>>> automatic. >>>> >>>> On the other hand, if this is a completely and utterly urgent, we >>>> may >>>> try to guide you through possible manual attempts to perform the >>>> upgrade. Mind though, that they weren't thoroughly tested, and not >>>> promised to go smoothly or even work, and we may have to think >>>> about >>>> possible alternative solutions on the go. >>>> >&g
Re: [Users] Fedora upgrading from 3.1 to 3.2
Hi Karli I've written up all we know at [1], please try to follow it (if you haven't yet) and let us know how it goes. If anything goes wrong, we will look for the ways to resolve it. Alex. [1] http://www.ovirt.org/OVirt_3.1_to_3.2_upgrade On Thu, Jun 20, 2013 at 8:05 PM, Alex Lourie wrote: Hi Karli I am reviewing all the actions again, and hopefully will have something documented on Sunday. Alex. On Tue, Jun 18, 2013 at 10:46 AM, Karli Sjöberg wrote: > tis 2013-06-18 klockan 10:06 +0300 skrev Moran Goldboim: On > 06/17/2013 02:51 PM, Karli Sjöberg wrote: >> >> > mån 2013-06-17 klockan 10:11 +0003 skrev Alex Lourie: On Fri, > Jun 14, 2013 at 12:26 PM, Karli Sjöberg >>>> wrote: >>>> > Hi! >>>> > >>>> >>>> Hi Karli, >>>> >>>> > >>>> > More than two months have passed without any notices or updates >>>> on >>>> > this issue, and looking at the bugreport absolutely nothing has >>>> been >>>> > done since then. What´s confusing me is that the release >>>> management >>>> > for oVirt 3.2 has this clearly printed: >>>> > "MUST: Upgrade from previous release" >>>> > >>>> > And you all seem too busy with getting the next release out of >>>> the >>>> > door before fixing the current... What gives? Don´t you care >>>> about >>>> > early adopters? >>>> > >>>> >>>> I apologise that this issue wasn't taken care of yet. It is clear >>>> that >>>> the priorities of developers shifted towards work on features in >>>> 3.3 >>>> release, which feature freeze is happening in about 2 weeks, so >>>> you can >>>> understand the time pressure they all have. There's no need to be >>>> angry >>>> about that. It is an open source project and as resources for the >>>> development are limited, we're trying to do our best to cover as >>>> much >>>> issues as possible. This can lead to situations as this issue, >>>> which >>>> may be left behind for some time. >>>> >>> >>> I´m not angry, as I stated before, I´m more confused, and maybe a >>> little disappointed that important(in my opinion) pieces of a >>> projects continuum have been ignored like that. I´m having a hard >>> time understanding the reasoning behind the priorities that have >>> made this issue appear. In my mind, making sure that users of any >>> project are able to follow between minor upgrades is a given, with >>> a schedule like; 1) Feature freeze, 2) Fix release blockers >>> (upgrading being one of them), 3) Release, in that order. Now >>> what´s happening is that you are kind of hoping to drag this out >>> until the problem goes away by itself when you decide it´s time to >>> stop supporting 3.1. >>> >>>> That said, the process for upgrading the oVirt 3.1 on Fedora 17 to >>>> oVirt 3.2 on Fedora 18 is complex and non-trivial, that's why it >>>> is >>>> taking time to resolve all the issues that come up in the process. >>>> >>>> If this matter is not extremely urgent, we are currently working >>>> on a >>>> tool that may make this upgrade easier, albeit, maybe, not >>>> completely >>>> automatic. >>>> >>>> On the other hand, if this is a completely and utterly urgent, we >>>> may >>>> try to guide you through possible manual attempts to perform the >>>> upgrade. Mind though, that they weren't thoroughly tested, and not >>>> promised to go smoothly or even work, and we may have to think >>>> about >>>> possible alternative solutions on the go. >>>> >>> >>> Straight answer: Am I ever going to be able to upgrade from 3.1 to >>> 3.2? >>> >>> My concern (fear) is about being left behind, abandoned. It makes >>> me feel non-important. Just like any admin, the work put down to >>> make Templates, to set up quotas, create VMPools, a dozen of >>> guests. And then have to export everything (nullifying the idea of >>> "Thin Provisioning"), redo every Role, reset every permission, >>> quota, and so on, isn´t (in my opinion) viable in the long run for >>> oVirt as a
Re: [Users] Fedora upgrading from 3.1 to 3.2
Hi Karli I am reviewing all the actions again, and hopefully will have something documented on Sunday. Alex. On Tue, Jun 18, 2013 at 10:46 AM, Karli Sjöberg wrote: tis 2013-06-18 klockan 10:06 +0300 skrev Moran Goldboim: On 06/17/2013 02:51 PM, Karli Sjöberg wrote: mån 2013-06-17 klockan 10:11 +0003 skrev Alex Lourie: On Fri, Jun 14, 2013 at 12:26 PM, Karli Sjöberg wrote: > Hi! > Hi Karli, > > More than two months have passed without any notices or updates on > this issue, and looking at the bugreport absolutely nothing has been > done since then. What´s confusing me is that the release management > for oVirt 3.2 has this clearly printed: > "MUST: Upgrade from previous release" > > And you all seem too busy with getting the next release out of the > door before fixing the current... What gives? Don´t you care about > early adopters? > I apologise that this issue wasn't taken care of yet. It is clear that the priorities of developers shifted towards work on features in 3.3 release, which feature freeze is happening in about 2 weeks, so you can understand the time pressure they all have. There's no need to be angry about that. It is an open source project and as resources for the development are limited, we're trying to do our best to cover as much issues as possible. This can lead to situations as this issue, which may be left behind for some time. I´m not angry, as I stated before, I´m more confused, and maybe a little disappointed that important(in my opinion) pieces of a projects continuum have been ignored like that. I´m having a hard time understanding the reasoning behind the priorities that have made this issue appear. In my mind, making sure that users of any project are able to follow between minor upgrades is a given, with a schedule like; 1) Feature freeze, 2) Fix release blockers (upgrading being one of them), 3) Release, in that order. Now what´s happening is that you are kind of hoping to drag this out until the problem goes away by itself when you decide it´s time to stop supporting 3.1. That said, the process for upgrading the oVirt 3.1 on Fedora 17 to oVirt 3.2 on Fedora 18 is complex and non-trivial, that's why it is taking time to resolve all the issues that come up in the process. If this matter is not extremely urgent, we are currently working on a tool that may make this upgrade easier, albeit, maybe, not completely automatic. On the other hand, if this is a completely and utterly urgent, we may try to guide you through possible manual attempts to perform the upgrade. Mind though, that they weren't thoroughly tested, and not promised to go smoothly or even work, and we may have to think about possible alternative solutions on the go. Straight answer: Am I ever going to be able to upgrade from 3.1 to 3.2? My concern (fear) is about being left behind, abandoned. It makes me feel non-important. Just like any admin, the work put down to make Templates, to set up quotas, create VMPools, a dozen of guests. And then have to export everything (nullifying the idea of "Thin Provisioning"), redo every Role, reset every permission, quota, and so on, isn´t (in my opinion) viable in the long run for oVirt as a project to demand. That´s why I had the notion that upgrading surely had to be a high priority. Was I wrong about that? upgrade actually was high priority task, but due to lots of platform (fedora 18) changes, it became a huge operation to support it (which comes on top new features/bugs/support etc.). in addition we have noticed that the interest from the community regarding it, is very limited. from where i see i we have couple of options: -if there is enough interest from the community we can give it another go (though i think most of it moved long ago to oVirt 3.2) You certainly have my interest at least;) -we can help individuals by making a migration (3.1->3.2) document on fedora base systems- we'll probably need your assistance on testing side here A document explaining how to upgrade would be completly acceptable for me. I´m not asking for a turnkey command that makes everything for me, I´ve managed to get quite far by myself any way. I would love to help testing the procedure, as I´ve stated before, we have set up a dedicated test environment dedicated for this specific upgrade task in mind, with engine, hosts and storage somewhat equal to the production system. Please, if there´s anything I can do to help, don´t hesitate to ask! Best regards, Alex Lourie, Software Developer in Integration, RHEV, Red Hat. > > Best Regards > Karli Sjöberg > > fre 2013-04-05 klockan 10:24 +0200 skrev Sandro Bonazzola: Hi Karli, >> we're still working on it >> >> >> Il 02/04/2013 12:22, Karli Sjöberg ha scritto: >> >
Re: [Users] Fedora upgrading from 3.1 to 3.2
On Fri, Jun 14, 2013 at 12:26 PM, Karli Sjöberg wrote: Hi! Hi Karli, More than two months have passed without any notices or updates on this issue, and looking at the bugreport absolutely nothing has been done since then. What´s confusing me is that the release management for oVirt 3.2 has this clearly printed: "MUST: Upgrade from previous release" And you all seem too busy with getting the next release out of the door before fixing the current... What gives? Don´t you care about early adopters? I apologise that this issue wasn't taken care of yet. It is clear that the priorities of developers shifted towards work on features in 3.3 release, which feature freeze is happening in about 2 weeks, so you can understand the time pressure they all have. There's no need to be angry about that. It is an open source project and as resources for the development are limited, we're trying to do our best to cover as much issues as possible. This can lead to situations as this issue, which may be left behind for some time. That said, the process for upgrading the oVirt 3.1 on Fedora 17 to oVirt 3.2 on Fedora 18 is complex and non-trivial, that's why it is taking time to resolve all the issues that come up in the process. If this matter is not extremely urgent, we are currently working on a tool that may make this upgrade easier, albeit, maybe, not completely automatic. On the other hand, if this is a completely and utterly urgent, we may try to guide you through possible manual attempts to perform the upgrade. Mind though, that they weren't thoroughly tested, and not promised to go smoothly or even work, and we may have to think about possible alternative solutions on the go. Best regards, Alex Lourie, Software Developer in Integration, RHEV, Red Hat. Best Regards Karli Sjöberg fre 2013-04-05 klockan 10:24 +0200 skrev Sandro Bonazzola: Hi Karli, we're still working on it Il 02/04/2013 12:22, Karli Sjöberg ha scritto: Hi, has there been any progress regarding this matter? Best Regards Karli Sjöberg fre 2013-03-15 klockan 14:12 + skrev Karli Sjöberg: fre 2013-03-15 klockan 14:59 +0100 skrev Sandro Bonazzola: Il 13/03/2013 12:24, Karli Sjöberg ha scritto: ons 2013-03-13 klockan 12:00 +0100 skrev Dave Neary: Hi Karli, On 03/11/2013 12:16 PM, Karli Sjöberg wrote: > Hi, > > in the absence of any official path, we have started working out our own > procedure for going from oVirt-3.1/Fedora 17 to oVirt-3.2/Fedora 18. Indeed, I have not seen any documentation in the wiki yet on upgrading oVirt - would you be interested in writing up your experiences there as a guide to others? Thanks! Dave. That was my intention to share a working procedure once it was complete but I unfortunately hit a wall at "engine-upgrade". I would be very glad, and able to continue, if that obstacle could be lifted. My experience in upgrading from oVirt-3.1/Fedora 17 to oVirt-3.2/Fedora 18: On Fedora 17: Be sure to have the latest updates running: yum distro-sync Set exclude=ovirt* in /etc/yum.conf Execute: fedup --disablerepo=ovirt* --network 18 When you have a running Fedora 18: # systemctl list-units --failed UNIT LOAD ACTIVE SUBDESCRIPTION httpd.service loaded failed failed The Apache HTTP Server postgresql.service loaded failed failed PostgreSQL database server # systemctl stop postgresql.service # tar cJvf pgsql-backup.tar.xz /var/lib/pgsql/data/ # yum install postgresql-upgrade # cp /var/lib/pgsql/data/pg_hba.conf /root/pg_hba.conf.ovirt edit /var/lib/pgsql/data/pg_hba.conf changing md5 to trust on the local line. # diff -u pg_hba.conf.ovirt pg_hba.conf --- pg_hba.conf.ovirt 2013-01-30 20:58:49.40400 +0100 +++ pg_hba.conf 2013-01-30 20:59:06.70900 +0100 @@ -77,7 +77,7 @@ # TYPE DATABASEUSERADDRESS METHOD # "local" is for Unix domain socket connections only -local all all md5 +local all all trust # IPv4 local connections: hostall all 127.0.0.1/32 md5 # IPv6 local connections: # postgresql-setup upgrade Redirecting to /bin/systemctl stop postgresql.service Upgrading database: OK See /var/lib/pgsql/pgupgrade.log for details. # cp /root/pg_hba.conf.ovirt /var/lib/pgsql/data/pg_hba.conf # systemctl postgrsql.service restart edit /etc/httpd/conf.d/ssl.conf: # diff -u ssl.conf.ovirt ssl.conf --- ssl.conf.ovirt 2013-01-30 21:21:06.90600 +0100 +++ ssl.conf2013-01-30 21:22:02.75700 +0100 @@ -9,7 +9,7 @@ # consult the online docs. You have been warned. # -LoadModule ssl_module modules/mod_ssl.so +#LoadModule ssl_module modules/mod_ssl.so # # When we also provide SSL we have to listen to the @@ -40,7 +40,7 @@ # Semaphore
Re: [Users] installation errors
On Fri, Apr 26, 2013 at 5:43 PM, Lance Oreste wrote: I got ovirt all in one working on one server, when I tried to install another host, I get some strange erros. Here is a copy of my log, I am not sure why the installation stopped Hi Lance There seems to be a problem starting the dwhd service after installation. Could you please attach dwhd service log as well, so we can have a better picture? Thank you. Alex. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] installation errors
On Sat, Apr 27, 2013 at 8:14 AM, Itamar Heim wrote: On 04/26/2013 05:43 PM, Lance Oreste wrote: I got ovirt all in one working on one server, when I tried to install another host, I get some strange erros. Here is a copy of my log, I am not sure why the installation stopped ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users sandro/alex/moran - how is the dwh service related to all-in-one? There's no connection between dwh and AIO. Alex. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt 3.2.1 and reports update error
Yaniv, Could you please take a look? Did you see this before? On Wed, Mar 20, 2013 at 2:48 PM, supo...@logicworks.pt wrote: Any news about this? De: supo...@logicworks.pt Para: "Alex Lourie" Cc: "users" Enviadas: Terça-feira, 19 de Março de 2013 16:04:51 Assunto: Re: [Users] oVirt 3.2.1 and reports update error still the same like this: https://docs.google.com/file/d/0BwoPbcrMv8mvQ3piS2xCRnRZdzg/edit?usp=sharing De: "Alex Lourie" Para: supo...@logicworks.pt Cc: "users" , "Gianluca Cecchi" Enviadas: Terça-feira, 19 de Março de 2013 15:28:22 Assunto: Re: [Users] oVirt 3.2.1 and reports update error On Tue, Mar 19, 2013 at 5:08 PM, supo...@logicworks.pt wrote: > Alex, dwhd is up and running (ovirt-engine-dwh) > OK, so let's see how the reports site is doing now. > > De: "Alex Lourie" > Para: supo...@logicworks.pt > Cc: "users" , "Gianluca Cecchi" > > Enviadas: Terça-feira, 19 de Março de 2013 13:16:49 > Assunto: Re: [Users] oVirt 3.2.1 and reports update error > > ___ 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: [Users] Problem install
Hi Marcelo We need to dig deeper. Can you please attach server and engine logs? Thanks. On Tue, Mar 19, 2013 at 4:52 PM, Marcelo Barbosa wrote: Alex, I run again, but error persist: ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt 3.2.1 and reports update error
On Tue, Mar 19, 2013 at 5:08 PM, supo...@logicworks.pt wrote: Alex, dwhd is up and running (ovirt-engine-dwh) OK, so let's see how the reports site is doing now. De: "Alex Lourie" Para: supo...@logicworks.pt Cc: "users" , "Gianluca Cecchi" Enviadas: Terça-feira, 19 de Março de 2013 13:16:49 Assunto: Re: [Users] oVirt 3.2.1 and reports update error ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Problem install
M, Marcelo Barbosa
wrote:
Alex,
i am check:
# rpm -qa | grep sanlock
sanlock-2.6-7.fc18.x86_64
libvirt-lock-sanlock-0.10.2.3-1.fc18.x86_64
sanlock-lib-2.6-7.fc18.x86_64
sanlock-python-2.6-7.fc18.x86_64
you would like make reinstall ? I can try again...
Marcelo Barbosa
mr.marcelo.barb...@gmail.com
On Tue, Mar 19, 2013 at 10:30 AM, Alex Lourie
wrote:
Hi Marcelo
Can you please check that you have sanlock-2.6-7 installed?
Thanks.
On Wed, Mar 6, 2013 at 10:51 PM, Marcelo Barbosa
wrote:
Alex,
Thankyou for attention. This return should not happen,
because I have my hostname registered and running on my DNS
servers, but i'm inserted in /etc/hosts my hostname and retry
setup, but return new error:
2013-03-06 17:35:14::DEBUG::all_in_one_100::297::root:: Waiting
for host to become operational
2013-03-06 17:35:14::DEBUG::all_in_one_100::300::root:: current
host status is: up
2013-03-06 17:35:14::DEBUG::all_in_one_100::302::root:: The host
is up.
2013-03-06 17:35:14::DEBUG::setup_sequences::59::root:: running
addStorageDomain
2013-03-06 17:35:14::DEBUG::all_in_one_100::317::root:: Adding
local storage domain
2013-03-06 17:35:14::INFO::all_in_one_100::322::root:: Creating
local storage
2013-03-06 17:35:14::INFO::all_in_one_100::326::root:: Creating
local storage domain
2013-03-06 17:35:14::INFO::all_in_one_100::334::root:: Adding
local storage domain
2013-03-06 17:35:15::ERROR::all_in_one_100::337::root:: Traceback
(most recent call last):
File
"/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line
335, in addStorageDomain
controller.CONF["API_OBJECT"].storagedomains.add(sdParams)
File
"/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py",
line 5151, in add
headers={"Expect":expect, "Correlation-Id":correlation_id})
File
"/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",
line 118, in add
return self.request('POST', url, body, headers)
File
"/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",
line 129, in request
last=last)
File
"/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",
line 159, in __doRequest
raise RequestError, response
RequestError:
status: 400
reason: Bad Request
detail: Cannot add Storage. Internal error, Storage Connection
doesn't exist.
2013-03-06 17:35:15::DEBUG::setup_sequences::62::root:: Traceback
(most recent call last):
File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line
60, in run
function()
File
"/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line
338, in addStorageDomain
raise Exception(ERROR_ADD_LOCAL_DOMAIN)
Exception: Error: could not add local storage domain
2013-03-06 17:35:15::DEBUG::engine-setup::1948::root:: *** The
following params were used as user input:
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
override-httpd-config: yes
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: http-port:
80
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: https-port:
443
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
random-passwords: no
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: mac-range:
00:1A:4A:10:FF:00-00:1A:4A:10:FF:FF
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: host-fqdn:
firelap.usc.unirede.net
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: auth-pass:
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: org-name:
firelap
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
application-mode: both
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
default-dc-type: NFS
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
db-remote-install: local
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: db-host:
localhost
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
db-local-pass:
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: nfs-mp:
/firebackup//iso
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
iso-domain-name: ISO_DOMAIN
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: config-nfs:
yes
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
override-firewall: IPTables
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
config-allinone: yes
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
storage-path: /firebackup//vms
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
superuser-pass:
2013-03-06 17:35:15::ERROR::engine-setup::2369::root:: Traceback
(most recent call last):
File "/bin/engine-setup", line 2363, in
main(confFile)
File "/bin/engine-setup", line 2146, in main
runSequences()
File "/bin/engine-setup", line 2068, in runSequences
controller.runAllSequences()
File "/usr/share/ovirt-engine/scripts/setup_controller.py",
line 54, i
Re: [Users] oVirt 3.2.1 and reports update error
Gianluca
On Tue, Mar 19, 2013 at 3:29 PM, Gianluca Cecchi
wrote:
On Tue, Mar 19, 2013 at 2:16 PM, Alex Lourie
wrote:
> > * Perform the following steps to upgrade the history service
or the
> > reporting package:
> > 1. Execute: yum update ovirt-engine-reports*
> > 2. Execute: ovirt-engine-dwh-setup
> > 3. Execute: ovirt-engine-reports-setup
> > * DB Backup available at
> > >
> > >
/var/lib/ovirt-engine/backups/ovirt-engine_db_backup_2013_03_15_23_16_03.sql
> > > > [root@tekkaman ~]# yum update ovirt-engine-reports*
> > Loaded plugins: fastestmirror, langpacks, presto, >
> > refresh-packagekit,
> > versionlock
> > Loading mirror speeds from cached hostfile
> > * fedora: fedora.mirror.garr.it
> > * livna: ftp-stud.fht-esslingen.de
> > * rpmfusion-free: ftp.nluug.nl
> > * rpmfusion-free-updates: ftp.nluug.nl
> > * rpmfusion-nonfree: ftp.nluug.nl
> > * rpmfusion-nonfree-updates: ftp.nluug.nl
In my case, I have a cluster with two f18 nodes with 3.2 and an f18
engine with 3.2.
I updated engine to 3.2.1.
I got the same error and:
1) yum update ovirt-engine-reports*
gives nothing to update
I presume I still have to run 2) and 3) or not if 1) doesn't catch
anything?
In anu case:
2) ovirt-engine-dwh-setup
# ovirt-engine-dwh-setup
Setting DB connectivity...[DONE]
Upgrade DB... [DONE ]
Starting ovirt-engine... [DONE ]
Starting oVirt-ETL... [DONE]
Successfully installed ovirt-engine-dwh.
The installation log file is available at:
/var/log/ovirt-engine/ovirt-engine-dwh-setup-2013_03_19_09_32_22.log
3)
# ovirt-engine-reports-setup
Welcome to ovirt-engine-reports setup utility
Exporting current users...[DONE]
Updating Redirect Servlet... [DONE]
Importing reports... [DONE]
Importing current users...[DONE]
Customizing Server... [DONE]
Running post setup steps... [DONE]
Starting ovirt-engine... [DONE]
Succesfully installed ovirt-engine-reports.
The installation log file is available at:
/var/log/ovirt-engine/ovirt-engine-reports-setup-2013_03_19_09_32_57.log
Then update my other f18 packages (comprising the ovirt ones for
possible new nodes deploy..)
4) yum update
5) reboot
(at 12:16)
At first ovirt-engine-dwhd didn't start correctly and then at 12:47 I
started it manually and seems to be ok now.
See messages:
Mar 19 12:16:49 f18engine systemd[1]: Started PostgreSQL database
server.
Mar 19 12:16:49 f18engine systemd[1]: Starting oVirt Engine...
Mar 19 12:16:50 f18engine systemd[1]: Started The Apache HTTP Server.
Mar 19 12:16:50 f18engine libvirtd[901]: 2013-03-19 11:16:50.984+:
1046: error : virNWFilterSnoopLeaseFileRefresh:1903 : o
pen("/var/run/libvirt/network/nwfilter.ltmp"): No such file or
directory
Mar 19 12:16:52 f18engine chronyd[641]: Selected source 131.175.12.3
Mar 19 12:16:55 f18engine ovirt-engine-dwhd[892]: Starting
ovirt-engine-dwhd: at Tue Mar 19 12:16:43 CET
2013[ OK ]
Mar 19 12:16:55 f18engine systemd[1]: Started LSB: oVirt Engine
History ETL Service for Data Warehouse and Reporting.
Mar 19 12:16:56 f18engine kernel: [ 28.759401] Ebtables v2.0
registered
Mar 19 12:16:56 f18engine kernel: [ 29.161347] ip6_tables: (C)
2000-2006 Netfilter Core Team
Mar 19 12:16:57 f18engine engine-service[1050]: Started engine
process 1091.
Mar 19 12:16:57 f18engine engine-service[1050]: Starting
engine-service: [ OK ]
Mar 19 12:16:57 f18engine kernel: [ 30.004260] cgroup: libvirtd
(1046) created nested cgroup for controller "memory" which has
incomplete hierarchy support. Nested cgroups may change behavior in
the future.
Mar 19 12:16:57 f18engine kernel: [ 30.004263] cgroup: "memory"
requires setting use_hierarchy to 1 on the root.
Mar 19 12:16:57 f18engine kernel: [ 30.004306] cgroup: libvirtd
(1046) created nested cgroup for controller "devices" which has
incomplete hierarchy support. Nested cgroups may change behavior in
the future.
Mar 19 12:16:57 f18engine kernel: [ 30.004352] cgroup: libvirtd
(1046) created nested cgroup for controller "blkio" which has
incomplete hierarchy support. Nested cgroups may change behavior in
the future.
Mar 19 12:16:57 f18engine systemd[1]: Started oVirt Engine.
Mar 19 12:16:57 f18engine systemd[1]: Starting Multi-User.
Mar 19 12:16:57 f18engine systemd[1]: Reached target Multi-User.
Mar 19 12:16:57 f18engine systemd[1]: Starting Update UTMP about
System Runlevel Changes...
Mar 19 12:16:57 f18engine systemd[1]: Starting Stop Read-Ahead Data
Collection 10s After Completed Startup.
Mar 19 12:16:57 f18eng
Re: [Users] Problem install
Hi Marcelo! On Tue, Mar 19, 2013 at 3:51 PM, Marcelo Barbosa wrote: Alex, i am check: # rpm -qa | grep sanlock sanlock-2.6-7.fc18.x86_64 libvirt-lock-sanlock-0.10.2.3-1.fc18.x86_64 sanlock-lib-2.6-7.fc18.x86_64 sanlock-python-2.6-7.fc18.x86_64 Thanks! you would like make reinstall ? I can try again... Marcelo Barbosa mr.marcelo.barb...@gmail.com Can you please also check the contents of the /etc/sysconfig/wdmd? Just attach it to the mail. Thanks. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Problem install
Hi Marcelo
Can you please check that you have sanlock-2.6-7 installed?
Thanks.
On Wed, Mar 6, 2013 at 10:51 PM, Marcelo Barbosa
wrote:
Alex,
Thankyou for attention. This return should not happen, because I
have my hostname registered and running on my DNS servers, but i'm
inserted in /etc/hosts my hostname and retry setup, but return new
error:
2013-03-06 17:35:14::DEBUG::all_in_one_100::297::root:: Waiting for
host to become operational
2013-03-06 17:35:14::DEBUG::all_in_one_100::300::root:: current host
status is: up
2013-03-06 17:35:14::DEBUG::all_in_one_100::302::root:: The host is
up.
2013-03-06 17:35:14::DEBUG::setup_sequences::59::root:: running
addStorageDomain
2013-03-06 17:35:14::DEBUG::all_in_one_100::317::root:: Adding local
storage domain
2013-03-06 17:35:14::INFO::all_in_one_100::322::root:: Creating local
storage
2013-03-06 17:35:14::INFO::all_in_one_100::326::root:: Creating local
storage domain
2013-03-06 17:35:14::INFO::all_in_one_100::334::root:: Adding local
storage domain
2013-03-06 17:35:15::ERROR::all_in_one_100::337::root:: Traceback
(most recent call last):
File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py",
line 335, in addStorageDomain
controller.CONF["API_OBJECT"].storagedomains.add(sdParams)
File
"/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py",
line 5151, in add
headers={"Expect":expect, "Correlation-Id":correlation_id})
File
"/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",
line 118, in add
return self.request('POST', url, body, headers)
File
"/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",
line 129, in request
last=last)
File
"/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",
line 159, in __doRequest
raise RequestError, response
RequestError:
status: 400
reason: Bad Request
detail: Cannot add Storage. Internal error, Storage Connection
doesn't exist.
2013-03-06 17:35:15::DEBUG::setup_sequences::62::root:: Traceback
(most recent call last):
File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line
60, in run
function()
File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py",
line 338, in addStorageDomain
raise Exception(ERROR_ADD_LOCAL_DOMAIN)
Exception: Error: could not add local storage domain
2013-03-06 17:35:15::DEBUG::engine-setup::1948::root:: *** The
following params were used as user input:
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
override-httpd-config: yes
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: http-port: 80
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: https-port: 443
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
random-passwords: no
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: mac-range:
00:1A:4A:10:FF:00-00:1A:4A:10:FF:FF
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: host-fqdn:
firelap.usc.unirede.net
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: auth-pass:
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: org-name:
firelap
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
application-mode: both
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
default-dc-type: NFS
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
db-remote-install: local
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: db-host:
localhost
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: db-local-pass:
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: nfs-mp:
/firebackup//iso
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
iso-domain-name: ISO_DOMAIN
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: config-nfs: yes
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
override-firewall: IPTables
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
config-allinone: yes
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root:: storage-path:
/firebackup//vms
2013-03-06 17:35:15::DEBUG::engine-setup::1953::root::
superuser-pass:
2013-03-06 17:35:15::ERROR::engine-setup::2369::root:: Traceback
(most recent call last):
File "/bin/engine-setup", line 2363, in
main(confFile)
File "/bin/engine-setup", line 2146, in main
runSequences()
File "/bin/engine-setup", line 2068, in runSequences
controller.runAllSequences()
File "/usr/share/ovirt-engine/scripts/setup_controller.py", line
54, in runAllSequences
sequence.run()
File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line
154, in run
step.run()
File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line
60, in run
function()
File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py",
line 338, in addStorageDomain
raise Exception(ERROR_ADD_LOCAL_DOMAIN)
Exception: Error: could not add local storage domain
Any ideas to solve this problem?
Marcelo Barbosa
mr.marcelo.barb...@gmail.com
On Wed, Mar 6, 2013 a
Re: [Users] oVirt 3.2.1 and reports update error
Jose Let's ignore notifierd for a second. How the dwhd is going? On Tue, Mar 19, 2013 at 2:13 PM, supo...@logicworks.pt wrote: The command service engine-notifierd stop and service engine-notifierd start sends an error: systemctl status engine-notifierd.service engine-notifierd.service - SYSV: The oVirt event notification service Loaded: loaded (/etc/rc.d/init.d/engine-notifierd) Active: failed (Result: exit-code) since Tue 2013-03-19 12:05:33 WET; 43s ago Process: 1952 ExecStart=/etc/rc.d/init.d/engine-notifierd start (code=exited, status=1/FAILURE) Mar 19 12:05:33 foot.acloud.pt runuser[1955]: pam_unix(runuser:session): session opened for user ovirt ...d=0) Mar 19 12:05:33 foot.acloud.pt engine-notifierd[1952]: Starting engine-notifier: at Tue Mar 19 12:05:33 ...onf Mar 19 12:05:33 foot.acloud.pt runuser[1955]: pam_unix(runuser:session): session closed for user ovirt Mar 19 12:05:33 foot.acloud.pt engine-notifierd[1952]: [17B blob data] Mar 19 12:05:33 foot.acloud.pt systemd[1]: engine-notifierd.service: control process exited, code=exite...us=1 Mar 19 12:05:33 foot.acloud.pt systemd[1]: Failed to start SYSV: The oVirt event notification service. Mar 19 12:05:33 foot.acloud.pt systemd[1]: Unit engine-notifierd.service entered failed state tail /var/log/messages Mar 19 12:05:14 foot systemd[1]: Starting LSB: oVirt Engine History ETL Service for Data Warehouse and Reporting... Mar 19 12:05:24 foot ovirt-engine-dwhd[1877]: Starting ovirt-engine-dwhd: at Tue Mar 19 12:05:14 WET 2013[ OK ] Mar 19 12:05:24 foot systemd[1]: Started LSB: oVirt Engine History ETL Service for Data Warehouse and Reporting. Mar 19 12:05:29 foot systemd[1]: Stopped SYSV: The oVirt event notification service. Mar 19 12:05:33 foot systemd[1]: Starting SYSV: The oVirt event notification service... Mar 19 12:05:33 foot engine-notifierd[1952]: Starting engine-notifier: at Tue Mar 19 12:05:33 WET 2013Error: $MAIL_SERVER is not defined, please check for this in configuration file /etc/ovirt-engine/notifier/notifier.conf Mar 19 12:05:33 foot engine-notifierd[1952]: [FAILED]#015[FAILED] Mar 19 12:05:33 foot systemd[1]: engine-notifierd.service: control process exited, code=exited status=1 Mar 19 12:05:33 foot systemd[1]: Failed to start SYSV: The oVirt event notification service. Mar 19 12:05:33 foot systemd[1]: Unit engine-notifierd.service entered failed state have a problem in the $MAIL_SERVER ? the problem is the login page appears scrambled: https://docs.google.com/file/d/0BwoPbcrMv8mvQ3piS2xCRnRZdzg/edit?usp=sharing De: "Alex Lourie" Para: supo...@logicworks.pt Cc: "users" , "Gianluca Cecchi" Enviadas: Terça-feira, 19 de Março de 2013 11:48:51 Assunto: Re: [Users] oVirt 3.2.1 and reports update error Hi Jose On Tue, Mar 19, 2013 at 12:18 PM, supo...@logicworks.pt wrote: > Yeah, Reports does not work for me too. Either, with IE10 or Firefox > 19.0.2 > Any idea how to fix this? > Try starting the services manually: service notifierd start service ovirt-engine-dwhd start and try again. > > Thanks > Jose > > De: "Alex Lourie" > Para: "Gianluca Cecchi" > Cc: "users" > Enviadas: Domingo, 17 de Março de 2013 9:29:30 > Assunto: Re: [Users] oVirt 3.2.1 and reports update error > > Hi Gianluca > > On Sat, Mar 16, 2013 at 12:35 AM, Gianluca Cecchi > wrote: > > Hello, > > an all-in-one setup with oVirt 3.2 on Fedora 18. > > # yum update ovirt-engine-setup > > and then > > # engine-upgrade > > > > with this output > > ... > > During the upgrade process, oVirt Engine will not be accessible. > > All existing running virtual machines will continue but you will > not > > be able to > > start or stop any new virtual machines during the process. > > > > Would you like to proceed? (yes|no): yes > > Stopping ovirt-engine service... > [ DONE ] > > Stopping DB related services... > [ DONE ] > > Pre-upgrade validations... > [ DONE ] > > Backing Up Database... > [ DONE ] > > Rename Database... > [ DONE ] > > Updating rpms... > [ DONE ] > > Updating Database... > [ DONE ] > > Restore Database name... > [ DONE ] > > Preparing CA... > [ DONE ] > > Running post install configuration... [ > DONE ] > > Starting ovirt-engine service... > [ DONE ] > > > > oVirt Engine upgrade completed successfully! > &
Re: [Users] oVirt 3.2.1 and reports update error
Hi Jose On Tue, Mar 19, 2013 at 12:18 PM, supo...@logicworks.pt wrote: Yeah, Reports does not work for me too. Either, with IE10 or Firefox 19.0.2 Any idea how to fix this? Try starting the services manually: service notifierd start service ovirt-engine-dwhd start and try again. Thanks Jose De: "Alex Lourie" Para: "Gianluca Cecchi" Cc: "users" Enviadas: Domingo, 17 de Março de 2013 9:29:30 Assunto: Re: [Users] oVirt 3.2.1 and reports update error Hi Gianluca On Sat, Mar 16, 2013 at 12:35 AM, Gianluca Cecchi wrote: > Hello, > an all-in-one setup with oVirt 3.2 on Fedora 18. > # yum update ovirt-engine-setup > and then > # engine-upgrade > > with this output > ... > During the upgrade process, oVirt Engine will not be accessible. > All existing running virtual machines will continue but you will not > be able to > start or stop any new virtual machines during the process. > > Would you like to proceed? (yes|no): yes > Stopping ovirt-engine service... [ DONE ] > Stopping DB related services... [ DONE ] > Pre-upgrade validations... [ DONE ] > Backing Up Database... [ DONE ] > Rename Database... [ DONE ] > Updating rpms... [ DONE ] > Updating Database... [ DONE ] > Restore Database name... [ DONE ] > Preparing CA... [ DONE ] > Running post install configuration... [ DONE ] > Starting ovirt-engine service... [ DONE ] > > oVirt Engine upgrade completed successfully! > > * Error: Can't start the ovirt-engine-dwhd service > * Upgrade log available at > /var/log/ovirt-engine/ovirt-engine-upgrade_2013_03_15_23_16_02.log > * Perform the following steps to upgrade the history service or the > reporting package: > 1. Execute: yum update ovirt-engine-reports* > 2. Execute: ovirt-engine-dwh-setup > 3. Execute: ovirt-engine-reports-setup > * DB Backup available at > /var/lib/ovirt-engine/backups/ovirt-engine_db_backup_2013_03_15_23_16_03.sql > > [root@tekkaman ~]# yum update ovirt-engine-reports* > Loaded plugins: fastestmirror, langpacks, presto, refresh-packagekit, > versionlock > Loading mirror speeds from cached hostfile > * fedora: fedora.mirror.garr.it > * livna: ftp-stud.fht-esslingen.de > * rpmfusion-free: ftp.nluug.nl > * rpmfusion-free-updates: ftp.nluug.nl > * rpmfusion-nonfree: ftp.nluug.nl > * rpmfusion-nonfree-updates: ftp.nluug.nl > * updates: ftp.nluug.nl > No Packages marked for Update > > Do I have to consider or not the error regarding reports? > Sure, yes; this is being already handled and will be merged into master upstream for ovirt-engine-dwh. > > After a reboot webadmin is ok but reports appears as totally > scrambled: > - login page > https://docs.google.com/file/d/0BwoPbcrMv8mvQ3piS2xCRnRZdzg/edit?usp=sharing > > - after login > https://docs.google.com/file/d/0BwoPbcrMv8mvNm1VVnk4cDhDR0U/edit?usp=sharing > > these above are from Fedora 18 and firefox 19.0.2 > It seems that something is wrong with CSS loading. Do you have any CSS/JS blocker addons installed in Firefox? > > > Gianluca > ___ > 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: [Users] engine-setup fails to setup ports when SElinux is disabled
Hi Dennis, all On Fri, Mar 15, 2013 at 10:12 AM, Itamar Heim wrote: On 02/25/2013 06:50 PM, Sandro Bonazzola wrote: Hi Dennis, the bug https://bugzilla.redhat.com/show_bug.cgi?id=893562 has a patch merged in the master tree, it's not included in oVirt 3.2. As a workaround, if you don't want selinux enforcing, enable selinux in permissive mode. Regards, did we backport this to 3.2.1? No, we didn't backport it to 3.2.1; but anyway the 'fix' is exactly the same as the workaround - to enable SELINUX at least in the permissive mode. The real problem lies in Fedora's security policies packages with breaks the functionality of the semanage utility. It is still not fixed in the Fedora repos, thus in our setup we just exit gracefully and ask to turn the selinux on. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Alex. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt 3.2.1 and reports update error
Hi Gianluca On Sat, Mar 16, 2013 at 12:35 AM, Gianluca Cecchi wrote: Hello, an all-in-one setup with oVirt 3.2 on Fedora 18. # yum update ovirt-engine-setup and then # engine-upgrade with this output ... During the upgrade process, oVirt Engine will not be accessible. All existing running virtual machines will continue but you will not be able to start or stop any new virtual machines during the process. Would you like to proceed? (yes|no): yes Stopping ovirt-engine service...[ DONE ] Stopping DB related services... [ DONE ] Pre-upgrade validations... [ DONE ] Backing Up Database... [ DONE ] Rename Database... [ DONE ] Updating rpms...[ DONE ] Updating Database...[ DONE ] Restore Database name...[ DONE ] Preparing CA... [ DONE ] Running post install configuration... [ DONE ] Starting ovirt-engine service...[ DONE ] oVirt Engine upgrade completed successfully! * Error: Can't start the ovirt-engine-dwhd service * Upgrade log available at /var/log/ovirt-engine/ovirt-engine-upgrade_2013_03_15_23_16_02.log * Perform the following steps to upgrade the history service or the reporting package: 1. Execute: yum update ovirt-engine-reports* 2. Execute: ovirt-engine-dwh-setup 3. Execute: ovirt-engine-reports-setup * DB Backup available at /var/lib/ovirt-engine/backups/ovirt-engine_db_backup_2013_03_15_23_16_03.sql [root@tekkaman ~]# yum update ovirt-engine-reports* Loaded plugins: fastestmirror, langpacks, presto, refresh-packagekit, versionlock Loading mirror speeds from cached hostfile * fedora: fedora.mirror.garr.it * livna: ftp-stud.fht-esslingen.de * rpmfusion-free: ftp.nluug.nl * rpmfusion-free-updates: ftp.nluug.nl * rpmfusion-nonfree: ftp.nluug.nl * rpmfusion-nonfree-updates: ftp.nluug.nl * updates: ftp.nluug.nl No Packages marked for Update Do I have to consider or not the error regarding reports? Sure, yes; this is being already handled and will be merged into master upstream for ovirt-engine-dwh. After a reboot webadmin is ok but reports appears as totally scrambled: - login page https://docs.google.com/file/d/0BwoPbcrMv8mvQ3piS2xCRnRZdzg/edit?usp=sharing - after login https://docs.google.com/file/d/0BwoPbcrMv8mvNm1VVnk4cDhDR0U/edit?usp=sharing these above are from Fedora 18 and firefox 19.0.2 It seems that something is wrong with CSS loading. Do you have any CSS/JS blocker addons installed in Firefox? Gianluca ___ 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: [Users] Features requests for the setup/configuration utilities - feedback requested
Hi Jiri On Thu, Mar 14, 2013 at 4:30 PM, Jiri Belka wrote: I'll talk about RHEVM but it's probably related to oVirt too. As rhevm installs all deps, I'm curious why versionlock.list is populated after rhevm-setup and _not_dirrectly during installation (maybe because you would need to hardcode versions into rhevm package?). It took me tens of minutes to figure out why is upgrade working differently now, just because I did _NOT_ do rhevm-setup after clean install because I was thinking I know what files are important and was restoring them from a tarball. I think running rhevm-setup if you just want to restore is stupid. If we would know 100% which files are involved, just install, restore from backup, restore DB should be sufficient, without loosing time with rhevm-setup which just writes there and here... :) I don't really follow you here. What are you restoring with rhevm-setup? jbelka ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Features requests for the setup/configuration utilities - feedback requested
- Original Message - From: "Jiri Belka" To: "Alex Lourie" Cc: engine-de...@ovirt.org, Users@ovirt.org Sent: Thursday, March 14, 2013 2:52:31 PM Subject: Re: [Users] Features requests for the setup/configuration utilities - feedback requested On Thu, 14 Mar 2013 12:12:25 +0002 Alex Lourie wrote: > Hi All > > As we are working on the configuration utilities (engine-setup, > engine-upgrade and engine-cleanup), we would like to get as much > community involvement as possible. As such, we'd like to hear the > wishes of the community in regards with those tools. 1. do not think yum is everywhere, make package upgrade extensible by some subclasses (apt-get, pkg_add...) Right. 2. usernames are not same everywhere postgres is not everywhere Right. 3. do not make absolute symlinks, some packaging tools scream I replied to this one, I don't fully agree, relative symlinks have their own issues, and hard to convert absolute to relative when 3rd party components are involved. 4. do not use #!/bin/bash but #!/bin/sh, in 99,9% people are not using anything special from bash anyway This is out of scope, we will depend on bash for now... too much legacy. We can attend to that in future. I can promise that no new code will be written in bash. Thanks! jbelka ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Wiki updated. Thanks! ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Features requests for the setup/configuration utilities - feedback requested
Hi All As we are working on the configuration utilities (engine-setup, engine-upgrade and engine-cleanup), we would like to get as much community involvement as possible. As such, we'd like to hear the wishes of the community in regards with those tools. I've created a wiki page [1] where we will keep the list of feature requests. We would appreciate adding features to the list of by replying to this thread directly. Please do not bugs to that list - the bugs should be resolved in due course according to their priorities and should not affect the features that we would like to implement. Thank you. [1] http://www.ovirt.org/Features/Engine-Config-Utilities -- Alex Lourie Software Engineer in RHEVM Integration Red Hat ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Migrating engine-setup to otopi
Hi Jiri - Original Message - > From: "Jiri Belka" > To: "Alex Lourie" > Cc: engine-de...@ovirt.org, users@ovirt.org > Sent: Thursday, March 14, 2013 12:38:46 PM > Subject: Re: [Users] Migrating engine-setup to otopi > > On Thu, 14 Mar 2013 06:13:39 -0400 (EDT) > Alex Lourie wrote: > > > Hi All > > > > Recent development of the otopi [1] framework allows us to migrate > > the engine-setup, > > upgrade and cleanup (and potentially other) utilities to > > implementation as an otopi > > plugin. > > > > Potential benefits of such a move are: > > > > 1. Be able to port engine to other distributions. > > Really? Beside this topic I see hardcoded usernames in scripts... > > http://gerrit.ovirt.org/#/c/12551/2/backend/manager/dbscripts/dbfunctions.sh,unified These usernames are not hard-coded. There are default values present which are kept for local installations, but with remote DB setup the user is prompted to provide a username of her/his own. > > Anyway, everything what is not RPM/YUM specific and more portable > is good way... > Thanks! > jbelka > -- Best regards, Alex Lourie Software Developer in Integration Red Hat ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Migrating engine-setup to otopi
Hi All Recent development of the otopi [1] framework allows us to migrate the engine-setup, upgrade and cleanup (and potentially other) utilities to implementation as an otopi plugin. Potential benefits of such a move are: 1. Be able to port engine to other distributions. 2. Be able to install engine in a development mode. 3. Be able to customize installation easily. 4. Share installation of components (reports, dwh). 5. Modular implementation, reduce maintenance costs. 6. Code reuse of installer code for multiple purposes (host-deploy, enigne-setup). Currently we are in the process of creating a 'setup' plugin for the otopi, and the progress can be monitored at [2]. The current roadmap for the feature is as follows: 1. Recreate the configuration utilities as plugins in otopi. 2. Support side-by side installation using both the old and the new utilities. 3. Switch to the new utility when the confidence that it is on-par with an old one is high. Our goal is to have the new utilities ready for 3.3 release (at least for the step 2 in the roadmap). We'd like to hear as much feedback as possible, so we could address it as soon as possible. Thanks! [1] http://gerrit.ovirt.org/#/q/project:otopi,n,z [2] http://www.ovirt.org/Features/Otopi_Infra_Migration ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt 3.2 all-in-one setup always fails
Hi Alex On Sun, Mar 10, 2013 at 4:26 PM, Alex Leonhardt wrote: Hi Alex, Regarding the dependencies - libvirtd would not start w/o having messagebus / avahi-daemon installed & running, however, it doesnt seem to come up as an dependency when installing libvirtd (otherwise it would have been installed previously) ? wow, that's strange. I haven't seen this before. I suggest opening a bug on libvirt anyway. I read this "solution" on some blog page, and based on that installed avahi-daemon & messagebus + started them, only then libvirtd started up. vdsmd wont tell you it's waiting for libvirtd to start on the console, it'll mention in the log that "it's waiting for libvirtd" and eventually will time out. Granted, if these are the required dependencies, then definitely they should be installed. I will look into this and try to understand what is it about. Thanks, Alex On 03/10/2013 10:19 AM, Alex Lourie wrote: On Fri 08 Mar 2013 04:33:53 PM IST, Alex Leonhardt wrote: Also, the there seem to be missing some dependencies for - messagebus (service not enabled/started/installed) - avahi-daemon (wasnt installed, had to install and start / enable) else libvirtd will not start and the setup will fail. On 8 March 2013 14:30, Alex Leonhardt <mailto:alex.t...@gmail.com>> wrote: And here from when I tried to use "localhost" as the host / fqdn : Installing: AIO: Validating CPU Compatibility... [ DONE ] AIO: Adding firewall rules... [ DONE ] Configuring oVirt Engine... [ DONE ] Configuring JVM... [ DONE ] Creating CA... [ DONE ] Updating ovirt-engine service... [ DONE ] Setting Database Configuration... [ DONE ] Setting Database Security... [ DONE ] Creating Database... [ DONE ] Updating the Default Data Center Storage Type... [ DONE ] Editing oVirt Engine Configuration... [ DONE ] Editing Postgresql Configuration... [ DONE ] Configuring the Default ISO Domain... [ DONE ] Configuring Firewall... [ DONE ] Starting ovirt-engine Service... [ DONE ] Configuring HTTPD... [ DONE ] AIO: Creating storage directory... [ DONE ] AIO: Adding Local Datacenter and cluster... [ DONE ] AIO: Adding Local host (This may take several minutes)... [ ERROR ] Error: Host was found in a 'Failed' state. Please check engine and bootstrap installation logs. Please check log file /var/log/ovirt-engine/engine-setup_2013_03_08_14_10_56.log for more information Exception in thread libvirtEventLoop (most likely raised during interpreter shutdown) # 2013-03-08 14:13:33::DEBUG::setup_sequences::59::root:: running _loadFilesToIsoDomain 2013-03-08 14:13:33::ERROR::engine-setup::1838::root:: Traceback (most recent call last): File "/usr/bin/engine-setup", line 1835, in _loadFilesToIsoDomain utils.copyFile(filename, targetPath, basedefs.CONST_VDSM_UID, basedefs.CONST_KVM_GID) File "/usr/share/ovirt-engine/scripts/common_utils.py", line 706, in copyFile shutil.copy2(fileSrc, destination) File "/usr/lib64/python2.6/shutil.py", line 95, in copy2 copyfile(src, dst) File "/usr/lib64/python2.6/shutil.py", line 50, in copyfile with open(src, 'rb') as fsrc: IOError: [Errno 2] No such file or directory: '/usr/share/virtio-win/virtio-win.vfd' 2013-03-08 14:13:33::ERROR::engine-setup::1839::root:: Failed to copy files to iso domain [snip] 2013-03-08 14:14:14::DEBUG::setup_sequences::59::root:: running waitForHostUp 2013-03-08 14:14:14::DEBUG::all_in_one_100::303::root:: Waiting for host to become operational 2013-03-08 14:14:14::DEBUG::all_in_one_100::306::root:: current host status is: installing 2013-03-08 14:14:14::DEBUG::all_in_one_100::317::root:: Traceback (most recent call last): File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line 314, in isHostUp raise Exception(INFO_CREATE_HOST_WAITING_UP) Exception: Waiting for the host to start 2013-03-08 14:14:19::DEBUG::all_in_one_100::303::root:: Waiting for host to become operational 2013-03-08 14:14:19::DEBUG::all_in_one_100::306::root:: current host status is: install_failed 2013-03-08 14:14:19::DEBUG::all_in_one_100::317::root:: Traceback (most recent call last): File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line 312, in isHostUp raise utils.RetryFailException(ERROR_CREATE_HOST_FAILED) RetryFailException: Error: Host was found in a 'Fa
Re: [Users] ovirt 3.2 all-in-one setup always fails
_100::306::root:: current host status is: installing 2013-03-08 14:22:43::DEBUG::all_in_one_100::317::root:: Traceback (most recent call last): File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line 314, in isHostUp raise Exception(INFO_CREATE_HOST_WAITING_UP) Exception: Waiting for the host to start 2013-03-08 14:22:48::DEBUG::all_in_one_100::303::root:: Waiting for host to become operational 2013-03-08 14:22:49::DEBUG::all_in_one_100::306::root:: current host status is: install_failed 2013-03-08 14:22:49::DEBUG::all_in_one_100::317::root:: Traceback (most recent call last): File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line 312, in isHostUp raise utils.RetryFailException(ERROR_CREATE_HOST_FAILED) RetryFailException: Error: Host was found in a 'Failed' state. Please check engine and bootstrap installation logs. 2013-03-08 14:22:49::DEBUG::setup_sequences::62::root:: Traceback (most recent call last): File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 60, in run function() File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line 300, in waitForHostUp utils.retry(isHostUp, tries=120, timeout=600, sleep=5) File "/usr/share/ovirt-engine/scripts/common_utils.py", line 1010, in retry raise e RetryFailException: Error: Host was found in a 'Failed' state. Please check engine and bootstrap installation logs. 2013-03-08 14:22:49::DEBUG::engine-setup::1934::root:: *** The following params were used as user input: I have the full log if required ?? Any help would be appreciated. The options used were : oVirt Engine will be installed using the following configuration: = override-httpd-config: yes http-port: 80 https-port:443 host-fqdn: stphv01 auth-pass: org-name: LOCAL application-mode: both default-dc-type: NFS db-remote-install: local db-local-pass: nfs-mp:/exports/iso override-firewall: None config-allinone: yes storage-path: /vmfs/ovirt superuser-pass: Alex -- | RHCE | Senior Systems Engineer | www.vcore.co <http://www.vcore.co> | www.vsearchcloud.com <http://www.vsearchcloud.com> | -- | RHCE | Senior Systems Engineer | www.vcore.co <http://www.vcore.co> | www.vsearchcloud.com <http://www.vsearchcloud.com> | -- | RHCE | Senior Systems Engineer | www.vcore.co <http://www.vcore.co> | www.vsearchcloud.com <http://www.vsearchcloud.com> | ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Hi Alex Could you please elaborate a bit on these dependencies? Do you have any logs that state the problem? Regarding the rest of the problem (that is adding the host), we're already looking into this. -- Best regards, Alex Lourie Software Developer in Integration Red Hat ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Problem install
On Thu 07 Mar 2013 06:15:52 PM IST, Marcelo Barbosa wrote:
Hi Alex,
Thankyou for interation, i'm register this problem in bugzilla for
a engineering team from ovirt project check:
https://bugzilla.redhat.com/show_bug.cgi?id=918742
full log and informations this.
Marcelo Barbosa
/mr.marcelo.barb...@gmail.com <mailto:mr.marcelo.barb...@gmail.com>/
On Thu, Mar 7, 2013 at 8:08 AM, Alex Lourie mailto:alou...@redhat.com>> wrote:
On Wed 06 Mar 2013 10:51:43 PM IST, Marcelo Barbosa wrote:
Alex,
Thankyou for attention. This return should not happen,
because I
have my hostname registered and running on my DNS servers, but i'm
inserted in /etc/hosts my hostname and retry setup, but return
new error:
2013-03-06 17:35:14::DEBUG::all_in_one___100::297::root::
Waiting for
host to become operational
2013-03-06 17:35:14::DEBUG::all_in_one___100::300::root::
current host
status is: up
2013-03-06 17:35:14::DEBUG::all_in_one___100::302::root:: The
host is up.
2013-03-06 17:35:14::DEBUG::setup___sequences::59::root:: running
addStorageDomain
2013-03-06 17:35:14::DEBUG::all_in_one___100::317::root::
Adding local
storage domain
2013-03-06 17:35:14::INFO::all_in_one___100::322::root::
Creating local
storage
2013-03-06 17:35:14::INFO::all_in_one___100::326::root::
Creating local
storage domain
2013-03-06 17:35:14::INFO::all_in_one___100::334::root::
Adding local
storage domain
2013-03-06 17:35:15::ERROR::all_in_one___100::337::root::
Traceback
(most recent call last):
File
"/usr/share/ovirt-engine/__scripts/plugins/all_in_one___100.py",
line 335, in addStorageDomain
controller.CONF["API_OBJECT"].__storagedomains.add(sdParams)
File
"/usr/lib/python2.7/site-__packages/ovirtsdk/__infrastructure/brokers.py",
line 5151, in add
headers={"Expect":expect, "Correlation-Id":correlation___id})
File
"/usr/lib/python2.7/site-__packages/ovirtsdk/__infrastructure/proxy.py",
line 118, in add
return self.request('POST', url, body, headers)
File
"/usr/lib/python2.7/site-__packages/ovirtsdk/__infrastructure/proxy.py",
line 129, in request
last=last)
File
"/usr/lib/python2.7/site-__packages/ovirtsdk/__infrastructure/proxy.py",
line 159, in __doRequest
raise RequestError, response
RequestError:
status: 400
reason: Bad Request
detail: Cannot add Storage. Internal error, Storage Connection
doesn't
exist.
2013-03-06 17:35:15::DEBUG::setup___sequences::62::root::
Traceback
(most recent call last):
File "/usr/share/ovirt-engine/__scripts/setup_sequences.py",
line 60,
in run
function()
File
"/usr/share/ovirt-engine/__scripts/plugins/all_in_one___100.py",
line 338, in addStorageDomain
raise Exception(ERROR_ADD_LOCAL___DOMAIN)
Exception: Error: could not add local storage domain
2013-03-06 17:35:15::DEBUG::engine-setup:__:1948::root:: *** The
following params were used as user input:
2013-03-06 17:35:15::DEBUG::engine-setup:__:1953::root::
override-httpd-config: yes
2013-03-06 17:35:15::DEBUG::engine-setup:__:1953::root::
http-port: 80
2013-03-06 17:35:15::DEBUG::engine-setup:__:1953::root::
https-port: 443
2013-03-06 17:35:15::DEBUG::engine-setup:__:1953::root::
random-passwords: no
2013-03-06 17:35:15::DEBUG::engine-setup:__:1953::root::
mac-range:
00:1A:4A:10:FF:00-00:1A:4A:10:__FF:FF
2013-03-06 17:35:15::DEBUG::engine-setup:__:1953::root::
host-fqdn:
firelap.usc.unirede.net <http://firelap.usc.unirede.net>
<http://firelap.usc.unirede.__net
<http://firelap.usc.unirede.net>>
2013-03-06 17:35:15::DEBUG::engine-setup:__:1953::root::
auth-pass:
2013-03-06 17:35:15::DEBUG::engine-setup:__:1953::root::
org-name: firelap
2013-03-06 17:35:15::DEBUG::engine-setup:__:1953::root::
application-mode: both
2013-03-06 17:35:15::DEBUG::engine-setup:__:1953::root::
default-dc-type: NFS
2013-03-06 17:35:15::DEBUG::engine-setup:__:1953::root::
db-remote-install: local
2013-03-06 17:35:15::DEBUG::engine-setup:__:1953::root::
db-host: localhost
2013-03-06 17:35:15::DEBUG::engine-setup:__:1953::root::
db-local-pass:
2013-
Re: [Users] Problem install
14:35:56::DEBUG::engine-setup::1953::root::
auth-pass:
2013-03-06 14:35:56::DEBUG::engine-setup::1953::root::
org-name: firelap.usc.unirede.net
<http://firelap.usc.unirede.net>
2013-03-06 14:35:56::DEBUG::engine-setup::1953::root::
application-mode: both
2013-03-06 14:35:56::DEBUG::engine-setup::1953::root::
default-dc-type: NFS
2013-03-06 14:35:56::DEBUG::engine-setup::1953::root::
db-remote-install: local
2013-03-06 14:35:56::DEBUG::engine-setup::1953::root::
db-host: localhost
2013-03-06 14:35:56::DEBUG::engine-setup::1953::root::
db-local-pass:
2013-03-06 14:35:56::DEBUG::engine-setup::1953::root::
nfs-mp: /firebackup//iso
2013-03-06 14:35:56::DEBUG::engine-setup::1953::root::
iso-domain-name: ISO_DOMAIN
2013-03-06 14:35:56::DEBUG::engine-setup::1953::root::
config-nfs: yes
2013-03-06 14:35:56::DEBUG::engine-setup::1953::root::
override-firewall: IPTables
2013-03-06 14:35:56::DEBUG::engine-setup::1953::root::
config-allinone: yes
2013-03-06 14:35:56::DEBUG::engine-setup::1953::root::
storage-path: /firebackup//vms
2013-03-06 14:35:56::DEBUG::engine-setup::1953::root::
superuser-pass:
2013-03-06 14:35:56::ERROR::engine-setup::2369::root::
Traceback (most recent call last):
File "/bin/engine-setup", line 2363, in
main(confFile)
File "/bin/engine-setup", line 2146, in main
runSequences()
File "/bin/engine-setup", line 2068, in runSequences
controller.runAllSequences()
File
"/usr/share/ovirt-engine/scripts/setup_controller.py",
line 54, in runAllSequences
sequence.run()
File
"/usr/share/ovirt-engine/scripts/setup_sequences.py", line
154, in run
step.run()
File
"/usr/share/ovirt-engine/scripts/setup_sequences.py", line
60, in run
function()
File
"/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py",
line 294, in waitForHostUp
utils.retry(isHostUp, tries=120, timeout=600, sleep=5)
File "/usr/share/ovirt-engine/scripts/common_utils.py",
line 1009, in retry
raise e
RetryFailException: Error: Host was found in a 'Failed'
state. Please check engine and bootstrap installation logs.
Thnkz for attention.
Marcelo Barbosa
/mr.marcelo.barb...@gmail.com
<mailto:mr.marcelo.barb...@gmail.com>/
___
Users mailing list
Users@ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Hi Marcelo
First, it seems that you have passed adding the host step, which is
good.
Second, about the adding storage - may Michael could help us understand
what the following error means:
RequestError:
status: 400
reason: Bad Request
detail: Cannot add Storage. Internal error, Storage Connection doesn't
exist.
--
Best regards,
Alex Lourie
Software Developer in Integration
Red Hat
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] DB error on fresh ovirt install
On 02/20/2013 12:55 PM, Eli Mesika wrote: - Original Message - From: "Dead Horse" To: "" Sent: Tuesday, February 19, 2013 11:58:01 PM Subject: [Users] DB error on fresh ovirt install Normally I upgrade from prior test installs. However for the past two weeks or so attempting a fresh install yields: oVirt Engine will be installed using the following configuration: = override-httpd-config: yes http-port: 80 https-port: 443 host-fqdn: ovirtfoo.test.domain auth-pass: org-name: DHC application-mode: both default-dc-type: NFS db-remote-install: local db-local-pass: config-nfs: no override-firewall: None Proceed with the configuration listed above? (yes|no): yes Installing: Configuring oVirt Engine... [ DONE ] Configuring JVM... [ DONE ] Creating CA... [ DONE ] Updating ovirt-engine service... [ DONE ] Setting Database Configuration... [ DONE ] Setting Database Security... [ DONE ] Upgrading Database Schema... [ ERROR ] dictionary update sequence element #0 has length 1; 2 is required Please check log file /var/log/ovirt-engine/engine-setup_2013_02_19_15_31_02.log for more information log attached Hi Seems like a BUG in the setup Python script see http://www.gossamer-threads.com/lists/python/python/917709 Alex, Moran can you check please ? Hi All It is indeed a but in our setup utility. I've opened a bug [1]. - DHC ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users [1] https://bugzilla.redhat.com/show_bug.cgi?id=913176 -- Best regards, Alex Lourie Software Developer in Integration Red Hat ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Discussion... work appears to be needed in areas of recovery and cleanup
On 02/14/2013 03:35 PM, Rick Beldin wrote: Hi... I've been working with both RHEV and Ovirt and can see distinct changes and improvements with regards to how Ovirt is emerging and changing. One area that still disturbs me is in the area of recovery and cleanup, specifically around the ovirt-engine (rhevm) node. I've observed a few things about the project: - backup of a engine db seems to be a fairly manual process with many steps. There are many files listed that need to be backed up manually as listed in the RHEVM admin manual. pg_dump seems to automate the dumping of the db, but other config files are left up to the admin. - restoration appears to be equally complex - engine-cleanup (rhevm-cleanup) doesn't always cleanup - there appear to be instances where the only way to get a solid base is reinstallation. I've removed and reinstalled components so many times it is now second nature. ;) I'm curious about: - Are there technical issues (beyond the code not being written yet) that prevent backup and restore procedures from working correctly to save and restore an engine environment? I would expect that a test for that operation would be to setup an environment, take a snapshot, and restore the whole thing to another management node. - Are all the config files properly identified? The RHEVM Admin manual has an extensive list but is it exhaustive? - What technically prevents engine-cleanup from really *cleaning* a system? My expectation would be that I should be able to run engine-cleanup and completely wipe out the setup. All databases, certs, config files and the like returned to their original, pristine state. Perhaps another script - engine-restore-defaults? - needs to go beyond where engine-cleanup goes today? As a support professional, these are areas that I think warrant investment and I wonder what is gating the development here. Thanks, Rick Hey Rick! Firstly, thanks for the time and effort you have put into this, it is really appreciated. Secondly, I created wiki page [1] with the set of requirements for such utility/feature that you discussed here, this would help in developing it. Please feel free to comment/provide feedback. [1] http://www.ovirt.org/Backup_And_Restore_Engine -- Best regards, Alex Lourie Software Developer in Integration Red Hat ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Upgrading to Fedora 18
On Sun 17 Feb 2013 10:38:08 AM IST, Vered Volansky wrote: Hi Kevin, How about https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum ? If you have anything specific that is unclear to you, please feel free to ask again. Regarding ovirt upgrade - Have a look at: http://wiki.centos.org/HowTos/oVirt . It's much more elaborated than what you probably need, but you should follow the same instructions as ovirt installation. You can use yum update instead of yum install, that's it. Regards, Vered - Original Message - From: "Kevin Daly" To: users@ovirt.org Sent: Friday, February 15, 2013 11:38:23 PM Subject: [Users] Upgrading to Fedora 18 I have installed Ovirt 3.1 on a Fedora 17 server, and would like to upgrade to Fedora 18... The documentation I have found on the mailing list is unclear on how to do this. Does anyone have any pointers on how this can be done.. as well as upgrading to Ovirt 3.2 after we've upgraded to Fedora 18 Thanks In advance ___ 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 Hi Kevin In addition to what Vered said, and while we still test it, you just upgrade fedora to Fedora 18 release and then simply upgrade engine with engine-upgrade command. -- Best regards, Alex Lourie Red Hat ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Some updates show up, and some don´t
egards Karli Sjöberg ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Karli As soon as engine is installed, it's rpm's are locked within yum, and are not visible for manual upgrade. It is done to prevent updating RPMs separately and not as an application. If all you want is to upgrade engine, simply run 'engine-upgrade'. Let us know how it goes. -- Alex Lourie. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [3.2 Beta]Creating DB fails
On Mon 04 Feb 2013 09:48:55 AM IST, Gianluca Cecchi wrote: On Feb 4, 2013 3:18 AM, "Nicholas Kesick" mailto:cybertimber2...@hotmail.com>> wrote: > > Hey guys, I'm having a problem with engine-setup. When it gets to the creating database part, it fails. I've tried rebuilding the system (this time from Fedora minimal install) and I had the same problem. Any suggestions? I've attached the engine setup log and it basically ends with the "engine" database is not currently accepting connections. > > ovirt-engine-setup-3.1.0-4.fc17.noarch > kernel 3.7.4-204.fc18.x86_64 (also tried with what came on the dvd) > sytemctl status postgresql.service reports postgresql is active (running). > > - Nick > > ___ > Users mailing list > Users@ovirt.org <mailto:Users@ovirt.org> > http://lists.ovirt.org/mailman/listinfo/users > You wrote with 3.2 beta tag in subject, but you are using a 3.1 engine-setup? Can you detail better your environment? Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users The error message probably means that postgresql service is not running or not running on default port 5432. Please verify that it is up before you continue. -- Alex Lourie. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Engine upgrade failure broken in master
On Wed 30 Jan 2013 04:51:56 AM IST, Yair Zaslavsky wrote: Looks like the following commits around the async task clearner introduced between the two commits you specified - e16f21c1a42d418cfb7528b7819d97e576d715f3 That's the one that fixes the issue. 9393178a693cddc8756cf3b21198faa43407ff5d Looks like the one that handles the extra character fixes this. *From: *"Dead Horse" *To: *"" *Sent: *Tuesday, January 29, 2013 10:19:31 PM *Subject: *[Users] Engine upgrade failure broken in master Commit: 72a51f5e21f38bf259a460948670eac92e97ca24 Breaks engine upgrades: 2013-01-29 12:40:52::ERROR::engine-upgrade::1177::root:: Traceback (most recent call last): File "/usr/bin/engine-upgrade", line 1170, in main(options) File "/usr/bin/engine-upgrade", line 1071, in main if zombieTasksFound(): File "/usr/bin/engine-upgrade", line 766, in zombieTasksFound msg="Can't get zombie async tasks", File "/usr/share/ovirt-engine/scripts/common_utils.py", line 459, in execCmd env=env, File "/usr/lib64/python2.7/subprocess.py", line 679, in __init__ errread, errwrite) File "/usr/lib64/python2.7/subprocess.py", line 1249, in _execute_child raise child_exception OSError: [Errno 8] Exec format error Upgrade was attempted on engine built from commit: 61c11aecc40e755d08b6c34c6fe1c0a07fa94de8 Building from commit: 82bdc46dfdb46b000f67f0cd4e51fc39665bf13b and upgrading works as expected. - DHC ___ 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 -- Alex Lourie. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] 3.1 to 3.2 migration
On 01/29/2013 07:48 AM, saravanan s wrote: im using redhat 6.2 linux version for the virtualization concept. But here im facing issues , listed below . please give me a guidance 1)hypervisors(host) cant able to stop properly 2)vm'z multipath functions not functioning properly 3)Storage not getting shutdown , because heavy load? 4) while running vm's im getting threshold error message Hi It seems that you are having a problem(s) that are not related to this thread. Would you mind posting it as a separate thread with it's own subject? It would be easier for everyone to understand the context. Thanks. On Tue, Jan 29, 2013 at 11:11 AM, Alex Lourie <mailto:alou...@redhat.com>> wrote: On 01/24/2013 04:51 PM, Alexandru Vladulescu wrote: On 01/24/2013 04:42 PM, Adrian Gibanel wrote: *De: *"Alexandru Vladulescu" <mailto:avladule...@bfproject.ro> *Para: *users@ovirt.org <mailto:users@ovirt.org> *Enviados: *Jueves, 24 de Enero 2013 14:21:22 *Asunto: *Re: [Users] 3.1 to 3.2 migration Hi, On 01/24/2013 03:13 PM, Adrian Gibanel wrote: As far as I know in Fedora you need to upgrade from Fedora 17 to Fedora 18. As you you're using CentOS I suppose you don't need to upgrade your CentOS but I'm not sure at all. This is not the case, it goes right if installed 3.2 from scratch on a new machine. Don't think CentOS has a problem here. Well, I remember having asked about Fedora and CentOS oVirt support differences in the irc and I think I was answered that for some features you needed extra repositories for new kernel + kvm and / or gluster and /or libvirt. Not sure about what were exactly the features you missed and the repos you need to enable manually. But just for upgrading to oVirt 3.2 I think you won't have any problem. Anyways what I've read in the mailing list about 3.1 to 3.2 update is the following one: * Update packages * Run: engine-upgrade command I don't know how easy it is to update packages in your case (stable to beta) so you might do it in your way like this: * Remove 3.1 packages * Install 3.2 beta packages * Run: engine-upgrade command I have removed 3.1 using yum, installed 3.2 using yum and run the engine-setup and not upgrade command. As seen engine-upgrade, tries first to locate a mirror through yum. Hummm. Maybe I was mistaken and what you have to do is to add a yum repository and then run engine-upgrade. What I remember without any doubt is that you had to run engine-upgrade no matter what. Hope someone can clarify it. I will check that and get back to you. Hi Alex When you test the upgrade, please attach its log file. We then can look into the upgrade process and find issues if there are any. Thanks. -- <http://www.btactic.com/>*Adrián Gibanel* I.T. Manager +34 675 683 301 www.btactic.com <http://btactic.com/> * Ens podeu seguir a/Nos podeis seguir en: <http://www.facebook.com/pages/btactic/118651634826400?v=app_9953271133> i <http://twitter.com/btactic>* Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El medio ambiente es cosa de todos. AVIS: El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge per error, us agrairem que ho feu saber immediatament al remitent i que procediu a destruir el missatge. AVISO: El contenido de este mensaje y de sus anexos es confidencial. Si no es el destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o copiarlo sin tener la autorización correspondiente. Si han recibido este mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al remitente y que procedan a destruir el mensaje. ___ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users -- Alex Lourie Red Hat ___ Users mailing list
Re: [Users] 3.1 to 3.2 migration
On 01/24/2013 04:51 PM, Alexandru Vladulescu wrote: On 01/24/2013 04:42 PM, Adrian Gibanel wrote: *De: *"Alexandru Vladulescu" *Para: *users@ovirt.org *Enviados: *Jueves, 24 de Enero 2013 14:21:22 *Asunto: *Re: [Users] 3.1 to 3.2 migration Hi, On 01/24/2013 03:13 PM, Adrian Gibanel wrote: As far as I know in Fedora you need to upgrade from Fedora 17 to Fedora 18. As you you're using CentOS I suppose you don't need to upgrade your CentOS but I'm not sure at all. This is not the case, it goes right if installed 3.2 from scratch on a new machine. Don't think CentOS has a problem here. Well, I remember having asked about Fedora and CentOS oVirt support differences in the irc and I think I was answered that for some features you needed extra repositories for new kernel + kvm and / or gluster and /or libvirt. Not sure about what were exactly the features you missed and the repos you need to enable manually. But just for upgrading to oVirt 3.2 I think you won't have any problem. Anyways what I've read in the mailing list about 3.1 to 3.2 update is the following one: * Update packages * Run: engine-upgrade command I don't know how easy it is to update packages in your case (stable to beta) so you might do it in your way like this: * Remove 3.1 packages * Install 3.2 beta packages * Run: engine-upgrade command I have removed 3.1 using yum, installed 3.2 using yum and run the engine-setup and not upgrade command. As seen engine-upgrade, tries first to locate a mirror through yum. Hummm. Maybe I was mistaken and what you have to do is to add a yum repository and then run engine-upgrade. What I remember without any doubt is that you had to run engine-upgrade no matter what. Hope someone can clarify it. I will check that and get back to you. Hi Alex When you test the upgrade, please attach its log file. We then can look into the upgrade process and find issues if there are any. Thanks. -- <http://www.btactic.com/>*Adrián Gibanel* I.T. Manager +34 675 683 301 www.btactic.com <http://btactic.com/> * Ens podeu seguir a/Nos podeis seguir en: <http://www.facebook.com/pages/btactic/118651634826400?v=app_9953271133> i <http://twitter.com/btactic>* Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El medio ambiente es cosa de todos. AVIS: El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge per error, us agrairem que ho feu saber immediatament al remitent i que procediu a destruir el missatge. AVISO: El contenido de este mensaje y de sus anexos es confidencial. Si no es el destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o copiarlo sin tener la autorización correspondiente. Si han recibido este mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al remitente y que procedan a destruir el mensaje. ___ 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 -- Alex Lourie Red Hat ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Problems with F17 and ovirt 3.1
I think it's the internals of the backend. Adding host, creating all the required objects, filling the DB, creting configurations, etc. We actually are using ovirtsdk for doing that, so it's something internal in that lib. - Original Message - From: "Itamar Heim" To: "Alex Lourie" Cc: "Veli-Matti Leppänen" , users@ovirt.org, "Eli Mesika" Sent: Monday, August 20, 2012 11:17:18 AM Subject: Re: [Users] Problems with F17 and ovirt 3.1 On 08/20/2012 11:12 AM, Alex Lourie wrote: > The actual operation of creating host is taking time. I believe we've handled > its timeout before, but it is possible that our waiting period is still too > short. which part is taking the time if all rpms are already pre-installed? > > I will look into this. > > Veli, could you open a bug please? Thank you. > > - Original Message - > From: "Itamar Heim" > To: "Eli Mesika" > Cc: "Veli-Matti Leppänen" , users@ovirt.org, "Alex Lourie" > > Sent: Sunday, August 19, 2012 7:33:27 PM > Subject: Re: [Users] Problems with F17 and ovirt 3.1 > > On 08/19/2012 12:14 PM, Eli Mesika wrote: >> >> >> - Original Message - >>> From: "Veli-Matti Leppänen" >>> To: users@ovirt.org >>> Sent: Sunday, August 19, 2012 11:47:46 AM >>> Subject: Re: [Users] Problems with F17 and ovirt 3.1 >>> >>> >>> On 2012-08-19 10:48, Eli Mesika wrote: >>>> - Original Message - >>>>> From: "Veli-Matti Leppänen" >>>>> To: users@ovirt.org >>>>> Sent: Saturday, August 18, 2012 1:13:23 PM >>>>> Subject: Re: [Users] Problems with F17 and ovirt 3.1 >>>>> >>>>> Hi. >>>>> >>>>> I tried to install ovirt 3.1 on clean F17 hosts. I tried >>>>> all-in-one >>>>> and plain manager + node installation, but every time host is just >>>>> non-responsive. >>>>> >>>>> vdsmd service does not start >>>>> [root@maila ~]# service vdsmd start >>>>> Redirecting to /bin/systemctl start vdsmd.service >>>>> Job canceled. >>>>> and there is no vdsm log. >>>>> >>>>> selinux or iptables is not the issue, cause setting selinux to >>>>> permissive mode or flushing the firewall does not help. >>>>> >>>>> any ideas where to start? >>>> >>>> There was an excellent step-by-step video showing how to install >>>> all-in-one on top of f17 >>>> please follow and check again >>>> >>>> http://blog.jebpages.com/archives/up-and-running-with-ovirt-3-1-edition/ >>>> >>> >>> I followed that video. Installation times out during adding local >>> host. >>> Web admin console shows it installing and after that it goes to >>> non-responsing state. >> Hi again >> please refer to the following (taken from the same site) >> >> I’ve found that the all-in-one installer sometimes times out during the >> install process. If the script times out during the final “AIO: Adding Local >> host (This may take several minutes)” step, you can proceed to the web admin >> console to complete the process. If it times out at an earlier point, like >> waiting for the jboss-as server to start, you should run “engine-cleanup” >> and then re-run “engine-setup”. >> >>> >>>>> >>>>> /Vellu >>>>> >>>>> >>>>> --- >>>>> __ >>>>> Veli-Matti Leppänen >>>>> ve...@velhot.net >>>>> Velzi @ IRC >>>>> >>>>> ___ >>>>> 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 >> > > Eli/Alex - what are we timing out on? > 1. all-in-one rpm is supposed to require vdsm rpms so the add host > wouldn't really need to install them > 2. all-in-one is skipping the reboot > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Problems with F17 and ovirt 3.1
The actual operation of creating host is taking time. I believe we've handled its timeout before, but it is possible that our waiting period is still too short. I will look into this. Veli, could you open a bug please? Thank you. - Original Message - From: "Itamar Heim" To: "Eli Mesika" Cc: "Veli-Matti Leppänen" , users@ovirt.org, "Alex Lourie" Sent: Sunday, August 19, 2012 7:33:27 PM Subject: Re: [Users] Problems with F17 and ovirt 3.1 On 08/19/2012 12:14 PM, Eli Mesika wrote: > > > - Original Message - >> From: "Veli-Matti Leppänen" >> To: users@ovirt.org >> Sent: Sunday, August 19, 2012 11:47:46 AM >> Subject: Re: [Users] Problems with F17 and ovirt 3.1 >> >> >> On 2012-08-19 10:48, Eli Mesika wrote: >>> - Original Message - >>>> From: "Veli-Matti Leppänen" >>>> To: users@ovirt.org >>>> Sent: Saturday, August 18, 2012 1:13:23 PM >>>> Subject: Re: [Users] Problems with F17 and ovirt 3.1 >>>> >>>> Hi. >>>> >>>> I tried to install ovirt 3.1 on clean F17 hosts. I tried >>>> all-in-one >>>> and plain manager + node installation, but every time host is just >>>> non-responsive. >>>> >>>> vdsmd service does not start >>>> [root@maila ~]# service vdsmd start >>>> Redirecting to /bin/systemctl start vdsmd.service >>>> Job canceled. >>>> and there is no vdsm log. >>>> >>>> selinux or iptables is not the issue, cause setting selinux to >>>> permissive mode or flushing the firewall does not help. >>>> >>>> any ideas where to start? >>> >>> There was an excellent step-by-step video showing how to install >>> all-in-one on top of f17 >>> please follow and check again >>> >>> http://blog.jebpages.com/archives/up-and-running-with-ovirt-3-1-edition/ >>> >> >> I followed that video. Installation times out during adding local >> host. >> Web admin console shows it installing and after that it goes to >> non-responsing state. > Hi again > please refer to the following (taken from the same site) > > I’ve found that the all-in-one installer sometimes times out during the > install process. If the script times out during the final “AIO: Adding Local > host (This may take several minutes)” step, you can proceed to the web admin > console to complete the process. If it times out at an earlier point, like > waiting for the jboss-as server to start, you should run “engine-cleanup” and > then re-run “engine-setup”. > >> >>>> >>>> /Vellu >>>> >>>> >>>> --- >>>> __ >>>> Veli-Matti Leppänen >>>> ve...@velhot.net >>>> Velzi @ IRC >>>> >>>> ___ >>>> 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 > Eli/Alex - what are we timing out on? 1. all-in-one rpm is supposed to require vdsm rpms so the add host wouldn't really need to install them 2. all-in-one is skipping the reboot ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt allinone installation
Sarfaraz Ahmed, hi (I don't know which is the private name, so I use both). Thanks for using oVirt. First, for the future reference, please send such emails to users@ovirt.org maillist (CC-ed in this message). This way it may get higher exposure and other people may respond earlier. Second, the reboot of the host when using 127.0.0.1 from the web interface is the expected behaviour, as all hosts restart after the installation. The problem, of course, is that it's the same node where the manager runs. For that purpose we created AIO plugin. To try and resolve the problem you're having, please post the complete log of the setup using all in one plugin. Please attach the file instead of pasting its content for a better readability. Thanks, Alex Lourie. - Original Message - From: "sarfaraz ahmed" To: alou...@redhat.com Sent: Saturday, August 18, 2012 10:28:15 AM Subject: ovirt allinone installation Hi, I am was to setup ovirt management and host on the same machine (running Centos6.3 core i3 2330m with 8Gb ram) I tried using ovirt-engine-setup-plugin-allinone . I used the rpm available i ovirt21-dre repository http://wiki.ovirt.org/wiki/Feature/AllInOne However installation fails in the createhost() method. This is the log that i am getting in /var/log/ovirt-engine/ Also, instead of using this package .can i simply add the host in ovirtmgmt interface using localhost(127.0.0.1) ip. I tried that but it reboots the machine and after reboot .ovirt -web interface shows non operational ovirtmgmt not found. Please give me any pointers. Any inputs are welcome. Here is the log. 2012-08-18 12:17:26::ERROR::engine-setup::2367::root:: Traceback (most recent call last): File "/usr/bin/engine-setup", line 2361, in main(confFile) File "/usr/bin/engine-setup", line 2150, in main runSequences() File "/usr/bin/engine-setup", line 2096, in runSequences controller.runAllSequences() File "/usr/share/ovirt-engine/scripts/setup_controller.py", line 54, in runAllSequences sequence.run() File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 154, in run step.run() File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 60, in run function() File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line 244, in createHost raise Exception(ERROR_CREATE_LOCAL_HOST) Exception: Error: Could not install local host Thanks, Sarfaraz Ahmad Assistant Systems Engineer Tata Consultancy Services New Delhi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-setup on rhel6.2 generates error
Andrei Is it a 3.1 version you're installing? Because according to the code it's 3.1, but according to the logs it's a very early version of 3.1 release we had at the beginning of the release cycle. Please let me know. Alex. - Original Message - From: "Andrei Vakhnin" To: "Alex Lourie" Cc: "Ofer Schreiber" , users@ovirt.org, "Haim Ateya" Sent: Wednesday, August 15, 2012 6:03:48 PM Subject: Re: [Users] engine-setup on rhel6.2 generates error engine-setup --http-port=8080 --https-port=8443 --host-fqdn=`hostname -f` --auth-pass=123123 --db-pass=123123 --default-dc-type=NFS --config-nfs=yes --override-iptables=yes --org-name=NASA LaRC --nfs-mp=/mnt/nfs --iso-domain-name=`hostname -s` Welcome to oVirt Engine setup utility Warning: Weak Password. Warning: Weak Password. oVirt Engine will be installed using the following configuration: = http-port: 8080 https-port:8443 host-fqdn: dsrvr130.larc.nasa.gov auth-pass: db-pass: org-name: NASA default-dc-type: NFS nfs-mp:/mnt/nfs iso-domain-name: dsrvr130 config-nfs:yes override-iptables: yes Proceed with the configuration listed above? (yes|no): y Installing: Configuring oVirt-engine... [ DONE ] Creating CA... [ DONE ] Editing JBoss Configuration...[ ERROR ] Error while updating jboss ROOT.war directory LOGS: 2012-08-15 10:45:48::DEBUG::engine-setup::2270::root:: importing module example_plugin_000, from file example_plugin_000.py 2012-08-15 10:45:48::DEBUG::example_plugin_000::16::root:: plugin example_plugin_000 loaded 2012-08-15 10:45:48::DEBUG::common_utils::258::root:: cmd = /sbin/ip addr 2012-08-15 10:45:48::DEBUG::common_utils::263::root:: output = 1: lo: mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: usb0: mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 02:21:5e:de:32:cb brd ff:ff:ff:ff:ff:ff 3: eth0: mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:21:5e:db:b2:c8 brd ff:ff:ff:ff:ff:ff inet6 fe80::221:5eff:fedb:b2c8/64 scope link valid_lft forever preferred_lft forever 4: eth1: mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:21:5e:db:b2:ca brd ff:ff:ff:ff:ff:ff inet6 fe80::221:5eff:fedb:b2ca/64 scope link valid_lft forever preferred_lft forever 5: eth2: mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 00:15:17:c5:7c:05 brd ff:ff:ff:ff:ff:ff 6: eth3: mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 00:15:17:c5:7c:04 brd ff:ff:ff:ff:ff:ff 7: eth4: mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 00:15:17:c5:7c:07 brd ff:ff:ff:ff:ff:ff 8: eth5: mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 00:15:17:c5:7c:06 brd ff:ff:ff:ff:ff:ff 9: eth6: mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:07:43:07:57:3d brd ff:ff:ff:ff:ff:ff inet 10.4.0.15/24 brd 10.4.0.255 scope global eth6 inet6 fe80::207:43ff:fe07:573d/64 scope link valid_lft forever preferred_lft forever 10: eth7: mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:07:43:07:57:3e brd ff:ff:ff:ff:ff:ff inet6 fe80::207:43ff:fe07:573e/64 scope link valid_lft forever preferred_lft forever 11: br0: mtu 1500 qdisc noqueue state UNKNOWN link/ether 00:21:5e:db:b2:c8 brd ff:ff:ff:ff:ff:ff inet 192.168.18.174/16 brd 192.168.255.255 scope global br0 inet6 fe80::221:5eff:fedb:b2c8/64 scope link valid_lft forever preferred_lft forever 12: br1: mtu 1500 qdisc noqueue state UNKNOWN link/ether 00:21:5e:db:b2:ca brd ff:ff:ff:ff:ff:ff inet 198.119.135.86/23 brd 198.119.135.255 scope global br1 inet6 fe80::221:5eff:fedb:b2ca/64 scope link valid_lft forever preferred_lft forever 13: br2: mtu 1500 qdisc noqueue state UNKNOWN link/ether 00:07:43:07:57:3e brd ff:ff:ff:ff:ff:ff inet 10.2.0.174/16 brd 10.2.255.255 scope global br2 inet6 fe80::207:43ff:fe07:573e/64 scope link valid_lft forever preferred_lft forever 14: virbr0: mtu 1500 qdisc noqueue state UNKNOWN link/ether 52:54:00:62:06:f5 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 15: virbr0-nic: mtu 1500 qdisc noop state DOWN qlen 500 link/ether 52:54:00:62:06:f5 brd ff:ff:ff:ff:ff:ff 17: bond0: mtu 1500 qdisc noop state DOWN link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 18: bond1: mtu 1500 qdisc noop state DOWN link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 19: bond2: mtu 1500 qdis
Re: [Users] engine-setup on rhel6.2 generates error
Andrei Could you please send the complete installation log file? Thanks. - Original Message - From: "Andrei Vakhnin" To: "Haim Ateya" Cc: "Alex Lourie" , "Ofer Schreiber" , users@ovirt.org Sent: Wednesday, August 15, 2012 5:01:35 PM Subject: Re: [Users] engine-setup on rhel6.2 generates error yes /etc/ovirt-engine/web-conf.js exist. Any other ideas. I tried updating box to rhels6.3 but same issue. Thanks var host_fqdn = "$HOST_FQDN$" var http_port = "$HTTP_PORT$" var https_port = "$HTTPS_PORT$" var http_url = "http://"+host_fqdn+":"+http_port var https_url = "https://"+host_fqdn+":"+https_port On May 15, 2012, at 4:10 PM, Haim Ateya wrote: > > > - Original Message - >> From: "Andrei Vakhnin" >> To: users@ovirt.org >> Sent: Tuesday, May 15, 2012 7:27:52 PM >> Subject: [Users] engine-setup on rhel6.2 generates error >> >> I am trying to run engine-setup utility on rhels6.2 machines to >> configure ovirt-engine but get an error while starting jboss. >> (Exception: Error while updating jboss ROOT.war directory) Any ideas >> what is happening? Thanks >> >> Andrei >> >> >> oVirt Engine will be installed using the following configuration: >> = >> http-port: 80 >> https-port:443 >> host-fqdn: xx.cluster.net >> auth-pass: >> org-name: NASA LaRC >> default-dc-type: NFS >> db-remote-install: local >> db-local-pass: >> config-nfs:no >> override-iptables: no >> Proceed with the configuration listed above? (yes|no): yes >> >> Installing: >> Configuring oVirt-engine... [ DONE ] >> Creating CA... [ DONE ] >> Editing JBoss Configuration...[ ERROR ] >> Error while updating jboss ROOT.war directory >> Please check log file >> /var/log/ovirt-engine/engine-setup_2012_05_15_12_23_53.log for more >> information >> >> >> >> /var/log/ovirt-engine/engine-setup_2012_05_15_12_23_53.log: >> >> File "/usr/share/ovirt-engine/scripts/setup_controller.py", line >> 54, in runAllSequences >>sequence.run() >> File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line >> 152, in run >>step.run() >> File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 59, >> in run >>function() >> File "/usr/bin/engine-setup", line 906, in _editRootWar >>raise Exception(output_messages.ERR_EXP_UPD_ROOT_WAR) >> Exception: Error while updating jboss ROOT.war directory > > Hi Andrei, > > We usually run oVirt on Fedora machine. > Can you check if the following file exists on your machine: > > "/etc/ovirt-engine/web-conf.js" > > Alex\Ofer - any thoughts ? > >> >> >> >> ___ >> 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: [Users] New engine install on remote DB fails "uuid-ossp extension is not loaded"
Hi Ian You're right in that superuser privileges are required to make this work. But it would rarely happen that remote DB admin would give you a user with super privileges. The solution we've come up with is this: 1. Use (or tell remote DB admin to do so) the psql command to load the extension functions to template1 DB on remote DB server: psql -U postgres -d template1 -f /usr/share/pgsql/contrib/uuid-ossp.sql 2. Now, all newly created databases will include extension functions. template1 is a special DB in postgres. In fact, when you create a new DB, it is actually copied from template1 with a new name. This way, we can still work with the user that has no superuser privileges in the remote DB server. - Original Message - From: "Ian Levesque" To: "Yair Zaslavsky" Cc: users@ovirt.org Sent: Wednesday, August 15, 2012 12:30:16 AM Subject: Re: [Users] New engine install on remote DB fails "uuid-ossp extension is not loaded" > Here's what the install log tells me: > > 2012-08-14 11:56:12::INFO::engine_validators::425::root:: Successfully > created temp database on server cmcd-web. > 2012-08-14 11:56:12::INFO::engine_validators::443::root:: Checking that uuid > extension is loaded by default on the remote server > 2012-08-14 11:56:12::DEBUG::common_utils::350::root:: running sql query > 'SELECT uuid_generate_v1();' on db server: 'cmcd-web'. > 2012-08-14 11:56:12::DEBUG::common_utils::286::root:: cmd = /usr/bin/psql -h > cmcd-web -p 5432 -U ovirt -d ovirt_engine_test -c "SELECT uuid_generate_v1();" > 2012-08-14 11:56:12::DEBUG::common_utils::291::root:: output = > 2012-08-14 11:56:12::DEBUG::common_utils::292::root:: stderr = ERROR: > function uuid_generate_v1() does not exist > > So, the installer is trying to create a database "ovirt_engine_test" and > succeeding. But until you run `psql -U postgres -d -f > /usr/share/pgsql/contrib/uuid-ossp.sql`, the function uuid_generate_v1() > won't be available. Therefore, the temporary database the installer is using > to determine compatibility fails. The problem ended up being that the postgres role which ovirt is using needs to have superuser privileges. Once I granted superuser to the "ovirt" role I created, all worked well. ~irl ___ 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: [Users] Problems when install ovirt-engine from rpm
On Thu 03 May 2012 10:48:38 AM IDT, Cao,Bing Bu wrote: On 05/03/2012 03:43 PM, Alex Lourie wrote: On Thu 03 May 2012 07:30:59 AM IDT, Shu Ming wrote: On 2012-5-3 10:37, Cao,Bing Bu wrote: Hi, I want to install the ovirt-engine from rpm package. Using the guide on wiki page: http://www.ovirt.org/wiki/Installing_ovirt-engine_from_rpm But when I install the ovirt-engine #sudo yum install -y ovirt-engine reported on error: Installing : ovirt-engine- 3.0.0_0001-1.6.fc16.x86_64 1/1 Error unpacking rpm package ovirt-engine-3.0.0_0001-1.6.fc16.x86_64 error: unpacking of archive failed on file /usr/share/jboss-as/modules/org/postgresql/main/postgresql-jdbc.jar;4fa1e777: cpio: mkdir Verifying : ovirt-engine-3.0.0_0001-1.6.fc16.x86_64 1/1 Failed: ovirt-engine.x86_64 0:3.0.0_0001-1.6.fc16 Can anyone tell me what is the matter? I think two reasons are possible: 1)Your file system was full without space. 2)The package was corrupted in the installation process. Hi Please let us know which RPMs you are using. Have you built your own set? Or are you using nightly sets from ovirt.org? No.I just use 'yum install ' to setup the ovirt-engine. I tried nightly repository,it report same error. -- Alex Lourie. OK We've seen similar error before and it was fixed some time ago. We'll try to make sure that nightly includes the fix and let you know. -- Alex Lourie. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Problems when install ovirt-engine from rpm
On Thu 03 May 2012 07:30:59 AM IDT, Shu Ming wrote: On 2012-5-3 10:37, Cao,Bing Bu wrote: Hi, I want to install the ovirt-engine from rpm package. Using the guide on wiki page: http://www.ovirt.org/wiki/Installing_ovirt-engine_from_rpm But when I install the ovirt-engine #sudo yum install -y ovirt-engine reported on error: Installing : ovirt-engine- 3.0.0_0001-1.6.fc16.x86_64 1/1 Error unpacking rpm package ovirt-engine-3.0.0_0001-1.6.fc16.x86_64 error: unpacking of archive failed on file /usr/share/jboss-as/modules/org/postgresql/main/postgresql-jdbc.jar;4fa1e777: cpio: mkdir Verifying : ovirt-engine-3.0.0_0001-1.6.fc16.x86_64 1/1 Failed: ovirt-engine.x86_64 0:3.0.0_0001-1.6.fc16 Can anyone tell me what is the matter? I think two reasons are possible: 1)Your file system was full without space. 2)The package was corrupted in the installation process. Hi Please let us know which RPMs you are using. Have you built your own set? Or are you using nightly sets from ovirt.org? -- Alex Lourie. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Exception: Database creation failed
On 04/27/2012 08:10 AM, Patrick Roughan wrote: Hey, While running engine-setup i get, creating database[ERROR] Database creation failed the following is in the log file 2012-04-27 14:33:23::ERROR::engine-setup::2453::root:: Traceback (most recent call last): File "/usr/bin/engine-setup", line 2447, in main(confFile) File "/usr/bin/engine-setup", line 2269, in main runMainFunctions(conf) File "/usr/bin/engine-setup", line 2187, in runMainFunctions runFunction([_createDB, _updateVDCOptions], output_messages.INFO_CREATE_DB) File "/usr/bin/engine-setup", line 1170, in runFunction raise Exception(instance) Exception: Database creation failed when i installed from repos which install the dependences including postgresql. postgresql failed to start, so i ran restorecon -R /var service postgresql initdb systemctl start postgresql.service service postgresql start i wasnt able to login to though so i change /var/lib/pqsql/data/pg_hba.conf values to trust now postgresql is run and can login (psql -U postgres) Any ideas? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Hello Patrick This problem could mean many things. Could you please attach the complete log file? Additionally, please attach the corresponding 'engine-db-install' log file. Finally, there's another log */usr/share/ovirt-engine/dbscripts/create_db.sh.log*. Please take a look in it to see if there are any errors, and if so, paste them too in your answer. Thank you. -- Alex Lourie. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
