Bug 1336200
| Summary: | Clean ovirt setup (gluster r 3 a 1): VMs and Templates from imported ESD (external nfs) get imported to hosted_storage SD | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | mike.lupe | ||||||
| Component: | Backend.Core | Assignee: | Nobody <nobody> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | meital avital <mavital> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | future | CC: | bugs, dfediuck, didi, mavital, mike.lupe, nsednev, rgolan, ylavi | ||||||
| Target Milestone: | ovirt-4.1.0-alpha | Flags: | dfediuck:
ovirt-4.1?
rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-09-14 12:42:36 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
mike.lupe
2016-05-15 15:06:37 UTC
EDIT DESCRIPTION Please change the main description. "import of VMs and Templates to an imported Export Storage Domain (external nfs)" becomes "import of VMs and Templates from an imported Export Storage Domain (external nfs)" Thanks for the report, please attach engine/vdsm logs. Thanks. Created attachment 1158219 [details]
Choose different SD while importing
See comment 3 screenshot - I import a template into my setup from an export domain, click the template in the grid, click on disks subtab and then it reveals the dropdown of the domain. This is on ovirt master. What are you seeing while doing that>? Just writing this here to confirm that this issue is HC specific. I've tried to reproduce this scenarion on clean environment with non HC deployment over NFS, works just fine. My setup consists from pair el7.2 hosts: ovirt-vmconsole-1.0.2-2.el7ev.noarch vdsm-4.17.28-0.el7ev.noarch sanlock-3.2.4-2.el7_2.x86_64 ovirt-hosted-engine-setup-1.3.6.1-1.el7ev.noarch mom-0.5.3-1.el7ev.noarch ovirt-host-deploy-1.4.1-1.el7ev.noarch ovirt-setup-lib-1.0.1-1.el7ev.noarch qemu-kvm-rhev-2.3.0-31.el7_2.14.x86_64 ovirt-vmconsole-host-1.0.2-2.el7ev.noarch ovirt-hosted-engine-ha-1.3.5.5-1.el7ev.noarch Linux 3.10.0-327.22.1.el7.x86_64 #1 SMP Mon May 16 13:31:48 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.2 (Maipo) Engine: rhevm-setup-base-3.6.6.2-0.1.el6.noarch rhevm-websocket-proxy-3.6.6.2-0.1.el6.noarch rhevm-webadmin-portal-3.6.6.2-0.1.el6.noarch rhevm-spice-client-x64-cab-3.6-7.el6.noarch rhevm-dbscripts-3.6.6.2-0.1.el6.noarch rhevm-setup-plugins-3.6.5-1.el6ev.noarch rhevm-setup-plugin-ovirt-engine-3.6.6.2-0.1.el6.noarch rhevm-extensions-api-impl-3.6.6.2-0.1.el6.noarch rhevm-dwh-3.6.6-1.el6ev.noarch rhevm-reports-setup-3.6.5.1-1.el6ev.noarch rhevm-doc-3.6.0-7.el6eng.noarch rhevm-log-collector-3.6.1-1.el6ev.noarch rhevm-setup-plugin-ovirt-engine-common-3.6.6.2-0.1.el6.noarch rhevm-setup-plugin-websocket-proxy-3.6.6.2-0.1.el6.noarch rhevm-branding-rhev-3.6.0-9.el6ev.noarch rhevm-spice-client-x86-msi-3.6-7.el6.noarch rhevm-spice-client-x64-msi-3.6-7.el6.noarch rhevm-userportal-3.6.6.2-0.1.el6.noarch rhevm-restapi-3.6.6.2-0.1.el6.noarch rhevm-backend-3.6.6.2-0.1.el6.noarch rhevm-setup-3.6.6.2-0.1.el6.noarch rhevm-setup-plugin-vmconsole-proxy-helper-3.6.6.2-0.1.el6.noarch rhevm-3.6.6.2-0.1.el6.noarch rhevm-iso-uploader-3.6.0-1.el6ev.noarch rhevm-cli-3.6.2.0-1.el6ev.noarch rhevm-lib-3.6.6.2-0.1.el6.noarch rhevm-dwh-setup-3.6.6-1.el6ev.noarch rhevm-reports-3.6.5.1-1.el6ev.noarch rhevm-dependencies-3.6.0-1.el6ev.noarch rhevm-tools-backup-3.6.6.2-0.1.el6.noarch rhevm-spice-client-x86-cab-3.6-7.el6.noarch rhevm-tools-3.6.6.2-0.1.el6.noarch rhevm-vmconsole-proxy-helper-3.6.6.2-0.1.el6.noarch rhevm-sdk-python-3.6.5.0-1.el6ev.noarch rhevm-guest-agent-common-1.0.11-6.el6ev.noarch rhevm-image-uploader-3.6.0-1.el6ev.noarch Linux 2.6.32-642.el6.x86_64 #1 SMP Wed Apr 13 00:51:26 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 6.8 (Santiago) I've imported 2 VMs and 2 templates from another 3.6 environment. I've used NFS export domain created at other environment to export VMs and templates, then detached it from there and imported to my environment, then imported 2 VMs and 2 templates without any issues. Hi, please see comment5 - I would like to know what you did differently? I just want to know if we missing something. Hello all, first of all: sorry I haven't been able to respond earlier. Had a lot of things going on (besides redesigning my whole infrastructure #@+*รง). I can finally more or less understand what must had happened when the VMs & templates were imported to the "hosted_Storage" SD. I realized (based on RGolan's screenshot) that I didn't know we have the possibility to chose to which SD the disk can go to. So I didn't set anything when that happened. But this imho ultimately means, the default import SD was set to "hosted_storage". I guess this was RGolan's recommendation - "do not allow non-hosted engine object imports to "hosted_storage". Or maybe at least check default is not set to "hosted_storage". I'm sorry I still haven't got the time to anonymize the logfiles, but I hope it at least clears up a bit what happened. Kind regards Addition: I DO see the "hosted_storage" SD (besides the master data SD) when opening the "Storage Domain" dropdown list for the disk of the template to be imported. Created attachment 1161942 [details]
Import template: dropdown list for disk "Storage Domain" shows all data storages
Dropdown list shows all data storage domains when importing templates from nfs ESD.
*** This bug has been marked as a duplicate of bug 1309150 *** |