Bug 1166303
| Summary: | [RFE] VM Storage type [VSAN] not supported | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Jared Deubel <jdeubel> | ||||||||||
| Component: | Storage | Assignee: | Rich Oliveri <roliveri> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Dave Johnson <dajohnso> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | unspecified | CC: | adahms, bascar, dajohnso, jhardy, mfeifer, obarenbo, rhenness, roliveri, snansi, xlecauch | ||||||||||
| Target Milestone: | GA | Keywords: | FutureFeature | ||||||||||
| Target Release: | 5.4.0 | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||||||||
| Doc Text: |
The latest version of CloudForms Management Engine adds the ability for fleecing of VMs that reside on VSAN based datastores. Previously, when a user tried to run a smart state scan on VSAN datastores, he got an error. Users are now able to fleece VMs on VSAN based datastores.
|
Story Points: | --- | ||||||||||
| Clone Of: | |||||||||||||
| : | 1205780 (view as bug list) | Environment: | |||||||||||
| Last Closed: | 2015-06-16 12:45:01 UTC | Type: | Feature Request | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 1205780 | ||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 959467 [details]
grep of pid that has error
Rich, can you confirm if this is a valid test to help things along; edit the line described in the ticket unless ["VMFS", "NAS", "NFS", "ISCSI", "DIR", "FCP"].include? change it to unless ["VSAN", "VMFS", "NAS", "NFS", "ISCSI", "DIR", "FCP"].include? Eg, to include VSAN, save, restart EVM and try the test. I guess other areas of the code may need to also include the update, but is it as simple as this? Thanks John/Rich - I worked with the customer to change the unless statement in the file. After the change they ran the smart state check again. The check came back with an error message of: "Could not find VM:...." I sent you both a screenshot of the error message. Created attachment 994041 [details]
vsan_pid_evm.log
Created attachment 998568 [details]
vsan_cannot_find_vm
Created attachment 998569 [details]
screenshot_vsan
Created attachment 998859 [details]
full_evm_log
I was able to reproduce this problem, without the requisite back-end configuration, by hacking my MIQ environment and database. Hopefully, this will eliminate the need for continued iterations with the customer, and facilitate the resolution of this problem. New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/fefb52bfca5cf5dcad3d4544571e465ab6b003a0 commit fefb52bfca5cf5dcad3d4544571e465ab6b003a0 Author: Richard Oliveri <roliveri> AuthorDate: Wed Mar 25 11:38:15 2015 -0400 Commit: Richard Oliveri <roliveri> CommitDate: Wed Mar 25 11:38:15 2015 -0400 Fleecing support for VSAN. Enable the fleecing ov VMs that reside on VSAN based datastores. https://bugzilla.redhat.com/show_bug.cgi?id=1166303 https://bugzilla.redhat.com/show_bug.cgi?id=1205780 vmdb/app/models/job_proxy_dispatcher.rb | 2 +- vmdb/app/models/vm_or_template.rb | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) New commit detected on cfme/5.3.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=366b3de8fde7841104255de23d9ca6784e1f45c1 commit 366b3de8fde7841104255de23d9ca6784e1f45c1 Author: Richard Oliveri <roliveri> AuthorDate: Wed Mar 25 11:38:15 2015 -0400 Commit: Richard Oliveri <roliveri> CommitDate: Wed Mar 25 16:26:12 2015 -0400 Fleecing support for VSAN. Enable the fleecing ov VMs that reside on VSAN based datastores. https://bugzilla.redhat.com/show_bug.cgi?id=1166303 https://bugzilla.redhat.com/show_bug.cgi?id=1205780 vmdb/app/models/job_proxy_dispatcher.rb | 2 +- vmdb/app/models/vm_or_template.rb | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1100.html Cancelling the needinfo request on this bug; this doc text has been reviewed and included in the advisory. |
Description of problem: When trying to run a smart state scan on VSAN getting ERROR: MIQ(Vm-path) VM [vm_name] storage type [VSAN] not supported Looking at vmdb/app/models/job_proxy_dispatcher.rb, I can see that VSAN is not showing in the list: ========================================================================== else unless ["VMFS", "NAS", "NFS", "ISCSI", "DIR", "FCP"].include?(@vm.storage.store_type) msg = "Vm storage type [#{@vm.storage.store_type}] not supported [#{job.target_id}], aborting job [#{job.guid}]." self.queue_signal(job, {:args => [:abort, msg, "error"]}) ========================================================================== Version-Release number of selected component (if applicable): 5.3.0.15 How reproducible: Very