Red Hat Bugzilla – Bug 1017056
virt-who can't work in the VDSM mode
Last modified: 2016-11-30 19:32:13 EST
Description of problem:
During test the Rhel6.5 + Rhevm3.2(vdsm mode) against SAM1.3, after set the virt-who work under the VDSM Mode, virt-who cannot work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. In the host, Set the virt-who parameters in file /etc/sysconfig/virt-who to make virt-who working in VDSM mode:
2. Restart service virt-who
# service virt-who restart
Stopping virt-who: [ OK ]
Starting virt-who: [ OK ]
3. Restart vdsmd service
# service vdsmd restart
Shutting down vdsm daemon:
vdsm watchdog stop [ OK ]
vdsm stop [ OK ]
vdsm: libvirt already configured for vdsm [ OK ]
Starting up vdsm daemon:
vdsm start [ OK ]
4. check the log file:
# tail -f /var/log/rhsm/rhsm.log
2013-10-09 15:43:48,010 [ERROR] @virt-who.py:184 - Unable to recover, retry in 10 seconds.
2013-10-09 15:43:58,020 [ERROR] @virt-who.py:181 - Unable to create connection:
Traceback (most recent call last):
File "/usr/share/virt-who/virt-who.py", line 178, in _send
File "/usr/share/virt-who/virt-who.py", line 157, in checkConnections
File "/usr/share/virt-who/virt-who.py", line 96, in initVirt
self.virt = VDSM(self.logger)
File "/usr/share/virt-who/vdsm.py", line 45, in __init__
File "/usr/share/virt-who/vdsm.py", line 54, in _readConfig
self.trust_store_path = parser.get("vars", "trust_store_path")
File "/usr/lib64/python2.6/ConfigParser.py", line 541, in get
raise NoOptionError(option, section)
NoOptionError: No option 'trust_store_path' in section: 'vars'
It hasn't sent the host/guest association to SAM server
virt-who should run normally under the VDSM mode, it should send the correct host/guest association to SAM server.
You're missing 'trust_store_path' option in the 'vars' section of /etc/vdsm/vdsm.conf file.
Virt-who is missing the check for this exception, I'll add it - it's easy fix.
(In reply to Radek Novacek from comment #2)
> You're missing 'trust_store_path' option in the 'vars' section of
> /etc/vdsm/vdsm.conf file.
> Virt-who is missing the check for this exception, I'll add it - it's easy
Hi Radek, I found this bug has been suggested to move to RHEL 6.6.0, but it blocked our virt-who test in vdsm mode for now, if it can not be fixed in RHEL 6.5, RHEL 6.5 will not support vdsm mode, is it as expected?
If it's possible, I suggest to fix it in RHEL 6.5, thanks.
I think it is too late for 6.5 fix. You can workaround this issue quite easily by adding 'trust_store_path' option to the 'vars' section in the /etc/vdsm/vdsm.conf file.
(In reply to Radek Novacek from comment #4)
> I think it is too late for 6.5 fix. You can workaround this issue quite
> easily by adding 'trust_store_path' option to the 'vars' section in the
> /etc/vdsm/vdsm.conf file.
Got it, after adding "trust_store_path = /etc/pki/vdsm" to /etc/vdsm/vdsm.conf, we can test vdsm mode now, thanks.
This bug is fixed upstream and will be resolved by rebase of virt-who, see bug 1002640.
This bug is fixed by rebase to virt-who-0.10-1.el6.
Verification of this bug is blocked by vdsm installation issue in rhel6.6, sent mail to email@example.com who is the vdsm Errata 18458 owner with Radek cc'd for help, after the issue got resolved, we will verify this bug ASAP.
Can't verify as bug 1135341
Verified on virt-who-0.10-7.el6.noarch
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.
Though this bug is fixed in RHEL6.6, in RHEVH6.5 and this bug is still exist. And now we are testing RHEVH6.5 and this bug bothers us, What should we do to deal with this bug?