Cloud Optimizer User Discussions
cancel

CO Failed to Retrieve Space Provisioned Information from vCenter

Valued Contributor.. ChongYC Valued Contributor..
Valued Contributor..

CO Failed to Retrieve Space Provisioned Information from vCenter

Hi All,

We are encountering issue on the CO where the space provisioned information came from vCenter showned as 0 GB and some of the VM retrieved wrong amount of disk info; E.g. 2.16 GB, 4.16 GB. 8.18 GB, & 16.16 GB. 

Any idea on what are the potential root causes that might lead to this issue?

Screenshot:

CO - Disk Issue - show 0.jpg

CO - Disk Issue - show wrong info.jpg

Thank you.

 

11 REPLIES
Micro Focus Expert
Micro Focus Expert

Re: CO Failed to Retrieve Space Provisioned Information from vCenter

Hello Chong YC,

There are some known issues with data collection for VMware environments.

If you are running CO 3.01, then I would suggest that you download the new patch that is available as of last week.

CO 3.01 Security Patch (Build 131)
https://softwaresupport.hpe.com/km/KM02782739

This patch includes a number of fixes that would resolve a data collection issue.

If you are using earlier versions of CO, then I would suggest either upgrading or if not possible, opening a support case so that we can confirm the issue and possibly provide hotfixes.

I hope that this information is helpful.

Regards,

Mark

---
Mark Butler
Micro Focus SW Support Engineer
https://softwaresupport.hpe.com/
Valued Contributor.. ChongYC Valued Contributor..
Valued Contributor..

Re: CO Failed to Retrieve Space Provisioned Information from vCenter

Hi Mark,

Noticed that the patch note stated that it will fix the issue on REST API call. Does it apply to CO portal as well?

"

Change Request: QCCR1A186893:
  Symptom:
    REST calls should not return DiskProvisioned" : 0.0 and "DiskUtil" : 0.0
    when DiskUsed is not zero. This issue occurs for VM's which are renamed or
    their vdisk stored in a datastore with folder name other than the VM name.
  Resolution:
    This has been fixed in Cloud Optimizer 3.01

"

Thanks

Micro Focus Expert
Micro Focus Expert

Re: CO Failed to Retrieve Space Provisioned Information from vCenter

Hello ChongYC,

In looking at the defect information, I can see that the problem was related to how the information was being requested from VMware.  Basically, the information was not being requested properly and thus it was returning wrong values.

Now that the information is being requested properly, the proper values are being returned and stored within the DB.  Because this issue is related to the original collection of the data, the fix will correct it within the CO UI as well as the Rest API call.

So, to answer your question, Yes.  This should fix the problem within the CO UI.

Regards,

Mark

---
Mark Butler
Micro Focus SW Support Engineer
https://softwaresupport.hpe.com/
Valued Contributor.. ChongYC Valued Contributor..
Valued Contributor..

Re: CO Failed to Retrieve Space Provisioned Information from vCenter

Hi Mark,

As advised, we have upgraded the CO from version 3.00 to 3.01. However, it doesn't help to resolve the issue.

By the way, we noticed that CO portal is actually able to retrieve the summary of disk information (on top left of the CO portal) but not in the individual VM list (as highlighted in the first post). 

Any other hints on why it still failed to retrieve proper information from VMware?

Thank you.

Micro Focus Expert
Micro Focus Expert

Re: CO Failed to Retrieve Space Provisioned Information from vCenter

Hello ChongYC,

Maybe I missed something, but did you upgrade from CO 3.00 to CO 3.01 by installing the CO 3.01 Update and then installing the Security patch (VPVINSTALLER_00007.tar) on top of CO 3.01?  That is the proper process since it is a patch to be placed on top of CO 3.01.

I hope that you do not have OA or OMi integrations with the older LCore because that would cause problems with CO 3.01.

In either case, at this point, I do not have anything more for you.  I would suggest that you open a support case at this point.

I'm sorry that I don't have a quick solution.

Regards,

Mark

---
Mark Butler
Micro Focus SW Support Engineer
https://softwaresupport.hpe.com/
Micro Focus Expert
Micro Focus Expert

Re: CO Failed to Retrieve Space Provisioned Information from vCenter

Hello ChongYC,

As I was thinking about it, one thing that may come into play is if VMtools is installed or not.  Also if it was installed and then removed, I don't know.  Just an idea.

Regards,

Mark

---
Mark Butler
Micro Focus SW Support Engineer
https://softwaresupport.hpe.com/
Valued Contributor.. ChongYC Valued Contributor..
Valued Contributor..

Re: CO Failed to Retrieve Space Provisioned Information from vCenter

Hi Mark,
Thanks for your information. We have upgraded to 3.01 without patching the latest security patch. Will perform the patch and hopefully it can resolve the issue.
By the way, what time zone are you in?
Micro Focus Expert
Micro Focus Expert

Re: CO Failed to Retrieve Space Provisioned Information from vCenter

Hello ChongYC,

I'm in U.S. Pacific Time Zone.  I'm in California.

Regards,

Mark

---
Mark Butler
Micro Focus SW Support Engineer
https://softwaresupport.hpe.com/
alexku85 Absent Member.
Absent Member.

Re: CO Failed to Retrieve Space Provisioned Information from vCenter

Hi Mark,

 

Would it be possible to purge the database and recollect from the datasource? ChongYC and myself have done the updates and the issue is still not resolved.

 

Regards,
Alex Ku

alexku85 Absent Member.
Absent Member.

Re: CO Failed to Retrieve Space Provisioned Information from vCenter

Hi Mark,

I have resorted to deploying a test CO Appliance and installed the update 3.01.131 before i added vCenter as a datasource. Once the data collection and analysis is completed, all VM across all datastore shows disk allocation of "0.00".

 

Thanks,

Alex Ku

Highlighted
Micro Focus Expert
Micro Focus Expert

Re: CO Failed to Retrieve Space Provisioned Information from vCenter

Hello Wahidovic,

What version of CO are you running?  Is it still CO 3.01.131?

The latest version is CO 3.04 and there have been a lot of fixes included within the updates.  In addition, there are new hotfixes available that can be provided by support.

There also may be an issue with the data collection process.  I do not believe that cleaning the database is the solution.

With CO 3.02 and later, there is a backup solution provided with the product (Ex. Backup_Restore.sh).  This did not exist in previous versions and it allows you to backup (and restore) the CO configuration, Vertica Database or both.  Information about the script is found within the OnlineHelp Guide for CO 3.02 and later.

I would highly recommend that you open a support case so that this issue could be investigated better.  I suggest the performing the following steps before you open a support case.  The references for pvsupport is for the PVTK utility which is available at the following location in case you do not have it installed already.

PVTK Utility:
https://softwaresupport.softwaregrp.com/km/KM02600652

A - Enable trace level logging for the Data Collection.
      Ex.  /opt/OV/contrib/PVTK/pvsupport.sh -trace collector:trace:20480:20
B - Reproduce the problem and let it run for several collection cycles (about 45 minutes at least) and collect an updated set of logs.
      Ex.  /opt/OV/contrib/PVTK/pvsupport.sh -grab
C - Open a support case and place the log collection on the FTP site for the case.
D - Once the issue has been reproduced, trace entries generated, and log files collected, then turn off tracing.
      Ex. #  /opt/OV/contrib/PVTK/pvsupport.sh -trace collector:info:20480:5

I hope that this information is helpful.

Regards,

Mark 

---
Mark Butler
Micro Focus SW Support Engineer
https://softwaresupport.hpe.com/