First of all I don't have too much experience in Fedora to say that this is 
actually a bug so it might be a problem on my part not being able to use repos 
or whatever.

My initial setup is explained in this other mailing list thread:
http://lists.ovirt.org/pipermail/users/2012-November/005125.html

Basically it's a Fedora 17 minimal installation with a /home mounted on a lvm 
partition and I just want to reinstall the whole oVirt again as an all-in-one 
setup without having to reinstall the whole Fedora 17.

So if I'm not mistaken (I repeat that I don't have too much experience in 
Fedora) the error is:

ovirt-engine-3.1.0-2.fc17.noarch needs:
  ovirt-engine-dbscripts = 3.1.0-2.fc17
but it's not going to be installed because the only version of:
ovirt-engine-dbscripts available in the repo is:
3.0.0.0001-13.fc17 .

  More than this I have: ovirt-engine-sdk 3.2 installed (instead of 3.1)... 
taking a look at the logs it would seem that:
yum upgrade --skip-broken
is the one that has updated ovirt-engine-sdk to 3.2 version.

  So... if no update of the repository was needed (as per apt-get update is 
usually needed in Debian.) and I just had to run yum upgrade I can confirm that 
bug: 869457 ( https://bugzilla.redhat.com/show_bug.cgi?id=869457 )  is not 
fixed at all.

  I'm temted to reinstall all the Fedora 17 again but it would be nice if you 
provided some yum commands to debug if the problem is for everyone or if it's 
specific of my setup so that we can confirm whether bug 869457 is fixed or not.

  Now I'm checking 
http://lists.ovirt.org/pipermail/users/2012-November/005116.html more carefully 
and they say to run:
engine-upgrade command which I haven't run. Anyways I think that running 
engine-cleanup and doing a yum upgrade should work (selecting the right 
ovirt-engine-sdk 3.1 version and not the 3.2 one) and it's not working at all.

Thank you!


(Here goes more or less the log):
-----------------------------------------


This is how I have proceeded:
(Don't proceed like this if you want to keep all your VMs... this is only a 
test machine)

engine-cleanup
rm -rf /home/iso
rm -rf /home/storage
rm -rf /etc/exports # I don't have any other exports there
yum upgrade # I run yum upgrade because it would seem that ovirt-engine-sdk is 
no longer upgraded to 3.2 as per bug 869457 and 
http://lists.ovirt.org/pipermail/users/2012-November/005116.html .

--> Resoluci�n de dependencias finalizada
Error: Paquete: ovirt-engine-3.1.0-2.fc17.noarch (@ovirt-stable)
           Necesita: ovirt-engine-dbscripts = 3.1.0-2.fc17
           Eliminando: ovirt-engine-dbscripts-3.1.0-2.fc17.noarch 
(@ovirt-stable)
               ovirt-engine-dbscripts = 3.1.0-2.fc17
           Actualizado por: ovirt-engine-dbscripts-3.1.0-4.fc17.noarch 
(ovirt-stable)
               ovirt-engine-dbscripts = 3.1.0-4.fc17
           Disponible: ovirt-engine-dbscripts-3.0.0.0001-12.fc17.noarch (fedora)
               ovirt-engine-dbscripts = 3.0.0.0001-12.fc17
           Disponible: ovirt-engine-dbscripts-3.0.0.0001-13.fc17.noarch 
(updates)
               ovirt-engine-dbscripts = 3.0.0.0001-13.fc17
 Podr�a intentar utilizar el comando --skip-broken para sortear el problema
** Se ha encontrado 1 problema(s) pre existentes en la base de datos RPM, este 
es el resultado de 'yum check':
kernel-headers-3.6.7-4.mykernel.fc17.x86_64 es uin duplicado con 
kernel-headers-3.6.7-4.fc17.x86_64

yum upgrade --skip-broken:

Updated:
  dbus.x86_64 1:1.4.10-7.fc17                                                
dbus-libs.x86_64 1:1.4.10-7.fc17
  ovirt-engine-sdk.noarch 0:3.2.0.2-1.fc17                                   
ovirt-engine-setup.noarch 0:3.1.0-4.fc17
  ovirt-engine-setup-plugin-allinone.noarch 0:3.1.0-4.fc17

Ignored (Dependency problems):
  ovirt-engine-dbscripts.noarch 0:3.1.0-4.fc17

Then I have run:

rpm -qa | grep ovirt

ovirt-engine-tools-common-3.1.0-2.fc17.noarch
ovirt-image-uploader-3.1.0-0.git9c42c8.fc17.noarch
ovirt-engine-restapi-3.1.0-2.fc17.noarch
ovirt-engine-3.1.0-2.fc17.noarch
ovirt-release-fedora-4-2.noarch
ovirt-engine-config-3.1.0-2.fc17.noarch
ovirt-engine-setup-plugin-allinone-3.1.0-4.fc17.noarch
ovirt-log-collector-3.1.0-0.git10d719.fc17.noarch
ovirt-engine-webadmin-portal-3.1.0-2.fc17.noarch
ovirt-engine-dbscripts-3.1.0-2.fc17.noarch
ovirt-engine-sdk-3.2.0.2-1.fc17.noarch
ovirt-engine-genericapi-3.1.0-2.fc17.noarch
ovirt-engine-backend-3.1.0-2.fc17.noarch
ovirt-engine-setup-3.1.0-4.fc17.noarch
ovirt-engine-notification-service-3.1.0-2.fc17.noarch
ovirt-iso-uploader-3.1.0-0.git1841d9.fc17.noarch
ovirt-engine-userportal-3.1.0-2.fc17.noarch

so... ovirt-engine-sdk 3.2 version is still there!
The bug is not fixed at all?


Let's downgrade it then:
yum downgrade ovirt-engine-sdk
It doesn't seem to work.

So I have tried:
yum remove kernel-headers-3.6.7-4.fc17.x86_64

And then: yum upgrade
[root@ns231094 ~]# yum upgrade
Complementos cargados:versionlock
Resolviendo dependencias
--> Ejecutando prueba de transacci�n
---> Paquete ovirt-engine-dbscripts.noarch 0:3.1.0-2.fc17 debe ser actualizado
--> Procesando dependencias: ovirt-engine-dbscripts = 3.1.0-2.fc17 para el 
paquete: ovirt-engine-3.1.0-2.fc17.noarch
---> Paquete ovirt-engine-dbscripts.noarch 0:3.1.0-4.fc17 debe ser una 
actualizaci�n
--> Resoluci�n de dependencias finalizada
Error: Paquete: ovirt-engine-3.1.0-2.fc17.noarch (@ovirt-stable)
           Necesita: ovirt-engine-dbscripts = 3.1.0-2.fc17
           Eliminando: ovirt-engine-dbscripts-3.1.0-2.fc17.noarch 
(@ovirt-stable)
               ovirt-engine-dbscripts = 3.1.0-2.fc17
           Actualizado por: ovirt-engine-dbscripts-3.1.0-4.fc17.noarch 
(ovirt-stable)
               ovirt-engine-dbscripts = 3.1.0-4.fc17
           Disponible: ovirt-engine-dbscripts-3.0.0.0001-12.fc17.noarch (fedora)
               ovirt-engine-dbscripts = 3.0.0.0001-12.fc17
           Disponible: ovirt-engine-dbscripts-3.0.0.0001-13.fc17.noarch 
(updates)
               ovirt-engine-dbscripts = 3.0.0.0001-13.fc17
 Podr�a intentar utilizar el comando --skip-broken para sortear el problema
Podr�a intentar ejecutar: rpm- Va --nofiles --nodigest

So... let's run:

rpm -Va --nofiles --nodigest
# Nothing interesting seen
I'm reading more carefully the log and I think it's telling me that:

ovirt-engine-3.1.0-2.fc17.noarch needs:
  ovirt-engine-dbscripts = 3.1.0-2.fc17
but it's not going to be installed the only version of:
ovirt-engine-dbscripts available in the repo is:
3.0.0.0001-13.fc17
.

So... not sure if I have hit a bug or if I need to force the ovirt repo 
manually when upgrading.

I'm going to run:
yum install -y http://www.ovirt.org\
/releases/ovirt-release-fedora.noarch.rpm

just in case. Nothing to be updated.

My final test was:

[root@ns231094 ~]# yum --enablerepo=ovirt upgrade
Complementos cargados:versionlock


Error getting repository data for ovirt, repository not found
[root@ns231094 ~]# yum --enablerepo=ovirt-stable upgrade
Complementos cargados:versionlock
Resolviendo dependencias
--> Ejecutando prueba de transacci�n
---> Paquete ovirt-engine-dbscripts.noarch 0:3.1.0-2.fc17 debe ser actualizado
--> Procesando dependencias: ovirt-engine-dbscripts = 3.1.0-2.fc17 para el 
paquete: ovirt-engine-3.1.0-2.fc17.noarch
---> Paquete ovirt-engine-dbscripts.noarch 0:3.1.0-4.fc17 debe ser una 
actualizaci�n
--> Resoluci�n de dependencias finalizada
Error: Paquete: ovirt-engine-3.1.0-2.fc17.noarch (@ovirt-stable)
           Necesita: ovirt-engine-dbscripts = 3.1.0-2.fc17
           Eliminando: ovirt-engine-dbscripts-3.1.0-2.fc17.noarch 
(@ovirt-stable)
               ovirt-engine-dbscripts = 3.1.0-2.fc17
           Actualizado por: ovirt-engine-dbscripts-3.1.0-4.fc17.noarch 
(ovirt-stable)
               ovirt-engine-dbscripts = 3.1.0-4.fc17
           Disponible: ovirt-engine-dbscripts-3.0.0.0001-12.fc17.noarch (fedora)
               ovirt-engine-dbscripts = 3.0.0.0001-12.fc17
           Disponible: ovirt-engine-dbscripts-3.0.0.0001-13.fc17.noarch 
(updates)
               ovirt-engine-dbscripts = 3.0.0.0001-13.fc17
 Podr�a intentar utilizar el comando --skip-broken para sortear el problema
Podr�a intentar ejecutar: rpm- Va --nofiles --nodigest

Finally I still get the 3.2 release:
[root@ns231094 ~]# rpm -qa | grep ovirt
ovirt-engine-tools-common-3.1.0-2.fc17.noarch
ovirt-image-uploader-3.1.0-0.git9c42c8.fc17.noarch
ovirt-engine-restapi-3.1.0-2.fc17.noarch
ovirt-engine-3.1.0-2.fc17.noarch
ovirt-release-fedora-4-2.noarch
ovirt-engine-config-3.1.0-2.fc17.noarch
ovirt-engine-setup-plugin-allinone-3.1.0-4.fc17.noarch
ovirt-log-collector-3.1.0-0.git10d719.fc17.noarch
ovirt-engine-webadmin-portal-3.1.0-2.fc17.noarch
ovirt-engine-dbscripts-3.1.0-2.fc17.noarch
ovirt-engine-sdk-3.2.0.2-1.fc17.noarch
ovirt-engine-genericapi-3.1.0-2.fc17.noarch
ovirt-engine-backend-3.1.0-2.fc17.noarch
ovirt-engine-setup-3.1.0-4.fc17.noarch
ovirt-engine-notification-service-3.1.0-2.fc17.noarch
ovirt-iso-uploader-3.1.0-0.git1841d9.fc17.noarch
ovirt-engine-userportal-3.1.0-2.fc17.noarch


The next commands I would have run:

export LANG=en_US.UTF-8
engine-setup

-- 

-- 
Adrián Gibanel 
I.T. Manager 

+34 675 683 301 
www.btactic.com 



Ens podeu seguir a/Nos podeis seguir en: 

i 


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

Reply via email to