Bug 1335658
| Summary: | Automate Storage Service Model missing association to Storage Clusters | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Greg McCullough <gmccullo> |
| Component: | Automate | Assignee: | Lucy Fu <lufu> |
| Status: | CLOSED ERRATA | QA Contact: | Dmitry Misharov <dmisharo> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.6.0 | CC: | jhardy, mkanoor, obarenbo, simaishi, tfitzger |
| Target Milestone: | GA | ||
| Target Release: | 5.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.6.0.7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-29 16:02:05 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Greg McCullough
2016-05-12 19:20:31 UTC
Lucy - I think the storage model should contain a virtual_has_many for storage_clusters as well as exposing the association through the automate service model. New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/57a73d0ca0d96e5c26532709d4755b83de923ff4 commit 57a73d0ca0d96e5c26532709d4755b83de923ff4 Author: Lucy Fu <lufu> AuthorDate: Thu May 12 15:49:11 2016 -0400 Commit: Lucy Fu <lufu> CommitDate: Thu May 12 15:49:11 2016 -0400 Add association Storage Clusters to Automate Storage Service Model. https://bugzilla.redhat.com/show_bug.cgi?id=1335658 app/models/storage.rb | 1 + lib/miq_automation_engine/service_models/miq_ae_service_storage.rb | 1 + 2 files changed, 2 insertions(+) Verified in 5.6.0.9 $evm.vmdb(:Storage).all.collect &:storage_clusters returns in my environment: => [[], [], [#<MiqAeServiceStorageCluster:0x5a4c6d0 @object=#<StorageCluster id: 33, name: "StorageCluster", ems_id: 1, created_on: "2016-06-02 10:07:35", updated_on: "2016-06-02 10:07:35", uid_ems: "group-p107665", ems_ref_obj: "--- !ruby/string:VimString\nstr: group-p107665\nxsiT...", ems_ref: "group-p107665", type: "StorageCluster", hidden: false>, @virtual_columns=["aggregate_cpu_speed", "aggregate_cpu_total_cores", "aggregate_disk_capacity", "aggregate_logical_cpus", "aggregate_memory", "aggregate_physical_cpus", "aggregate_vm_cpus", "aggregate_vm_memory", "region_description", "region_number"], @associations=["hosts", "vms"]>], [#<MiqAeServiceStorageCluster:0x5a3f264 @object=#<StorageCluster id: 33, name: "StorageCluster", ems_id: 1, created_on: "2016-06-02 10:07:35", updated_on: "2016-06-02 10:07:35", uid_ems: "group-p107665", ems_ref_obj: "--- !ruby/string:VimString\nstr: group-p107665\nxsiT...", ems_ref: "group-p107665", type: "StorageCluster", hidden: false>, @virtual_columns=["aggregate_cpu_speed", "aggregate_cpu_total_cores", "aggregate_disk_capacity", "aggregate_logical_cpus", "aggregate_memory", "aggregate_physical_cpus", "aggregate_vm_cpus", "aggregate_vm_memory", "region_description", "region_number"], @associations=["hosts", "vms"]>], [], [], [], [], [], [], [], [], [], []] Storage.all.collect &:storage_clusters returns => [[], [], [#<StorageCluster id: 33, name: "StorageCluster", ems_id: 1, created_on: "2016-06-02 10:07:35", updated_on: "2016-06-02 10:07:35", uid_ems: "group-p107665", ems_ref_obj: "--- !ruby/string:VimString\nstr: group-p107665\nxsiT...", ems_ref: "group-p107665", type: "StorageCluster", hidden: false>], [#<StorageCluster id: 33, name: "StorageCluster", ems_id: 1, created_on: "2016-06-02 10:07:35", updated_on: "2016-06-02 10:07:35", uid_ems: "group-p107665", ems_ref_obj: "--- !ruby/string:VimString\nstr: group-p107665\nxsiT...", ems_ref: "group-p107665", type: "StorageCluster", hidden: false>], [], [], [], [], [], [], [], [], [], []] 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://access.redhat.com/errata/RHBA-2016:1348 |