Re: [Users] ovirt-engine-dbscripts broken dependencies on F17
Yes, I confirm it's working. I don't get the error: "could not create ovirtsdk API object" when using it. I've just done: engine-cleanup rm -rf /home/iso rm -rf /home/storage rm /etc/exports yum remove ovirt* yum install -y http://www.ovirt.org\ /releases/ovirt-release-fedora.noarch.rpm yum install -y ovirt-engine-setup-plugin-allinone export LANG=en_US.UTF-8 engine-setup I have some annoying problems with storage which I have described in another thread but as I say the engine-setup command did not issue any error. - Mensaje original - De: "Itamar Heim" Para: "Adrian Gibanel" CC: users@ovirt.org Enviados: Martes, 27 de Noviembre 2012 15:44:26 Asunto: Re: [Users] ovirt-engine-dbscripts broken dependencies on F17 On 11/27/2012 07:55 AM, Adrian Gibanel wrote: > While I was trying to fix it on my own with the commands you will see > below I have taken a look at the fix which has nothing to do with 3.1 / > 3.2 version (I was interpreting the bug as its fixing was going to just > fix the dependency to be ovirt-engine-sdk 3.1 as the manual workaround > that Jason Brooks proposed). It has to do with the new security mode. > > So... What I understand so far is that: > > * I should have read the commit so see what was actually been fixed and how. > * If you install ovirt 3.1 in Fedora 17 you will find an > ovirt-engine-sdk 3.2 package and that should work fine. > > So sorry about all these warnings and I will give you feedback about how > ovirt-engine-sdk 3.2 package works in Fedora 17. we just released 3.1.0-4 1-2 days ago fixing this issue specifically. seems its working -- 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
Re: [Users] ovirt-engine-dbscripts broken dependencies on F17
On 11/27/2012 07:55 AM, Adrian Gibanel wrote:
While I was trying to fix it on my own with the commands you will see
below I have taken a look at the fix which has nothing to do with 3.1 /
3.2 version (I was interpreting the bug as its fixing was going to just
fix the dependency to be ovirt-engine-sdk 3.1 as the manual workaround
that Jason Brooks proposed). It has to do with the new security mode.
So... What I understand so far is that:
* I should have read the commit so see what was actually been fixed and how.
* If you install ovirt 3.1 in Fedora 17 you will find an
ovirt-engine-sdk 3.2 package and that should work fine.
So sorry about all these warnings and I will give you feedback about how
ovirt-engine-sdk 3.2 package works in Fedora 17.
we just released 3.1.0-4 1-2 days ago fixing this issue specifically.
seems its working
---
yum remove ovirt*
yum install -y http://www.ovirt.org\
/releases/ovirt-release-fedora.noarch.rpm
yum install -y ovirt-engine-setup-plugin-allinone
Instalando:
ovirt-engine-setup-plugin-allinone noarch
3.1.0-4.fc17 ovirt-stable 12 k
Instalando para las dependencias:
ovirt-engine noarch
3.1.0-4.fc17 ovirt-stable 1.0 M
ovirt-engine-backend noarch
3.1.0-4.fc17 ovirt-stable 7.0 M
ovirt-engine-confignoarch
3.1.0-4.fc17 ovirt-stable 130 k
ovirt-engine-dbscripts noarch
3.1.0-4.fc17 ovirt-stable 132 k
ovirt-engine-genericapinoarch
3.1.0-4.fc17 ovirt-stable 18 k
ovirt-engine-notification-service noarch
3.1.0-4.fc17 ovirt-stable 52 k
ovirt-engine-restapi noarch
3.1.0-4.fc17 ovirt-stable 5.0 M
ovirt-engine-sdk noarch
3.2.0.2-1.fc17updates 211 k
ovirt-engine-setup noarch
3.1.0-4.fc17 ovirt-stable 115 k
ovirt-engine-tools-common noarch
3.1.0-4.fc17 ovirt-stable 8.8 k
ovirt-engine-userportalnoarch
3.1.0-4.fc17 ovirt-stable 13 M
ovirt-engine-webadmin-portal noarch
3.1.0-4.fc17 ovirt-stable 15 M
ovirt-image-uploader noarch
3.1.0-0.git9c42c8.fc17ovirt-stable 92 k
ovirt-iso-uploader noarch
3.1.0-0.git1841d9.fc17ovirt-stable 29 k
ovirt-log-collectornoarch
3.1.0-0.git10d719.fc17ovirt-stable 53 k
Wrong! It's trying to get ovirt-engine-sdk 3.2 !
===
# Trying to ignore the 3.2 version unsucessfully
yum remove ovirt*
yum install -y http://www.ovirt.org\
/releases/ovirt-release-fedora.noarch.rpm
yum install --disablerepo=updates -y ovirt-engine-setup-plugin-allinone
--> Resoluci�n de dependencias finalizada
Error: Paquete: ovirt-engine-setup-plugin-allinone-3.1.0-4.fc17.noarch
(ovirt-stable)
Necesita: ovirt-engine-sdk >= 3.2
Disponible: ovirt-engine-sdk-1.3-1.fc17.noarch (fedora)
ovirt-engine-sdk = 1.3-1.fc17
Instalando: ovirt-engine-sdk-3.1.0.4-1.fc17.noarch
(ovirt-stable)
ovirt-engine-sdk = 3.1.0.4-1.fc17
Error: Paquete: ovirt-engine-setup-plugin-allinone-3.1.0-4.fc17.noarch
(ovirt-stable)
Necesita: ovirt-engine-sdk >= 3.2
Disponible: ovirt-engine-sdk-1.3-1.fc17.noarch (fedora)
ovirt-engine-sdk = 1.3-1.fc17
Disponible: ovirt-engine-sdk-3.1.0.4-1.fc17.noarch
(ovirt-stable)
ovirt-engine-sdk = 3.1.0.4-1.fc17
Podr�a intentar utilizar el comando --skip-broken para sortear el problema
*De: *"Adrian Gibanel"
*Para: *users@ovirt.org
*Enviados: *Martes, 27 de Noviembre 2012 13:31:06
*Asunto: *[Users] ovirt-engine-dbscripts broken dependencies on F17
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 .
--
<http://www.btactic.com/>*Adrián Gibanel*
I.T. Manager
+34 675 683 301
www.btactic.com <http://btactic.com/>
*
Ens podeu segui
Re: [Users] ovirt-engine-dbscripts broken dependencies on F17
While I was trying to fix it on my own with the commands you will see below I have taken a look at the fix which has nothing to do with 3.1 / 3.2 version (I was interpreting the bug as its fixing was going to just fix the dependency to be ovirt-engine-sdk 3.1 as the manual workaround that Jason Brooks proposed). It has to do with the new security mode. So... What I understand so far is that: * I should have read the commit so see what was actually been fixed and how. * If you install ovirt 3.1 in Fedora 17 you will find an ovirt-engine-sdk 3.2 package and that should work fine. So sorry about all these warnings and I will give you feedback about how ovirt-engine-sdk 3.2 package works in Fedora 17. --- yum remove ovirt* yum install -y http://www.ovirt.org\ /releases/ovirt-release-fedora.noarch.rpm yum install -y ovirt-engine-setup-plugin-allinone Instalando: ovirt-engine-setup-plugin-allinone noarch 3.1.0-4.fc17 ovirt-stable 12 k Instalando para las dependencias: ovirt-engine noarch 3.1.0-4.fc17 ovirt-stable 1.0 M ovirt-engine-backend noarch 3.1.0-4.fc17 ovirt-stable 7.0 M ovirt-engine-config noarch 3.1.0-4.fc17 ovirt-stable 130 k ovirt-engine-dbscripts noarch 3.1.0-4.fc17 ovirt-stable 132 k ovirt-engine-genericapi noarch 3.1.0-4.fc17 ovirt-stable 18 k ovirt-engine-notification-service noarch 3.1.0-4.fc17 ovirt-stable 52 k ovirt-engine-restapi noarch 3.1.0-4.fc17 ovirt-stable 5.0 M ovirt-engine-sdk noarch 3.2.0.2-1.fc17 updates 211 k ovirt-engine-setup noarch 3.1.0-4.fc17 ovirt-stable 115 k ovirt-engine-tools-common noarch 3.1.0-4.fc17 ovirt-stable 8.8 k ovirt-engine-userportal noarch 3.1.0-4.fc17 ovirt-stable 13 M ovirt-engine-webadmin-portal noarch 3.1.0-4.fc17 ovirt-stable 15 M ovirt-image-uploader noarch 3.1.0-0.git9c42c8.fc17 ovirt-stable 92 k ovirt-iso-uploader noarch 3.1.0-0.git1841d9.fc17 ovirt-stable 29 k ovirt-log-collector noarch 3.1.0-0.git10d719.fc17 ovirt-stable 53 k Wrong! It's trying to get ovirt-engine-sdk 3.2 ! === # Trying to ignore the 3.2 version unsucessfully yum remove ovirt* yum install -y http://www.ovirt.org\ /releases/ovirt-release-fedora.noarch.rpm yum install --disablerepo=updates -y ovirt-engine-setup-plugin-allinone --> Resoluci�n de dependencias finalizada Error: Paquete: ovirt-engine-setup-plugin-allinone-3.1.0-4.fc17.noarch (ovirt-stable) Necesita: ovirt-engine-sdk >= 3.2 Disponible: ovirt-engine-sdk-1.3-1.fc17.noarch (fedora) ovirt-engine-sdk = 1.3-1.fc17 Instalando: ovirt-engine-sdk-3.1.0.4-1.fc17.noarch (ovirt-stable) ovirt-engine-sdk = 3.1.0.4-1.fc17 Error: Paquete: ovirt-engine-setup-plugin-allinone-3.1.0-4.fc17.noarch (ovirt-stable) Necesita: ovirt-engine-sdk >= 3.2 Disponible: ovirt-engine-sdk-1.3-1.fc17.noarch (fedora) ovirt-engine-sdk = 1.3-1.fc17 Disponible: ovirt-engine-sdk-3.1.0.4-1.fc17.noarch (ovirt-stable) ovirt-engine-sdk = 3.1.0.4-1.fc17 Podr�a intentar utilizar el comando --skip-broken para sortear el problema - Mensaje original - > De: "Adrian Gibanel" > Para: users@ovirt.org > Enviados: Martes, 27 de Noviembre 2012 13:31:06 > Asunto: [Users] ovirt-engine-dbscripts broken dependencies on F17 > 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 . -- 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
[Users] ovirt-engine-dbscripts broken dependencies on F17
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
