oVirt 3.2 on fedora 18
Juan Hernandez
jhernand at redhat.com
Mon Nov 5 16:28:43 UTC 2012
On 11/05/2012 04:08 PM, Ohad Basan wrote:
>
>
>
>
> ----- Original Message -----
>> From: "Ohad Basan" <obasan at redhat.com>
>> To: "Eli Mesika" <emesika at redhat.com>, "Juan Hernandez" <jhernand at redhat.com>, "Federico Simoncelli"
>> <fsimonce at redhat.com>, "Alon Bar-Lev" <alonbl at redhat.com>
>> Cc: "Itamar Heim" <iheim at redhat.com>, arch at ovirt.org, "Moran Goldboim" <mgoldboi at redhat.com>
>> Sent: Sunday, November 4, 2012 6:59:53 PM
>> Subject: Re: oVirt 3.2 on fedora 18
>>
>> Here is a progress upgrade of engine+upgrade from f17 to f18
>>
>> F17 to F18 upgrade engine
>>
>> -installation -
>>
>> upgrade to F18 with --exclude=ovirt* and --exclude=vdsm* or
>> otherwise it won't work.
>> upgrade to f18 using the following guide
>> https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum?rd=YumUpgradeFaq#Fedora_17_-.3E_Fedora_18
>> httpd won't start at the beginning. it is a must to correctly
>> merge ssl.conf and ssl.conf.rpmnew. NOTE: SSLMutex parameter has
>> to be removed or apache won't start.
>> Postgresql won't start. db structure has to be converted to the
>> structure of the new version of the pg. we'll have to see what
>> is the best way to handle it. basically
>> http://www.postgresql.org/docs/current/static/pgupgrade.html is
>> required but it can't be run since the pg server can't be
>> started. might have to dump the db prior the dist upgrade though
>> I'm not sure it's the best way to take care of it.
> walkaround for db upgrade:
> I didn't get pg_upgrade to work so the steps are as following.
>
> 1. pg_dumpall to a file.
> 2. drop database engine;
> 3. upgrade to fedora18
> 4. move psql data library. /var/lib/pgsql to another location (backup)
> 5. run postgresql-setup initdb
> 6. make sure that pg_hba.conf is configured correctly and restart the db.
> 7. restore the backed up dump file. psql -f <Filename> -U postgres.
> 8. restart engine
>
> despite the fact that the database is in place with the correct owner. engine still has issues accessing the db.
> engine.log is attached. plz see the end of the file
>
> 2012-11-05 16:40:50,974 ERROR [org.ovirt.engine.core.bll.Backend] (MSC service thread 1-1) Error in getting DB connection. The database is inaccessible. Original exception is: DataAccessResourceFailureException: Error retreiving database metadata; nested exception is org.springframework.jdbc.support.MetaDataAccessException: Could not get Connection for extracting meta data; nested exception is org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/ENGINEDataSource
> 2012-11-05 16:40:56,329 INFO [org.ovirt.engine.core.bll.Backend] (MSC service thread 1-1) Start time: 11/5/12 4:40 PM
> 2012-11-05 16:40:56,498 WARN [org.ovirt.engine.core.utils.ConfigUtilsBase] (MSC service thread 1-1) Could not find enum value for option: CbcCheckOnVdsChange
> 2012-11-05 16:40:56,509 WARN [org.ovirt.engine.core.utils.ConfigUtilsBase] (MSC service thread 1-1) Could not find enum value for option: CAEngineKey
> 2012-11-05 16:40:56,918 WARN [org.ovirt.engine.core.utils.ConfigUtilsBase] (MSC service thread 1-1) Could not find enum value for option: SQLServerI18NPrefix
> 2012-11-05 16:40:57,172 WARN [org.ovirt.engine.core.utils.ConfigUtilsBase] (MSC service thread 1-1) Could not find enum value for option: ScriptsPath
> 2012-11-05 16:40:57,203 ERROR [org.ovirt.engine.core.dal.dbbroker.generic.DBConfigUtils] (MSC service thread 1-1) Could not parse option AutoRecoveryAllowedTypes value.
> 2012-11-05 16:40:57,205 WARN [org.ovirt.engine.core.utils.ConfigUtilsBase] (MSC service thread 1-1) Could not find enum value for option: MinimalETLVersion
> 2012-11-05 16:40:57,262 ERROR [org.ovirt.engine.core.engineencryptutils.EncryptionUtils] (MSC service thread 1-1) Failed to decrypt Data must start with zero
> 2012-11-05 16:40:57,262 ERROR [org.ovirt.engine.core.dal.dbbroker.generic.DBConfigUtils] (MSC service thread 1-1) Failed to decrypt value for property TruststorePass will be used encrypted value
> 2012-11-05 16:40:57,263 WARN [org.ovirt.engine.core.utils.ConfigUtilsBase] (MSC service thread 1-1) Could not find enum value for option: ENGINEEARLib
> 2012-11-05 16:40:57,355 INFO [org.ovirt.engine.core.bll.Backend] (MSC service thread 1-1) VDSBrokerFrontend: 11/5/12 4:40 PM
> 2012-11-05 16:40:57,366 INFO [org.ovirt.engine.core.bll.Backend] (MSC service thread 1-1) CpuFlagsManager: 11/5/12 4:40 PM
> 2012-11-05 16:40:57,370 INFO [org.ovirt.engine.core.bll.AuditLogCleanupManager] (MSC service thread 1-1) Setting audit clean up manager to run at: 35 35 3 * * ?
> 2012-11-05 16:40:57,371 ERROR [org.ovirt.engine.core.utils.ejb.EJBUtilsStrategy] (MSC service thread 1-1) Failed to lookup resource type: SCHEDULER. JNDI name: java:global/engine/engine-scheduler/Scheduler: javax.naming.NameNotFoundException: Error looking up engine/engine-scheduler/Scheduler, service service jboss.naming.context.java.global.engine.engine-scheduler.Scheduler is not started
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
> at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:123)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214)
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_09-icedtea]
> at org.ovirt.engine.core.utils.ejb.EJBUtilsStrategy.findBean(EJBUtilsStrategy.java:104) [engine-utils.jar:]
> at org.ovirt.engine.core.utils.ejb.EjbUtils.findBean(EjbUtils.java:23) [engine-utils.jar:]
> at org.ovirt.engine.core.utils.timer.SchedulerUtilQuartzImpl.getInstance(SchedulerUtilQuartzImpl.java:106) [engine-scheduler.jar:]
> at org.ovirt.engine.core.bll.AuditLogCleanupManager.<init>(AuditLogCleanupManager.java:34) [engine-bll.jar:]
> at org.ovirt.engine.core.bll.AuditLogCleanupManager.<clinit>(AuditLogCleanupManager.java:19) [engine-bll.jar:]
> at org.ovirt.engine.core.bll.Backend.Initialize(Backend.java:180) [engine-bll.jar:]
> at org.ovirt.engine.core.bll.Backend.create(Backend.java:118) [engine-bll.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_09-icedtea]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_09-icedtea]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_09-icedtea]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_09-icedtea]
> at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
>
>
>>
>> -basic operation
>>
>>
>> ----- Original Message -----
>>> From: "Ohad Basan" <obasan at redhat.com>
>>> To: "Eli Mesika" <emesika at redhat.com>, "Juan Hernandez"
>>> <jhernand at redhat.com>, "Federico Simoncelli"
>>> <fsimonce at redhat.com>, "Alon Bar-Lev" <alonbl at redhat.com>
>>> Cc: "Itamar Heim" <iheim at redhat.com>, arch at ovirt.org, "Moran
>>> Goldboim" <mgoldboi at redhat.com>
>>> Sent: Thursday, November 1, 2012 6:09:43 PM
>>> Subject: oVirt 3.2 on fedora 18
>>>
>>> Status:
>>>
>>>
>>> Clean F18 engine
>>>
>>> Status:
>>>
>>> -installation -
>>>
>>> passed RPM installation
>>> failed engine-setup
>>> Can't find systemct.conf - workaround
>>> http://gerrit.ovirt.org/#/c/8705/
>>> can't create a database due to wrong template1 encoding -
>>> workaround > change tempalte1 encoding to UTF8 -
>>>
>>> UPDATE pg_database SET datistemplate = FALSE WHERE datname
>>> =
>>> 'template1';
>>>
>>> DROP DATABASE template1;
>>>
>>> CREATE DATABASE template1 WITH TEMPLATE = template0
>>> ENCODING
>>> = 'UNICODE';
>>>
>>> UPDATE pg_database SET datistemplate = TRUE WHERE datname =
>>> 'template1';
>>>
>>> Patch that should solve it is here:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=870056
>>>
>>> can't find uuid-extension (The uuid-ossp extension is not
>>> available.
>>> It is possible the 'postgresql-contrib' package was not installed)
>>> -
>>> should also be solved by the patch above.
>>>
>>> -basic operation - not started
>>>
>>>
>>> Bugs:
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=867833
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=869221
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=870056
>>>
>>>
>>> Clean F18 vdsm
>>>
>>> -Installation -
>>>
>>> Passed RPM installation
>>> Bootstrapping fails. unable to create bridge. - workaround -
>>> create bridge manually. (if networking daemon doesn't start -
>>> try disabling selinux)
>>>
>>> -Basic Operation
>>>
>>> Added f18 host to engine > host doesn't reboot. workaround >
>>> reboot manually.
>>> Failed to set iptables due to the switch to firewalld
>>> Failed to attach storage domain.
>>>
>>> Bugs
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=869963
>>>
>>>
>>>
>>> Logs are attached.
>>> note the exception:
>>>
>>> Thread-103::ERROR::2012-11-01
>>> 13:58:53,630::task::833::TaskManager.Task::(_setError)
>>> Task=`5a51a266-2f10-4f1d-84f6-03417a41be2d`::Unexpected error
>>> Traceback (most recent call last):
>>> File "/usr/share/vdsm/storage/task.py", line 840, in _run
>>> return fn(*args, **kargs)
>>> File "/usr/share/vdsm/logUtils.py", line 38, in wrapper
>>> res = f(*args, **kwargs)
>>> File "/usr/share/vdsm/storage/hsm.py", line 801, in
>>> createStoragePool
>>> return sp.StoragePool(spUUID, self.taskMng).create(poolName,
>>> masterDom, domList, masterVersion, safeLease)
>>> File "/usr/share/vdsm/storage/sp.py", line 569, in create
>>> self._acquireTemporaryClusterLock(msdUUID, safeLease)
>>> File "/usr/share/vdsm/storage/sp.py", line 510, in
>>> _acquireTemporaryClusterLock
>>> msd.acquireHostId(self.id)
>>> File "/usr/share/vdsm/storage/sd.py", line 426, in acquireHostId
>>> self._clusterLock.acquireHostId(hostId, async)
>>> File "/usr/share/vdsm/storage/safelease.py", line 175, in
>>> acquireHostId
>>> raise se.AcquireHostIdFailure(self._sdUUID, e)
>>> AcquireHostIdFailure: Cannot acquire host id:
>>> ('7653059f-1141-444a-b5d6-9459d6d76638', SanlockException(-203,
>>> 'Sanlock lockspace add failure', 'Sanlock exception'))
>>>
>>>
>>> F17 to F18 upgrade engine
>>>
>>> -installation - Not started
>>>
>>> -basic operation
>>>
>>>
>>>
>>> F17 to F18 upgrade vdsm
>>>
>>> -installation - Not started
>>>
>>> -basic operation
>>>
>>>
>>> Thank you
>>
Would it be possible to test the following command in order to verify
that the database is accessible using TCP:
psql --host the_name_of_the_host --user engine engine
That should ask for the password and then should give you a database
prompt. If it doesn't then something is wrong with authentication in the
pg_hba.conf file.
--
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.
More information about the Arch
mailing list