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.

Description of problem:
getSpmStatus is returned from cache which might be wrong - faced a problem with it when rhevm goes up and doesn't know which is the SPM, he sends getSpmStatus to a random host in the cluster and based on the spmId from the result tries that host for spm, since the spmId is wrong rhevm fails and looks for additional host - which may take a long time on a large scaled env.

Version-Release number of selected component (if applicable):
vdsm-4.9-91.el6.x86_64

How reproducible:


Steps to Reproduce:
1.restart vdsm on spm
2.let other host take spm
3.run getSpmStatus on old spm
  
Actual results:
when rhevm goes up it tries to take spm using multiple hosts - and get resource acquire timeout. 

Expected results:


Additional info:
running on host id 89 - vdsm says that spm runs on hostId 89 and free...
[root@dhcp151-128 ~]# vdsClient -s 0 getSpmStatus e505624e-c8af-11e0-96a0-03e8c0272e3a
        spmId = 89
        spmStatus = Free
        spmLver = 4

http://gerrit.usersys.redhat.com/#change,860

Checked on 4.9-104.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2011-1782.html