Loading...

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Undefined
Fix Version/s: CNV v4.20.z
Affects Version/s: None
Component/s: CNV Install, Upgrade and Operators
Labels:
None

Activity Type:
Quality / Stability / Reliability
Story Points:
0.42
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Component Fix Version(s):
None
Market:

Sprint:
CNV I/U Operators Sprint 272, CNV I/U Operators Sprint 273, CNV I/U Operators Sprint 274, CNV I/U Operators Sprint 275, CNV I/U Operators Sprint 276, CNV I/U Operators Sprint 277, CNV I/U Operators Sprint 278
Customer Impact:

Customer Reported

Regression:
None

SFDC Cases Links:
SFDC Cases Open:
SFDC Cases Counter:

PX Impact Score:

Description of problem:

When running the metric, the information for windows vms not listed with the information.

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

4.19

How reproducible:

Steps to Reproduce:

1.Create a windows vm.
2.Check for the metric result

Actual results:

Nothing

Expected results:

The value of used memory in bytes of the vm.

Additional info:

When running the command virsh dommemstat on windows vm virt-launcher I get less information than linux vm, the available field is missing so maybe this is why the metric is not working for windows vms, because this is the information it seeks but it is not there.