Not sure if you can skip doing engine-cleanup as you ask.

----- Original Message ----- > From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com&gt; > To: "Adrian Gibanel" <adrian.gibanel(a)btactic.com&gt; > Cc: "users" <users(a)ovirt.org&gt; > Sent: Monday, December 3, 2012 11:15:48 AM > Subject: Re: [Users] Testing ovirt all in one on F18 gives error on DB creation > > On Sun, Dec 2, 2012 at 3:08 AM, Adrian Gibanel wrote: > > Not sure if you can skip doing engine-cleanup as you ask. > > If engine-cleanup takes me to the starting point it is ok for me. > Or do I have to take any other manual step to clean up and start > again > after fixing the problem? > > I also found a post about problems with template0/template1 and this > change to avoid exensions totally... > but I don't know if it is applicable to my version > (ovirt-engine-setup-3.1.0-1.fc18.noarch as I wrote before): > http://gerrit.ovirt.org/#/c/8955/ > > Hopefully this change is going to come to f18 too..? Hi This change was introduced especially for f18 Patch was available from Nov 7 2012 and should resolve this problem. > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users >

On 12/03/2012 01:12 PM, Gianluca Cecchi wrote: > > Do i have to wait for official packages for f18 or can I directly apply > patches ? nightlies should have the patch afaiu.

From: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; To: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com&gt; Cc: "Juan Antonio Hernandez Fernandez" <jhernand(a)redhat.com&gt;, "users" <users(a)ovirt.org&gt; Sent: Monday, December 3, 2012 2:58:51 PM Subject: Re: [Users] Testing ovirt all in one on F18 gives error on DB creation ----- Original Message ----- > From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com&gt; > To: "Itamar Heim" <iheim(a)redhat.com&gt; > Cc: "Juan Antonio Hernandez Fernandez" <jhernand(a)redhat.com&gt;, > "users" <users(a)ovirt.org&gt; > Sent: Monday, December 3, 2012 2:56:58 PM > Subject: Re: [Users] Testing ovirt all in one on F18 gives error on > DB creation > > On Mon, Dec 3, 2012 at 1:15 PM, Itamar Heim wrote: > > On 12/03/2012 01:12 PM, Gianluca Cecchi wrote: > >> > >> Do i have to wait for official packages for f18 or can I > >> directly > >> apply > >> patches ? > > > > > > nightlies should have the patch afaiu. > > I presume I have to get them here: > http://ovirt.org/releases/nightly/rpm/Fedora/18/noarch/ > but do I need to get nightly for all related packages due to > dependencies or can be sufficient to get only > > ovirt-engine-setup-3.1.0-3.20121202.gite000dc9.fc18.noarch.rpm > > ? > And if I want to test in order to qualify final F18, would it be > better to post to fedora-test mailing list and wait for F18 > packages > or here? > > Gianluca I suspect this is due to[1]. Alon [1] http://gerrit.ovirt.org/#/c/9648/

ovirt-engine-sdk-3.2.0.2-1.fc18.noarch

From: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; To: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com&gt; Cc: "Juan Antonio Hernandez Fernandez" <jhernand(a)redhat.com&gt;, "users" <users(a)ovirt.org&gt; Sent: Tuesday, December 4, 2012 10:13:46 AM Subject: Re: [Users] Testing ovirt all in one on F18 gives error on DB creation ----- Original Message ----- > From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com&gt; > To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; > Cc: "Juan Antonio Hernandez Fernandez" <jhernand(a)redhat.com&gt;, > "users" <users(a)ovirt.org&gt; > Sent: Tuesday, December 4, 2012 9:39:05 AM > Subject: Re: [Users] Testing ovirt all in one on F18 gives error on > DB creation > > Is there a way to "enable" nightly repo for f18 or do I have to > manually download and install/update? > I tried downloading manually and installed: > [g.cecchi@f18aio ~]$ rpm -qa | egrep "ovirt|vdsm|otopi" > ovirt-host-deploy-java-0.0.0-0.0.master.20121202.git17db8cd.fc18.noarch > ovirt-log-collector-3.1.0-1.fc18.noarch > vdsm-4.10.2-0.57.gite8f3848.fc18.x86_64 > ovirt-engine-sdk-3.2.0.5-1.20121202.gitc0ab704.fc18.noarch > ovirt-engine-setup-3.1.0-3.20121202.gite000dc9.fc18.noarch > ovirt-engine-webadmin-portal-3.1.0-3.20121202.gite000dc9.fc18.noarch > ovirt-engine-cli-3.2.0.7-1.20121202.gitf43fd5c.fc18.noarch > otopi-java-0.0.0-0.0.master.20121202.gitedc19ec.fc18.noarch > vdsm-cli-4.10.2-0.57.gite8f3848.fc18.noarch > ovirt-engine-restapi-3.1.0-3.20121202.gite000dc9.fc18.noarch > ovirt-engine-notification-service-3.1.0-3.20121202.gite000dc9.fc18.noarch > ovirt-image-uploader-3.1.0-1.fc18.noarch > ovirt-engine-userportal-3.1.0-3.20121202.gite000dc9.fc18.noarch > ovirt-engine-3.1.0-3.20121202.gite000dc9.fc18.noarch > otopi-0.0.0-0.0.master.20121202.gitedc19ec.fc18.noarch > vdsm-bootstrap-4.10.0-11.fc18.noarch > vdsm-python-4.10.2-0.57.gite8f3848.fc18.x86_64 > ovirt-host-deploy-0.0.0-0.0.master.20121202.git17db8cd.fc18.noarch > ovirt-engine-dbscripts-3.1.0-3.20121202.gite000dc9.fc18.noarch > ovirt-engine-setup-plugin-allinone-3.1.0-3.20121202.gite000dc9.fc18.noarch > vdsm-xmlrpc-4.10.2-0.57.gite8f3848.fc18.noarch > ovirt-engine-config-3.1.0-3.20121202.gite000dc9.fc18.noarch > ovirt-engine-backend-3.1.0-3.20121202.gite000dc9.fc18.noarch > ovirt-host-deploy-offline-0.0.0-0.0.master.20121202.git17db8cd.fc18.noarch > ovirt-iso-uploader-3.1.0-1.fc18.noarch > ovirt-engine-tools-common-3.1.0-3.20121202.gite000dc9.fc18.noarch > ovirt-engine-genericapi-3.1.0-3.20121202.gite000dc9.fc18.noarch > > > Now I get: > 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... [ > ERROR ] > Failed updating configuration parameter: Error: failed updating > configuration field CAEngineKey to > /etc/pki/ovirt-engine/private/ca.pem > Please check log file > /var/log/ovirt-engine/engine-setup_2012_12_04_08_34_45.log for more > information > > and in that log file: > 2012-12-04 08:37:04::DEBUG::engine-setup::1786::root:: *** The > following params were used as user input: > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: > override-httpd-config: yes > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: http-port: > 80 > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: https-port: > 443 > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: mac-range: > 00:1A:4A:A8:7A:00-00:1A:4A:A8:7A:FF > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: host-fqdn: > f18aio.localdomain.local > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: auth-pass: > ******** > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: org-name: > localdomain.local > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: > default-dc-type: NFS > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: > db-remote-install: local > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: db-host: > localhost > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: > db-local-pass: > ******** > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: nfs-mp: /ISO > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: > iso-domain-name: ISO_DOMAIN > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: config-nfs: > yes > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: > override-iptables: yes > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: > config-allinone: yes > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: > storage-path: > /DATA > 2012-12-04 08:37:04::DEBUG::engine-setup::1791::root:: > superuser-pass: ******** > 2012-12-04 08:37:04::ERROR::engine-setup::2195::root:: Traceback > (most > recent call last): > File "/bin/engine-setup", line 2189, in <module> > main(confFile) > File "/bin/engine-setup", line 1972, in main > runSequences() > File "/bin/engine-setup", line 1906, 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 "/bin/engine-setup", line 1113, in _updateVDCOptions > raise > Exception(output_messages.ERR_FAILED_UPD_VDC_OPTIONS%(sys.exc_info()[1])) > Exception: Failed updating configuration parameter: Error: failed > updating configuration field CAEngineKey to > /etc/pki/ovirt-engine/private/ca.pem > > Thanks for any other inside help, > Gianluca > You can configure http://resources.ovirt.org/releases/nightly/rpm/Fedora/18/ as a repository within your yum.repos.d. Nightly snapshots cannot be used as it was recently broken due to[1]. I also wait for a fix. Thanks! Alon. [1] http://gerrit.ovirt.org/#/c/9648/

From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com&gt; To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; Cc: "Juan Antonio Hernandez Fernandez" <jhernand(a)redhat.com&gt;, "users" <users(a)ovirt.org&gt; Sent: Tuesday, December 4, 2012 5:10:12 PM Subject: Re: [Users] Testing ovirt all in one on F18 gives error on DB creation On Tue, Dec 4, 2012 at 1:35 PM, Alon Bar-Lev wrote: >> >> You can configure >> http://resources.ovirt.org/releases/nightly/rpm/Fedora/18/ as a >> repository within your yum.repos.d. >> >> Nightly snapshots cannot be used as it was recently broken due >> to[1]. > > This change was reverted, you can use the next nightly. > > Alon Ok, successfully configured and tested nightly repo. Thanks I will try rerun engine-setup after next nightly build. Initially I tried to keep it signed and with same fedora key file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch but it said one of the vdsm packages was not signed, so for the moment I configured the repo as enabled=0 gpgcheck=0 and using --enablerepo parameter when I need it BTW: how to completely clean the configuration? I can manually run engine-cleanup manually drop db as postgres user engine-cleanup again

But if I rerun engine-setup I get: In order to proceed the installer must stop the ovirt-engine service Would you like to stop the ovirt-engine service? (yes|no): yes oVirt Engine uses httpd to proxy requests to the application server. It looks like the httpd installed locally is being actively used. The installer can override current configuration . Alternatively you can use JBoss directly (on ports higher than 1024) Do you wish to override current httpd configuration and restart the service? ['yes'| 'no'] [yes] :

Which other files can I delete so that the setup thinks it is a "new" system?

From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com&gt; To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; Cc: "Juan Antonio Hernandez Fernandez" <jhernand(a)redhat.com&gt;, "users" <users(a)ovirt.org&gt;, "Alex Lourie" <alourie(a)redhat.com&gt;, "Ohad Basan" <obasan(a)redhat.com&gt; Sent: Tuesday, December 4, 2012 6:04:41 PM Subject: Re: [Users] Testing ovirt all in one on F18 gives error on DB creation Probably the problems I have in cleanup are all related to the DB problems during engine-setup..? In fact this is what I get: [root@f18aio ~]# engine-cleanup WARNING: Executing oVirt Engine cleanup utility. This utility will wipe all existing data including configuration settings, certificates and database. In addition, all existing DB connections will be closed. Would you like to proceed? (yes|no): yes Stopping ovirt-engine service... [ DONE ] Removing Database... [ ERROR ] Removing CA... [ DONE ] Stopping engine-notifierd service... [ DONE ] Cleanup finished with errors, please see log file Error: failed to clear active DB connections Cleanup log available at /var/log/ovirt-engine/engine-cleanup_2012_12_04_08_32_37.log So I manage to drop the "engine" database from psql prompt and then run the cleanup again: [root@f18aio ~]# engine-cleanup WARNING: Executing oVirt Engine cleanup utility. This utility will wipe all existing data including configuration settings, certificates and database. In addition, all existing DB connections will be closed. Would you like to proceed? (yes|no): yes Stopping ovirt-engine service... [ DONE ] Removing CA... [ DONE ] Stopping engine-notifierd service... [ DONE ] Cleanup finished successfully! Cleanup log available at /var/log/ovirt-engine/engine-cleanup_2012_12_04_08_33_53.log But at next engine-setup I get the errors I sent the previous mail. I'll retry with next nightly build. The important thing is the confirmation that "engin-cleanup" has to be sufficient. I'll deploy a new f18 and test. Gianluca

From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com&gt; To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; Cc: "Juan Antonio Hernandez Fernandez" <jhernand(a)redhat.com&gt;, "users" <users(a)ovirt.org&gt;, "Alex Lourie" <alourie(a)redhat.com&gt;, "Ohad Basan" <obasan(a)redhat.com&gt; Sent: Wednesday, December 5, 2012 4:56:44 PM Subject: Re: [Users] Testing ovirt all in one on F18 gives error on DB creation On Tue, Dec 4, 2012 at 5:06 PM, Alon Bar-Lev wrote: Installed nightly build (rebased on 3.2) So now I managed to run - engine-setup It detected previous install so I exited Welcome to oVirt Engine setup utility WARNING: oVirt Engine setup has already been run on this host. To remove all configuration and reset oVirt Engine please run engine-cleanup. Please be advised that executing engine-setup without cleanup is not supported. Would you like to proceed? (yes|no): no Installation stopped, Goodbye. - engine-cleanup It gave errore in relation to the db where it didn't find some objects (sue to cration failur in 3.1 I presume...) WARNING: Executing oVirt Engine cleanup utility. This utility will wipe all existing data including configuration settings, certificates and database. In addition, all existing DB connections will be closed. Would you like to proceed? (yes|no): yes Stopping ovirt-engine service... [ DONE ] Removing Database... [ ERROR ] Removing CA... [ DONE ] Stopping engine-notifierd service... [DONE ] Cleanup finished with errors, please see log file Error: failed to clear active DB connections Cleanup log available at /var/log/ovirt-engine/engine-cleanup_2012_12_05_14_56_48.log from this file: 2012-12-05 14:56:54::DEBUG::common_utils::390::root:: Executing command --> '/usr/bin/psql -U postgres -c SELECT pg_terminate_ backend(procpid) FROM pg_stat_activity WHERE datname = 'engine'' 2012-12-05 14:56:54::DEBUG::common_utils::428::root:: output = 2012-12-05 14:56:54::DEBUG::common_utils::429::root:: stderr = ERROR: column "procpid" does not exist LINE 1: SELECT pg_terminate_backend(procpid) FROM pg_stat_activity W... ^ 2012-12-05 14:56:54::DEBUG::common_utils::430::root:: retcode = 1 2012-12-05 14:56:54::ERROR::engine-cleanup::408::root:: Traceback (most recent call last): File "/bin/engine-cleanup", line 402, in runFunc funcName() File "/bin/engine-cleanup", line 308, in drop utils.clearDbConnections(basedefs.DB_NAME) File "/usr/share/ovirt-engine/scripts/common_utils.py", line 1004, in clearDbConnections execCmd(cmdList=cmd, failOnError=True, msg=output_messages.ERR_DB_CONNECTIONS_CLEAR, envDict=getPgPassEnv()) File "/usr/share/ovirt-engine/scripts/common_utils.py", line 433, in execCmd raise Exception(msg) Exception: Error: failed to clear active DB connections - Manually dropped "engine" db - engine-cleanup again It completed successfully: WARNING: Executing oVirt Engine cleanup utility. This utility will wipe all existing data including configuration settings, certificates and database. In addition, all existing DB connections will be closed. Would you like to proceed? (yes|no): yes Stopping ovirt-engine service... [DONE ] Removing CA... [ DONE ] Stopping engine-notifierd service... [DONE ] Cleanup finished successfully! Cleanup log available at /var/log/ovirt-engine/engine-cleanup_2012_12_05_14_58_07.log - engine-setup Now it gives error at NFS point 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... [ ERROR ] Failed to configure NFS share on this host Please check log file /var/log/ovirt-engine/engine-setup_2012_12_05_14_58_43.log for more information In logfile 2012-12-05 15:00:28::DEBUG::common_utils::429::root:: stderr = Redirecting to /bin/systemctl start rpcbind.service 2012-12-05 15:00:28::DEBUG::common_utils::430::root:: retcode = 0 2012-12-05 15:00:28::DEBUG::common_utils::390::root:: Executing command --> '/sbin/chkconfig nfs-server on' 2012-12-05 15:00:28::DEBUG::common_utils::428::root:: output = 2012-12-05 15:00:28::DEBUG::common_utils::429::root:: stderr = Note: Forwarding request to 'systemctl enable nfs-server.servic e'. ln -s '/usr/lib/systemd/system/nfs-server.service' '/etc/systemd/system/multi-user.target.wants/nfs-server.service' 2012-12-05 15:00:28::DEBUG::common_utils::430::root:: retcode = 0 2012-12-05 15:00:28::DEBUG::common_utils::1163::root:: stopping nfs-server 2012-12-05 15:00:28::DEBUG::common_utils::1200::root:: executing action nfs-server on service stop 2012-12-05 15:00:28::DEBUG::common_utils::390::root:: Executing command --> '/sbin/service nfs-server stop' 2012-12-05 15:00:28::DEBUG::common_utils::428::root:: output = 2012-12-05 15:00:28::DEBUG::common_utils::429::root:: stderr = Redirecting to /bin/systemctl stop nfs-server.service 2012-12-05 15:00:28::DEBUG::common_utils::430::root:: retcode = 0 2012-12-05 15:00:28::DEBUG::common_utils::1153::root:: starting nfs-server 2012-12-05 15:00:28::DEBUG::common_utils::1200::root:: executing action nfs-server on service start 2012-12-05 15:00:28::DEBUG::common_utils::390::root:: Executing command --> '/sbin/service nfs-server start' 2012-12-05 15:00:28::DEBUG::common_utils::428::root:: output = 2012-12-05 15:00:28::DEBUG::common_utils::429::root:: stderr = Redirecting to /bin/systemctl start nfs-server.service A dependency job for nfs-server.service failed. See 'journalctl -n' for details. 2012-12-05 15:00:28::DEBUG::common_utils::430::root:: retcode = 1 2012-12-05 15:00:28::ERROR::engine-setup::1674::root:: Traceback (most recent call last): File "/bin/engine-setup", line 1672, in _startNfsServices srv.start(True) File "/usr/share/ovirt-engine/scripts/common_utils.py", line 1158, in start raise Exception(output_messages.ERR_FAILED_START_SERVICE % self.name) Exception: Error: Can't start the nfs-server service 2012-12-05 15:00:28::ERROR::engine-setup::1612::root:: Traceback (most recent call last): File "/bin/engine-setup", line 1598, in _configNfsShare _startNfsServices() File "/bin/engine-setup", line 1675, in _startNfsServices raise Exception(output_messages.ERR_FAILED_TO_START_NFS_SERVICE) Exception: Failed to start the NFS services # journalctl -n -- Logs begin at Wed, 2012-12-05 12:12:16 CET, end at Wed, 2012-12-05 15:01:02 CET. -- Dec 05 15:00:29 f18aio.localdomain.local kernel: SELinux: initialized (dev nfsd, type nfsd), uses genfs_contexts Dec 05 15:00:29 f18aio.localdomain.local kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory Dec 05 15:00:29 f18aio.localdomain.local kernel: NFSD: starting 90-second grace period Dec 05 15:01:01 f18aio.localdomain.local CROND[14412]: (root) CMD (run-parts /etc/cron.hourly) Dec 05 15:01:01 f18aio.localdomain.local run-parts(/etc/cron.hourly)[14415]: starting 0anacron Dec 05 15:01:01 f18aio.localdomain.local run-parts(/etc/cron.hourly)[14421]: finished 0anacron Dec 05 15:01:01 f18aio.localdomain.local run-parts(/etc/cron.hourly)[14423]: starting mcelog.cron Dec 05 15:01:01 f18aio.localdomain.local run-parts(/etc/cron.hourly)[14427]: finished mcelog.cron Dec 05 15:01:02 f18aio.localdomain.local run-parts(/etc/cron.hourly)[14429]: starting vdsm-logrotate Dec 05 15:01:02 f18aio.localdomain.local run-parts(/etc/cron.hourly)[14435]: finished vdsm-logrotate # systemctl status nfs-server.service nfs-server.service - NFS Server Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled) Active: active (exited) since Wed, 2012-12-05 15:00:29 CET; 54min ago Process: 14396 ExecStartPost=/usr/lib/nfs-utils/scripts/nfs-server.postconfig (code=exited, status=0/SUCCESS) Process: 14377 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS $RPCNFSDCOUNT (code=exited, status=0/SUCCESS) Process: 14372 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS) Process: 14366 ExecStartPre=/usr/lib/nfs-utils/scripts/nfs-server.preconfig (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/nfs-server.service Dec 05 15:00:28 f18aio.localdomain.local systemd[1]: Starting NFS Server... Dec 05 15:00:28 f18aio.localdomain.local systemd[1]: Dependency failed for NFS Server. In /var/log/messages: Dec 5 15:00:28 f18aio systemd[1]: Starting NFS Server... Dec 5 15:00:28 f18aio mount[14364]: mount: unknown filesystem type 'rpc_pipefs' Dec 5 15:00:28 f18aio systemd[1]: var-lib-nfs-rpc_pipefs.mount mount process exited, code=exited status=32 Dec 5 15:00:28 f18aio systemd[1]: Failed to mount RPC Pipe File System. Dec 5 15:00:28 f18aio systemd[1]: Dependency failed for NFS Server. Dec 5 15:00:28 f18aio systemd[1]: Dependency failed for NFS Remote Quota Server. Dec 5 15:00:28 f18aio systemd[1]: Job nfs-rquotad.service/start failed with result 'dependency'. Dec 5 15:00:28 f18aio systemd[1]: Dependency failed for NFS Mount Daemon. Dec 5 15:00:28 f18aio systemd[1]: Job nfs-mountd.service/start failed with result 'dependency'. Dec 5 15:00:28 f18aio systemd[1]: Dependency failed for NFSv4 ID-name mapping daemon. Dec 5 15:00:28 f18aio systemd[1]: Job nfs-idmap.service/start failed with result 'dependency'. Dec 5 15:00:28 f18aio systemd[1]: Job nfs-server.service/start failed with result 'dependency'. Dec 5 15:00:28 f18aio systemd[1]: Unit var-lib-nfs-rpc_pipefs.mount entered failed state Dec 5 15:00:28 f18aio kernel: RPC: Registered named UNIX socket transport module. Dec 5 15:00:28 f18aio kernel: RPC: Registered udp transport module. Dec 5 15:00:28 f18aio kernel: RPC: Registered tcp transport module. Dec 5 15:00:28 f18aio kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Dec 5 15:00:28 f18aio kernel: Installing knfsd (copyright (C) 1996 okir(a)monad.swb.de). Dec 5 15:00:29 f18aio systemd[1]: Mounted RPC Pipe File System. Dec 5 15:00:28 f18aio kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory Dec 5 15:00:28 f18aio kernel: NFSD: starting 90-second grace period what to do? Thanks, Gianluca

From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com&gt; To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; Cc: "Juan Antonio Hernandez Fernandez" <jhernand(a)redhat.com&gt;, "users" <users(a)ovirt.org&gt;, "Alex Lourie" <alourie(a)redhat.com&gt;, "Ohad Basan" <obasan(a)redhat.com&gt; Sent: Wednesday, December 5, 2012 6:42:17 PM Subject: Re: [Users] Testing ovirt all in one on F18 gives error on DB creation On Wed, Dec 5, 2012 at 5:35 PM, Alon Bar-Lev <alonbl(a)redhat.com&gt; wrote: > Is there any special reason why you are using fedora 18 and not > fedora 17? To give feedback for final f18. But if it is useless at this moment because f18 is going to exit with 3.1 or without oVirt at all I can stop testing, no problem...

As I also asked on fedora test mailing list, it would be good to know if final f18 shipped ovirt is going to be based on 3.1 or 3.2 and in case update its feature list page for f18...

Il giorno 05/dic/2012 17:46, "Alon Bar-Lev" <alonbl(a)redhat.com <mailto:alonbl@redhat.com>> ha scritto: ----- Original Message ----- > From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com <mailto:gianluca.cecchi@gmail.com>> > To: "Alon Bar-Lev" <alonbl(a)redhat.com <mailto:alonbl@redhat.com>> > Cc: "Juan Antonio Hernandez Fernandez" <jhernand(a)redhat.com <mailto:jhernand@redhat.com>>, "users" <users(a)ovirt.org <mailto:users@ovirt.org>>, "Alex Lourie" > <alourie(a)redhat.com <mailto:alourie@redhat.com>>, "Ohad Basan" <obasan(a)redhat.com <mailto:obasan@redhat.com>> > Sent: Wednesday, December 5, 2012 6:42:17 PM > Subject: Re: [Users] Testing ovirt all in one on F18 gives error on DB creation > > On Wed, Dec 5, 2012 at 5:35 PM, Alon Bar-Lev <alonbl(a)redhat.com <mailto:alonbl@redhat.com>> > wrote: > > Is there any special reason why you are using fedora 18 and not > > fedora 17? > > To give feedback for final f18. > But if it is useless at this moment because f18 is going to exit with > 3.1 or without oVirt at all I can stop testing, no problem... > Just wanted to make sure you need f18... :) It is important to get feedback, please keep testing. Ohad, you have installed engine on f18 already, right? Alon. Alon _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Ok. So i should stick fedora 18 packages for that. But right now there is the failure oin aio setup, that was my initial mail in this thread... Is a new update planned for f18 rpms then? Or aio setup nitric for final f18?

On Dec 5, 2012 6:42 PM, "Juan Hernandez" <jhernand(a)redhat.com <mailto:jhernand@redhat.com>> wrote: On 12/05/2012 06:22 PM, Gianluca Cecchi wrote: > As I also asked on fedora test mailing list, it would be good to know if > final f18 shipped ovirt is going to be based on 3.1 or 3.2 and in case > update its feature list page for f18... It will be 3.1 as that is what was approved as a feature for Fedora 18 by FESCO. However, once Fedora 18 is released, we could work on upgrading to 3.2, and if that is accepted we can then make the update in Fedora 18 instead of waiting for Fedora 19. > > Il giorno 05/dic/2012 17:46, "Alon Bar-Lev" <alonbl(a)redhat.com <mailto:alonbl@redhat.com> > <mailto:alonbl@redhat.com <mailto:alonbl@redhat.com>>> ha scritto: > > > > ----- Original Message ----- > > From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com <mailto:gianluca.cecchi@gmail.com> > <mailto:gianluca.cecchi@gmail.com <mailto:gianluca.cecchi@gmail.com>>> > > To: "Alon Bar-Lev" <alonbl(a)redhat.com <mailto:alonbl@redhat.com> <mailto:alonbl@redhat.com <mailto:alonbl@redhat.com>>> > > Cc: "Juan Antonio Hernandez Fernandez" <jhernand(a)redhat.com <mailto:jhernand@redhat.com> > <mailto:jhernand@redhat.com <mailto:jhernand@redhat.com>>>, "users" <users(a)ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>>, "Alex Lourie" > > <alourie(a)redhat.com <mailto:alourie@redhat.com> <mailto:alourie@redhat.com <mailto:alourie@redhat.com>>>, "Ohad Basan" > <obasan(a)redhat.com <mailto:obasan@redhat.com> <mailto:obasan@redhat.com <mailto:obasan@redhat.com>>> > > Sent: Wednesday, December 5, 2012 6:42:17 PM > > Subject: Re: [Users] Testing ovirt all in one on F18 gives error > on DB creation > > > > On Wed, Dec 5, 2012 at 5:35 PM, Alon Bar-Lev <alonbl(a)redhat.com <mailto:alonbl@redhat.com> > <mailto:alonbl@redhat.com <mailto:alonbl@redhat.com>>> > > wrote: > > > Is there any special reason why you are using fedora 18 and not > > > fedora 17? > > > > To give feedback for final f18. > > But if it is useless at this moment because f18 is going to exit with > > 3.1 or without oVirt at all I can stop testing, no problem... > > > > Just wanted to make sure you need f18... :) > It is important to get feedback, please keep testing. > > Ohad, you have installed engine on f18 already, right? > > Alon. > > Alon > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org <mailto:Users@ovirt.org> > http://lists.ovirt.org/mailman/listinfo/users > -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

In the mean time my tests on f18 with nightly build (ovirt-engine-3.2.0-1.20121204.git5d79c41.fc18.noarch) went ahead ... PREFACE: this is a f18 vm in a fedora 17 host, where I put this in xml <cpu mode='custom' match='exact'> <model fallback='allow'>SandyBridge</model> <vendor>Intel</vendor> <feature policy='require' name='osxsave'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='xtpr'/> <feature policy='require' name='tm2'/> <feature policy='require' name='est'/> <feature policy='require' name='smx'/> <feature policy='require' name='vmx'/> <feature policy='require' name='ds_cpl'/> <feature policy='require' name='monitor'/> <feature policy='require' name='dtes64'/> <feature policy='require' name='pbe'/> <feature policy='require' name='tm'/> <feature policy='require' name='ht'/> <feature policy='require' name='ss'/> <feature policy='require' name='acpi'/> <feature policy='require' name='ds'/> <feature policy='require' name='vme'/> <feature policy='disable' name='aes'/> </cpu> It goes through in installation, but now it fails at instaling the host 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 (iptables)... [ 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: Timed out while waiting for host to start Please check log file /var/log/ovirt-engine/engine-setup_2012_12_05_16_57_11.log for more information NOTE: In log file I found: 1) problem with loading files to iso domain 2012-12-05 16:59:51::ERROR::engine-setup::1694::root:: Traceback (most recent call last): File "/usr/bin/engine-setup", line 1691, in _loadFilesToIsoDomain utils.copyFile(filename, targetPath, basedefs.CONST_VDSM_UID, basedefs.CONST_KVM_GID) File "/usr/share/ovirt-engine/scripts/common_utils.py", line 653, in copyFile shutil.copy2(fileSrc, destination) File "/usr/lib64/python2.7/shutil.py", line 128, in copy2 copyfile(src, dst) File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile with open(src, 'rb') as fsrc: IOError: [Errno 2] No such file or directory: '/usr/share/virtio-win/virtio-win.vfd' 2012-12-05 16:59:51::ERROR::engine-setup::1695::root:: Failed to copy files to iso domain ---> probably to include some deendency when you install packages? 2) Install of host fails 2012-12-05 17:00:24::DEBUG::all_in_one_100::279::root:: current host status is: installing 2012-12-05 17:00:24::DEBUG::all_in_one_100::290::root:: Traceback (most recent call last): File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line 287, in isHostUp raise Exception(INFO_CREATE_HOST_WAITING_UP) Exception: Waiting for the host to start 2012-12-05 17:00:29::DEBUG::all_in_one_100::276::root:: Waiting for host to become operational 2012-12-05 17:00:29::DEBUG::all_in_one_100::279::root:: current host status is: installing 2012-12-05 17:00:29::DEBUG::all_in_one_100::290::root:: Traceback (most recent call last): File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line 287, in isHostUp raise Exception(INFO_CREATE_HOST_WAITING_UP) Exception: Waiting for the host to start 2012-12-05 17:01:15::DEBUG::all_in_one_100::276::root:: Waiting for host to become operational 2012-12-05 17:01:15::DEBUG::all_in_one_100::279::root:: current host status is: installing 2012-12-05 17:01:15::DEBUG::all_in_one_100::290::root:: Traceback (most recent call last): File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line 287, in isHostUp raise Exception(INFO_CREATE_HOST_WAITING_UP) Exception: Waiting for the host to start 2012-12-05 17:01:20::DEBUG::all_in_one_100::276::root:: Waiting for host to become operational 2012-12-05 17:01:20::DEBUG::all_in_one_100::279::root:: current host status is: install_failed 2012-12-05 17:01:20::DEBUG::all_in_one_100::290::root:: Traceback (most recent call last): 3) Installation failure probably caused by tuned-adm error under /var/log/ovirt-engine/host-deploy ovirt-20121205170118-f18aio.localdomain.local.log 2012-12-05 17:01:18 DEBUG otopi.plugins.ovirt_host_deploy.tune.tuned plugin.execute:393 execute-output: ('/sbin/tuned-adm', 'profile', 'vir tual-host') stderr: 2012-12-05 17:00:53,193 ERROR dbus.proxies: Introspect error on :1.43:/Tuned: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ERROR:dbus.proxies:Introspect error on :1.43:/Tuned: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. DBus call to Tuned daemon failed (org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.). the same if I run from command line: /sbin/tuned-adm profile virtual-host NOTE: in messages I have 2012-12-05 17:00:53,207 INFO tuned.profiles.loader: loading profile: virtual-host 2012-12-05 17:00:53,212 INFO tuned.daemon.daemon: starting tuning 2012-12-05 17:00:53,220 INFO tuned.units.manager: creating unit 'sysctl' (devices: sysctl) 2012-12-05 17:00:53,243 INFO tuned.units.manager: skipping unit 'mounts', no devices available 2012-12-05 17:00:53,244 INFO tuned.units.manager: skipping unit 'disk', no devices available 2012-12-05 17:00:53,246 INFO tuned.units.manager: creating unit 'vm' (devices: vm) 2012-12-05 17:00:53,246 INFO tuned.units.manager: creating unit 'cpu' (devices: 0) 2012-12-05 17:00:53,289 ERROR tuned.utils.commands: Executing cpupower error: 2012-12-05 17:00:53,289 INFO tuned.plugins.plugin_cpu: setting governor 'performance' on cpu '0' 2012-12-05 17:00:53,300 ERROR tuned.utils.commands: Executing cpupower error: 2012-12-05 17:01:03,301 INFO tuned.plugins.plugin_cpu: new cpu latency 100 --> Possibly tuned-adm not supported in a guest? Skippable? 4) I can open the weadmin portal and see the local_cluser configuration Trying to re-install the host from web interface gives the same error In messages during install of host I find this: Dec 6 17:04:07 f18aio setroubleshoot: SELinux is preventing /usr/bin/lsblk from search access on the directory udev. For complete SELinux messages. run sealert -l 5f88c680-1876-4bd5-b800-767cba201f73 don't know if it can be related, but I noticed that in output of "sealert -l" it says to run audit2allow to create policy: " If you believe that lsblk should be allowed search access on the udev directory by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep lsblk /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp " and audit2allow was not present on my system. In f17 it is in policycoreutils-python (that I have in my f18 too) In f18 it is instead in policycoreutils-devel So in case the audit2allow command could be of any importance during installation of oVirt, policycoreutils-devel has to be a dependency. Gianluca

From: "Jason Brooks" <jbrooks(a)redhat.com&gt; To: "users" <users(a)ovirt.org&gt; Sent: Wednesday, December 12, 2012 11:39:44 PM Subject: Re: [Users] Testing ovirt all in one on F18 gives error on DB creation > > > > 3) Installation failure probably caused by tuned-adm error > > > > under /var/log/ovirt-engine/host-deploy > > > > ovirt-20121205170118-f18aio.localdomain.local.log > > > > 2012-12-05 17:01:18 DEBUG > > otopi.plugins.ovirt_host_deploy.tune.tuned > > plugin.execute:393 execute-output: ('/sbin/tuned-adm', 'profile', > > 'vir > > tual-host') stderr: > > 2012-12-05 17:00:53,193 ERROR dbus.proxies: Introspect error > > on > > :1.43:/Tuned: dbus.exceptions.DBusException: > > org.freedesktop.DBus.Error.NoReply: Did not receive a reply. > > Possible > > causes include: the remote application did not send a reply, the > > message bus security policy blocked the reply, the reply timeout > > expired, or the network connection was broken. > > ERROR:dbus.proxies:Introspect error on :1.43:/Tuned: > > dbus.exceptions.DBusException: > > org.freedesktop.DBus.Error.NoReply: > > Did > > not receive a reply. Possible causes include: the remote > > application > > did not send a reply, the message bus security policy blocked the > > reply, the reply timeout expired, or the network connection was > > broken. > > DBus call to Tuned daemon failed > > (org.freedesktop.DBus.Error.NoReply: > > Did not receive a reply. Possible causes include: the remote > > application did not send a reply, the message bus security policy > > blocked the reply, the reply timeout expired, or the network > > connection was broken.). > > > > the same if I run from command line: > > /sbin/tuned-adm profile virtual-host I was having this same issue w/ F18 w/ all updates applied and ovirt 3.2 from the new 3.2-alpha repo. I did a "yum downgrade tuned" and the install completed successfully. Now I just have to figure out why my host is non-operational... Jason

> > > > the same if I run from command line: > > > > /sbin/tuned-adm profile virtual-host > > > > > > I was having this same issue w/ F18 w/ all updates applied and > > ovirt > > 3.2 from the new 3.2-alpha repo. I did a "yum downgrade tuned" and > > the install completed successfully. > > > > Now I just have to figure out why my host is non-operational... > > > > Jason > > I suggest you perform host deployment again. Thanks, that worked. The ovirtmgmt bridge wasn't created the first time around, now I'm up.

From host:

Not sure if you can skip doing engine-cleanup as you ask.=20