Red Hat Bugzilla – Bug 855872
vdsm: "Failed to collect auth credentials" error from vdsm after yum downgrade on vdsm from 4.9.6-32 back to vdsm-4.9-113.3
Last modified: 2012-10-14 03:50:31 EDT
Created attachment 611428 [details]
Description of problem:
I am testing upgrade from 3.0 cluster to 3.1
after upgrading the vdsm I decided to downgrade and rerun the vdsm upgrade so I ran yum downgrade vdsm
when vdsm came back up it cannot communicate with libvirt with the below error:
MainThread::ERROR::2012-09-10 16:06:06,512::vdsm::74::vds::(run) Traceback (most recent call last):
File "/usr/share/vdsm//vdsm", line 72, in run
File "/usr/share/vdsm//vdsm", line 40, in serve_clients
cif = clientIF.clientIF(log)
File "/usr/share/vdsm/clientIF.py", line 92, in __init__
self._libvirt = libvirtconnection.get()
File "/usr/share/vdsm/libvirtconnection.py", line 94, in get
conn = libvirt.openAuth('qemu:///system', auth, 0)
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 102, in openAuth
if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: authentication failed: Failed to collect auth credentials
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install vdsm vdsm-4.9-113.3.el6_3.x86_64
2. upgrade to 4.9.6-32.0.el6_3
3. restart vdsm
4. run yum downgrade vdsm
when vdsm starts we cannot comunicate to libvirt with:
authentication failed: Failed to collect auth credentials
we should be able to connect to libvirt
Additional info: attaching vdsm logs and libvirt_password files.
I tried restarting libvirt/vdsm and the host.
looking at cd /etc/pki/vdsm/keys/ I can see two files:
both have the correct password.
Is downgrade supported?
There are 2 aspects for that:
- QE scenario as shown above
- Customers that upgrade a zstream VDSM that brings out a problem in their
setup, they may want to downgrade it.
I have instructed Dafna to open this BZ just to bring up the discussion and get PM's response.
I think that a GSS KB is enough.
Should it be tested by QE ?
Andrew ? Miki ?
(In reply to comment #2)
> There are 2 aspects for that:
> - QE scenario as shown above
> - Customers that upgrade a zstream VDSM that brings out a problem in their
> setup, they may want to downgrade it.
The problem is more complicated then that, since if the customer used re-install the host to upgrade the host then there may be other packaged that may have been upgraded including libvirt. Roll back should be done for all in this case or old VDSM may not work properly - right?
I need answer here.
I don't think this should be supported.
Downgrade should be done using full bootstrap procedure.
Barak, please assign to me when we have some answer.
I think this should not be supported.