RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
Summary: vdsm: "Failed to collect auth credentials" error from vdsm after yum downgrad...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Barak
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-10 13:22 UTC by Dafna Ron
Modified: 2012-10-14 07:50 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-14 07:50:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
logs (1.83 MB, application/x-gzip)
2012-09-10 13:22 UTC, Dafna Ron 		no flags Details
View All

Description Dafna Ron 2012-09-10 13:22:41 UTC 
Created attachment 611428 [details]
logs

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
    serve_clients(log)
  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):


How reproducible:

100%

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
  
Actual results:

when vdsm starts we cannot comunicate to libvirt with:
authentication failed: Failed to collect auth credentials

Expected results:

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: 
libvirt_password.rpmnew   libvirt_password.rpmsave
both have the correct password.
Comment 1 Alon Bar-Lev 2012-09-12 22:17:40 UTC 
Is downgrade supported?
Comment 2 Barak 2012-09-14 14:56:12 UTC 
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 ?
Comment 3 Simon Grinberg 2012-09-23 16:41:01 UTC 
(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?
Comment 4 Alon Bar-Lev 2012-09-27 17:59:21 UTC 
I need answer here.

I don't think this should be supported.

Downgrade should be done using full bootstrap procedure.
Comment 5 Alon Bar-Lev 2012-10-04 16:47:41 UTC 
Barak, please assign to me when we have some answer.

I think this should not be supported.
Note You need to log in before you can comment on or make changes to this bug.