[Spacewalk-list] two Maven servers have broken yum

[Michael Mraka]

Clouse, Raymond:
> On one of our environments we have two Maven servers (stage & prod) and on both yum seems to have broken:
> 
> $ yum list | grep salt
> Traceback (most recent call last):
>   File "/bin/yum", line 29, in <module>
>     yummain.user_main(sys.argv[1:], exit_code=True)
...
>   File "/usr/lib64/python2.7/site-packages/sqlitecachec.py", line 46, in getPrimary
>     self.repoid))
> TypeError: Can not create requiresname index: unable to open database file
> 
> Googling the last line gives me variations on rebuilding the yum database:
> 
> yum clean all
> rm -f /var/lib/rpm/__db*
> rpm --rebuilddb
> 
> But that doesn't fix the problem.
> 
> Perhaps Spacewalk has a separate database for yum and that needs to be rebuilt?  But then why is it just the Maven servers? (the rest of the servers on the environment have no problem, approximately 50 VMs)

Hello Raymond,

Spacewalk does not have a different database. It calls yum/rpm api which
then uses their internal databases. 

You can check if rpm database works, e.g. rpm -qa, rpm -ql kernel.
Then you can try to (backup and) remove yum's cache (/var/cache/yum/*) or
even yum history and package database (/var/lib/yum/*).

> Anyone else seen this kind of issue?

Regards,

--
Michael Mráka
System Management Engineering, Red Hat