On Wed, Feb 6, 2019 at 6:33 AM Nicolas Ecarnot <nicolas@ecarnot.net> wrote:
Le 06/02/2019 à 10:53, Lucie Leistnerova a écrit :
On 2/6/19 10:22 AM, Nicolas Ecarnot wrote:
Hi Lucie,
Le 06/02/2019 à 10:02, Lucie Leistnerova a écrit :
I'm sorry, my mistake I did not mention to remove the package without dependencies.
Same -- sorry, ugh. For anyone in the same situation, the better thing to do now is simply 'yum update ovirt-engine-ui-extensions' That will remove the old dashboard correctly. https://github.com/oVirt/ovirt-engine-ui-extensions/blob/master/packaging/sp...
rpm -e --nodeps ...
I'll write that down.
When looking at the log file above ( https://framadrop.org/r/ywTOD-Q02-#dA6hdYaxfZpgUB68gtJLB9inH5oJajrL4H9LTktDd...)
[...]
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py",
The error is cause by missing ovirt-engine-dbscripts.
OK
Well, I thought I messed up with packages, and I thought a compete yum update would help, as I read :
Le 05/02/2019 à 15:19, Greg Sheremeta wrote :
The fix is pushed. Standalone engine upgrades should be fine starting > now. `yum update` any appliance engines or already upgraded > engines to get the latest ovirt-engine-ui-extensions, which fixes > the problem.
So I ran a yum update.
This package is part of ovirt-engine versionlock so can't be installed/updated separately. engine-setup should install the missing packages. I tried it by myself and it fixed the issue.
[install]
ovirt-engine-dbscripts-4.3.0.5-0.0.master.20190205084851.gitaaebfc9.el7.noarch
will be installed
I see I have this package, though in an older version : # rpm -qa|grep -i dbscripts ovirt-engine-dbscripts-4.3.0.4-1.el7.noarch
The version shouldn't be problem. I tested it in u/s ovirt. Now I tried with same version.
Try to remove that package and install again. Versionlock seems to differ here so I was able to install it separately, if not run engine-setup.
# rpm -e --nodeps ovirt-engine-dbscripts
Indeed, it found a lot of missing files/dir.
# yum install ovirt-engine-dbscripts
I forgot to set LANG=C so you'll read some parts in french, but I get the idea :
---------------------------------------------------------------- root@mvm01:/tmp# yum install ovirt-engine-dbscripts Modules complémentaires chargés : fastestmirror, versionlock Loading mirror speeds from cached hostfile * base: centos.mirror.fr.planethoster.net * epel: pkg.adfinis-sygroup.ch * extras: ftp.pasteur.fr * ovirt-4.3: ovirt.repo.nfrance.com * ovirt-4.3-epel: pkg.adfinis-sygroup.ch * updates: centos.mirror.fr.planethoster.net Excluding 1 update due to versionlock (use "yum versionlock status" to show it) Résolution des dépendances --> Lancement de la transaction de test ---> Le paquet ovirt-engine-dbscripts.noarch 0:4.3.0.4-1.el7 sera installé --> Résolution des dépendances terminée
Dépendances résolues
===================================================================================================================================================================================================================================== Package Architecture Version Dépôt Taille
===================================================================================================================================================================================================================================== Installation : ovirt-engine-dbscripts noarch 4.3.0.4-1.el7 ovirt-4.3 331 k
Résumé de la transaction
===================================================================================================================================================================================================================================== Installation 1 Paquet
Taille totale des téléchargements : 331 k Taille d'installation : 1.6 M Is this ok [y/d/N]: y Downloading packages: ovirt-engine-dbscripts-4.3.0.4-1.el7.noarch.rpm
| 331 kB 00:00:02 Running transaction check Running transaction test Transaction test succeeded Running transaction Avertissement : RPMDB a été modifiée par une autre application que yum. ** 1 problèmes RPMDB préexistants trouvés, la sortie de « yum check » est la suivante : ovirt-engine-4.3.0.4-1.el7.noarch a des dépendances manquantes de ovirt-engine-dbscripts = ('0', '4.3.0.4', '1.el7') Installation : ovirt-engine-dbscripts-4.3.0.4-1.el7.noarch
1/1 Vérification : ovirt-engine-dbscripts-4.3.0.4-1.el7.noarch
1/1
Installé : ovirt-engine-dbscripts.noarch 0:4.3.0.4-1.el7
Terminé !
-------------------------------------------------------------
After that, I ran again engine-setup and it went OK. Now, my ovirt DC and dashboard is back to life, thanks to you Lucie.
To sum up, I think what I'm missing is a clear and solide documentation or official Redhat message about whether/what/how/when can/cannot we update (with "yum update") the engine host and/or the hosts.
Not Red Hat -- oVirt :) Indeed, we need an Upgrade Guide update. I'll look into it. Generally, on my dev instances (which are probably nowhere near as complicated as your setups), I run 'yum update' followed by 'engine-setup'. Perhaps Sandro can speak further to the versionlock stuff. I don't understand it that much. Greg
??
-- Nicolas ECARNOT _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/WNGSIBQ4UJ36TD...
-- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme@redhat.com IRC: gshereme <https://red.ht/sig>