All the fields in Datastore on RHV providers displays 0.

[jarovo]

Description of problem:
The fields in Datastore on RHV providers:
All Files

• VM Provisioned Disk Files
• VM Snapshot Files
• VM Memory Files
• Other VM Files
• Non-VM Files

all contain 0. If it is the case that CFME couldn't obtain the required information to display correct number, it should not display 0 but "N/A" or something in that sense.

Note the BZ
https://bugzilla.redhat.com/show_bug.cgi?id=1429935

Version-Release number of selected component (if applicable):
5.11.7.0.20200714215453_0da8a4a

How reproducible:
1/1 for RHV provider 4.4 and 4.3

Steps to Reproduce:

1. Add a provider, wait for its population
2. Check any datastore in it

Actual results:
The "Content" table displays 0 for every field.

Expected results:
actual number or information that the count coudln'T be determined.

Additional info:

[gtanzillo]

@JaryN Can you please confirm whether these values are actually 0 in the DB, or nil?

[jarovo]

I will need to know which table to look at.

…

On Thu, Jul 23, 2020 at 7:53 PM Gregg Tanzillo ***@***.***> wrote: @JaryN <https://github.com/jaryn> Can you please confirm whether these values are actually 0 in the DB, or nil? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#20366 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJB3QPP6XOIWIV3OHOB6EDR5B2JPANCNFSM4O6RL6JA> .

-- Insanity: doing the same thing over and over and expecting a different result. Engineering: doing the same thing over and over and hoping for the same result.

[agrare]

Hey @JaryN it'll be in the storage_files table where the storage_id matches the storage record for the RHV datastore

[agrare]

This isn't rhv specific, I see the same thing on VMware datastores.

This just means that datastore smartstate hasn't run and we haven't collected any of these files. @h-kataria this is a similar issue that we were talking about with the VM details page so I'll assign it to you if you want to use the last_scan_on attribute to show N/A vs. 0 but I think its a pretty low priority.

[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.