Created attachment 1134243 [details] /var/log/vdsm.log Description of problem: After stand-up of initial oVirt node, VDSM error messages are seen on oVirt UI denoting domain is either inaccessible or partially inaccessible. Version-Release number of selected component (if applicable): vdsm-4.17.23-0.el7.centos.noarch vdsm-cli-4.17.23-0.el7.centos.noarch vdsm-gluster-4.17.23-0.el7.centos.noarch vdsm-hook-vmfex-dev-4.17.23-0.el7.centos.noarch vdsm-infra-4.17.23-0.el7.centos.noarch vdsm-jsonrpc-4.17.23-0.el7.centos.noarch vdsm-python-4.17.23-0.el7.centos.noarch vdsm-xmlrpc-4.17.23-0.el7.centos.noarch vdsm-yajsonrpc-4.17.23-0.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. Install oVirt 3.6.3 2. Note the oVirt UI and vdsm.log, ERROR is thrown Actual results: 1. ERROR noted in oVirt UI and VDSM log. Expected results: 1. No error Additional info:
Ala, as this week's QE contact please have a look
Can you please share more info regarding what you did: Storage domain(s) you created When did you start seeing this error? Can you access the storage domain and make sure it is accessible?
I'm attaching the answerfile that was used for the non-interactive installation. The storage domains that were created are: - CRITICAL - NONCRITICAL - REPOS - ISODATASTORE - cpce_bd_storage (engine domain)
Created attachment 1134554 [details] answer file
These errors indicate that the storage is not accessible. Can you verify that the storage is accessible?
It appears that this issue is related to Bug 1269768. I found the following error in the ovirt-engine log: 2016-03-10 08:41:12,444 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainInfoVDSCommand] (org.ovirt.thread.pool-8-thread-41) [] FINISH, HSMGetStorageDomainInfoVDSCommand, return: <StorageDomainStatic:{name='cpce_bd_storage', id='7fa61429-4fcc-4f1a-bc03-62e8210acec2'}, null>, log id: 23f4591c We are deploying oVirt in a multiple host environment, but due to Bug 1311317, we are using OVEHOSTED_STORAGE/storageDomainName=str:cpce_bd_storage, not OVEHOSTED_STORAGE/storageDomainName=str:hosted_storage to allow us to currently add additional oVirt hosts. Due to the fact that the hosted engine cannot auto-import its engine storage domain, we are seeing this issue. The engine domain was accessible via NFS/Gluster from the first oVirt host. Performing a "showmount -e" displayed "engine" as an accessible mount point. However, when I tried importing that domain into oVirt, the hosted engine crashed.
We don't support this currently, you can do: engine-config -s HostedEngineStorageDomainName=custom_he_storage_domain_name service restart ovirt-engine See BZ 1303716. You can open RFE to support this.