Bug 1324075
Summary: | Can not access storage domain hosted_storage | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Richard Neuboeck <hawk> |
Component: | BLL.HostedEngine | Assignee: | Roy Golan <rgolan> |
Status: | CLOSED DUPLICATE | QA Contact: | meital avital <mavital> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.4 | CC: | amureini, bugs, rgolan, stirabos, tnisan |
Target Milestone: | --- | Flags: | rule-engine:
planning_ack?
rule-engine: devel_ack? rule-engine: testing_ack? |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | sla | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-04-08 06:43:21 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Richard Neuboeck
2016-04-05 13:08:39 UTC
Roy, this seems like more of a hosted engine issue, can someone from your team have a look? Pretty sure this is a dup of a bug we've already seen, but Tal seems to be correct - the hosted_engine domain is not registered properly. This problem must have been introduced after March 22. At this point installing the hosted-engine setup and adding additional hosts worked. Yes, it seams that the auto-import procedure in the engine took that storage domain as an NFS one. The temporary bug fix seems to be to update the storage connection in the database manually: On the Engine VM you find information to access the DB in /etc/ovirt-engine/engine.conf.d/10-setup-database.conf Then access the engine database and update the vfs_type field in the storage_server_connections table of the engine storage volume entry: psql -U engine -W -h localhost select * from storage_server_connections; update storage_server_connections set vfs_type = 'glusterfs' where id = 'THE_ID_YOU_FOUND_IN_THE_OUTPUT_ABOVE_FOR_THE_ENGINE_VOLUME'; *** This bug has been marked as a duplicate of bug 1317699 *** |