Bug 1649424
| Summary: | Cannot attach Virtual Disk. The target Data Center does not contain the Virtual Disk. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Nikolai Sednev <nsednev> | ||||||
| Component: | ovirt-engine | Assignee: | Ahmad Khiet <akhiet> | ||||||
| Status: | CLOSED WORKSFORME | QA Contact: | meital avital <mavital> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.2.7 | CC: | lsurette, nsednev, tnisan | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-10-27 09:53:51 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Nikolai Sednev
2018-11-13 15:24:57 UTC
Created attachment 1505338 [details]
deploy logs from alma04
Initial deployment was made on iSCSI and then restore was made on NFS. Nikolai are you able to reproduce? (In reply to Sandro Bonazzola from comment #3) > Nikolai are you able to reproduce? I did not reproduced this, only opened when found the issue and reported it back. Please note that this bug is about different host cluster and storage domain name "restore" during restore, than was previously used for host cluster and storage domain as "test". Postponing to 4.3.0 not being identified as blocker for 4.2.8 Moving to 4.3.2 not being identified as blocker for 4.3.1. Can you please reproduce on latest build? Just got reproduced on my environment.
[ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[Cannot attach Virtual Disk. The target Data Center does not contain the Virtual Disk.]". HTTP response code is 409.
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Cannot attach Virtual Disk. The target Data Center does not contain the Virtual Disk.]\". HTTP response code is 409."}
[ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook
These are the components that reproduction was made on: ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch ovirt-hosted-engine-setup-2.3.5-1.el7ev.noarch ovirt-ansible-engine-setup-1.1.8-1.el7ev.noarch rhvm-appliance-4.3-20190220.2.el7.x86_64 Linux 3.10.0-957.5.1.el7.x86_64 #1 SMP Wed Dec 19 10:46:58 EST 2018 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.6 (Maipo) Looks like the issue is on engine side, moving to storage team for further investigations Hi, is this bug still reproducable? can you attach engine logs? Can't reproduce due to capacity. what I saw in the logs that there are deprecations in Ansible playbooks, and error related to Ansible mainly. I don't see in the attached logs anything I can follow to debug ovirt-engine or vdsm. I'm closing the bug. if the bug is reproduced, please attach the engine logs and vdsm logs, also clear and simple reproducing steps which this bug is missing. Removing target milestone and release since we have insufficient data for handling this report. During restore, customer is required to provide exactly the same datacenter and cluster names as were provided during initial deployment:
Please enter the name of the datacenter where you want to deploy this hosted-engine host. Please note that if you are restoring a backup that contains info about other hosted-engine hosts,
this value should exactly match the value used in the environment you are going to restore. [Default]:
Please enter the name of the cluster where you want to deploy this hosted-engine host. Please note that if you are restoring a backup that contains info about other hosted-engine hosts,
this value should exactly match the value used in the environment you are going to restore. [Default]:
Works as designed.
|