Reports Fail When Using CPU or Memory Ratio Column [Najdorf-1 vSphere Image]

[derekleeth]

We are having an issue with the latest stable version [Najdorf-1] we've deployed in one of our datacenters where reports fail to show any data at all when you add the "CPU Cores Virtual to Real Ratio" or "Memory Virtual to Real Ratio" columns to a report. We are running older versions of MIQ (Ivanchuk & Fine) in some datacenters that do not have this issue. If we remove those columns from the report, the report does not error out and shows data.

Report w/ Ratio Columns

Reports Failing w/ Ratio Columns

Report w/out Real Ratio Columns Showing Data

[Fryguy]

Sounds like a possible bug with aggregation?

[derekleeth]

I'm not 100% sure if it helps but it does show the "Virtual to Real Ratio" for memory and CPU when you pull up an individual cluster. Here's the screenshot below that shows the two fields.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

[miq-bot]

This issue has been automatically closed because it has not been updated for at least 3 months.

Feel free to reopen this issue if this issue is still valid.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

[kbrock]

columns referenced:

• CPU Cores Virtual to Real Ratio: v_cpu_vr_ratio = aggregate_vm_cpus / aggregate_cpu_total_cores cluster.yaml
• Memory Virtual to Real Ratio: v_ram_vr_ratio = aggregate_vm_memory / aggregate_memory (this is accessing aggregate_vm_memory vs total_memory -- just a note) referenced in product/reports/130_Configuration\ Management\ -\ Clusters/040_Cluster\ Resources.yaml

general notes:

• There are division by zero checks for both
• it is rounded by one decimal place
• both defined in ems_cluster.rb:81
• ems_cluster.rb does test include_examples "AggregationMixin" to test the shared_example_for "AggregationMixin". need to verify that it runs one for ems_cluster (there is an if block around class)

[kbrock]

@Fryguy I noticed that EmsCluster uses AggregationMixin.

class EmsCluster
  include AggregationMixin
  # include `RelationshipsAggregationMixin`
  has_many    :vms

  def direct_vms
    Relationship.resources(direct_vm_rels).sort_by { |v| v.name.downcase }
  end
end

That is used for creating virtual totals based upon a has_many :vms which sounds about right. But it also has the direct_vms, which make it sound like this should be a recursive type calculation and therefore using relationships

These seem to contradict each other. Ideas which one of these is correct?

[Fryguy]

Cluster has a normal vms relationship in the database...this is the same as "all_vms". direct_vms goes through resource_pools which is relationship based and only gets vms directly in the immediate resource pool.

[kbrock]

ok. cool. so direct_vms is an extra addon.

EmsFolder and ResourcePool definitely use relationships for children

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.