Unsolved

This post is more than 5 years old

2 Posts

144353

August 19th, 2013 09:00

VMware CPU Overallocation report does not list data after being copied to My Definitions

Hi Team,

ENV:

vFoglight 6.8

PROBLEM:

SC attempt to duplicate an OOTB report to customize the report for our customer.

The duplicated VMware CPU Overallocation report does not list data when it is being deep copied to My Definitions

VMware CPU Overallocation report is duplicated by using deep copy from Definitions > Capacity Management > VMware > Optimization to My Definitons.

1.png

2.png

Warning message appeared while copying the getListSizeWithUnit function...

3.png

5.png

The OOTB VMware CPU Overallocation report is reporting data when it is being run.

Refer to the attached VMware CPU Overallocation report.pdf.

However, the duplicated VMware CPU Overallocation report does not list out any data when we attempt to run the report.

Refer to the attached Duplicated VMware CPU Overallocation report.pdf.

QUESTION:

1. Any idea why the duplicated report fail to list out any data?

2. Any suggestion on how to duplicate OOTB report for customization purpose?

Thank you

Regards,

-Ken

Additional Attachments:

1 Attachment

August 19th, 2013 12:00

Hey Ken,

I tried to repo customer's issue with FVE 6.8.

Please find the screenshots of the WARNING message, the generated report being empty.

Definitions.jpg

View copied to Reports dashboard:

reports.jpg

Empty report:

empty_PDF.jpg

But also find this KB, which talks about the warning:

https://support.quest.com/SolutionDetail.aspx?id=SOL73897&pr=Foglight

However, a warning message will be issued that the inaccessible, non-public entity will be copied and the reference will be changed to refer to the copy. This may not be what you want.

Could be design of the product, where a canned report cannot be copied as it is.

KB talks as below:

However, a warning message will be issued that the inaccessible, non-public entity will be copied and the reference will be changed to refer to the copy. This may not be what you want. You may actually want the references to be maintained because you intend to deep copy a view to a temporary module, make the desired changes to the view and its related entities, and then deep copy the view back to its original module.

Please Open CSR with repo steps to find out, what causes this WARNING MESSAGE & how to address as mentioned in the KB about the "desired changes to the view and its related entities, and then deep copy the view back to its original module"

Hope this helps!

Best Regards,

Rachel

2 Posts

August 19th, 2013 23:00

Hi Rachel,

Thank you so much.

I managed to reproduce the issue for the other report templates as well.

Yeah, I suspect that it could be a product behavior.

I will open a CSR to investigate deeper.

Thanks,

-Ken

No Events found!

Top