Red Hat Bugzilla – Bug 1256036
[VDSM] monitor domain complains it can't find fcp domains on hsm hosts
Last modified: 2016-05-25 21:49:46 EDT
Description of problem: When having an fcp storage domain on a datacenter with more than one host, the hsm hypervisors will wrongly complain they can't "see" the fcp storage domain every 320 seconds. from vdsm.log: Thread-1171::ERROR::2015-08-23 16:51:06,447::sdc::138::Storage.StorageDomainCache::(_findDomain) looking for unfetched domain 5f081e07-1e99-4012-9fd9-345f8d74a116 Thread-1171::ERROR::2015-08-23 16:51:06,447::sdc::155::Storage.StorageDomainCache::(_findUnfetchedDomain) looking for domain 5f081e07-1e99-4012-9fd9-345f8d74a116 Where 5f081e07-1e99-4012-9fd9-345f8d74a116 is an fcp domain Version-Release number of selected component (if applicable): vdsm-4.17.2-1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1.create an fcp domain Actual results: HSM hypervisors complain they can't reach the fcp domain Expected results: The Error should be thrown only if the hypervisor can't see the storage Additional info:
Logs please?
Created attachment 1066772 [details] logs Hey, sorry about it :)
Every time the monitoring task wakes up, it will check when was the last time the domain have been refreshed to pick up changes on it. If it has been 300 sec or more , the domain will be dropped from the cache and will be refreshed. There is a configuration value 'repo_stats_cache_refresh_timeout' in config.py that define the refresh time (300 sec by default). The log you mentioned is from StorageDomainCache when it failed to find the domain in the cache and start refreshing it. This log does not mean the hypervisor is not seeing the storage, but that it did not find it in its cache and will refresh it. In my opinion, there is nothing to fix here.
*** This bug has been marked as a duplicate of bug 1101009 ***