cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Melnik (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-10125) Usage Server shows incorrect amount of RAM
Date Tue, 31 Oct 2017 12:57:00 GMT
Vladimir Melnik created CLOUDSTACK-10125:
--------------------------------------------

             Summary: Usage Server shows incorrect amount of RAM
                 Key: CLOUDSTACK-10125
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10125
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Usage
    Affects Versions: 4.9.0
         Environment: CentOS-6.8-x64
            Reporter: Vladimir Melnik
            Priority: Critical


I don't know, how to reproduce it, but the usage server reports incorrect amount of RAM for
one of several hundreds VMs: it has 4 GB of RAM, but 8 GB are being reported:

{{<virtualmachine>
  <id>a4d03771-7267-4281-b615-d5cbae6c6e39</id>
  <name>VM-a4d03771-7267-4281-b615-d5cbae6c6e39</name>
  <displayname>VM-a4d03771-7267-4281-b615-d5cbae6c6e39</displayname>
  <account>admin</account>
  <userid>87417805-cc3c-4244-bdde-ce35d5f83d19</userid>
  <username>admin</username>
  <domainid>e681b2ae-7d10-44d9-befc-c0facc34cf64</domainid>
  <domain>A201***</domain>
  <created>2017-02-22T15:58:56+0200</created>
  <state>Running</state>
  <haenable>false</haenable>
  <zoneid>c8d773fa-76ca-4637-8ecf-88656444fc86</zoneid>
  <zonename>z2.tucha13.net</zonename>
  <hostid>ed5a7c16-adf3-453a-9238-23c9e2697eb5</hostid>
  <hostname>h3.c1.p1.z2.tucha13.net</hostname>
  <templateid>3a8dfd95-96c1-4d86-8365-9645a9ea7996</templateid>
  <templatename>windows-server-2012-r2-x64-russian</templatename>
  <templatedisplaytext>Microsoft Windows Server 2012 R2 x64 Russian</templatedisplaytext>
  <passwordenabled>false</passwordenabled>
  <serviceofferingid>5248afa9-f896-4608-bf3b-316262c21b9d</serviceofferingid>
  <serviceofferingname>custom-ssd-a1</serviceofferingname>
  <diskofferingid>a7c8489e-214f-41b0-90fc-1a0f5ac537cb</diskofferingid>
  <diskofferingname>custom-tier-a</diskofferingname>
  <cpunumber>2</cpunumber>
  <cpuspeed>2499</cpuspeed>
  <memory>4096</memory>
  <cpuused>1.39%</cpuused>
  <networkkbsread>188561</networkkbsread>
  <networkkbswrite>112379</networkkbswrite>
  <diskkbsread>4930471</diskkbsread>
  <diskkbswrite>3153415</diskkbswrite>
  <memorykbs>4194304</memorykbs>
  <memoryintfreekbs>4235640</memoryintfreekbs>
  <memorytargetkbs>4194304</memorytargetkbs>
  <diskioread>231433</diskioread>
  <diskiowrite>128710</diskiowrite>
  <guestosid>b5490e1c-bd31-11e6-b74f-06973a00088a</guestosid>
  <rootdeviceid>0</rootdeviceid>
  <rootdevicetype>ROOT</rootdevicetype>
  <nic>
    <id>29e08f6e-8649-4b1b-bda2-a7872f69485a</id>
    <networkid>e4a97b82-c7c1-420d-b77f-987881064e0b</networkid>
    <networkname>NET-PUB-193.151.***.0-24</networkname>
    <netmask>255.255.255.0</netmask>
    <gateway>193.151.***.***</gateway>
    <ipaddress>193.151.***.***</ipaddress>
    <isolationuri>vlan://***</isolationuri>
    <broadcasturi>vlan://***</broadcasturi>
    <traffictype>Guest</traffictype>
    <type>Shared</type>
    <isdefault>true</isdefault>
    <macaddress>06:b9:d0***:***:***</macaddress>
  </nic>
  <hypervisor>KVM</hypervisor>
  <instancename>i-1251-386-VM</instancename>
  <displayvm>true</displayvm>
  <isdynamicallyscalable>false</isdynamicallyscalable>
  <ostypeid>168</ostypeid>
</virtualmachine>
}}

{{
<listusagerecordsresponse cloud-stack-version="4.9.0">
  <count>1</count>
  <usagerecord>
    <account>admin</account>
    <accountid>10aa1795-e315-46e7-a09a-3712acb51962</accountid>
    <domainid>e681b2ae-7d10-44d9-befc-c0facc34cf64</domainid>
    <zoneid>c8d773fa-76ca-4637-8ecf-88656444fc86</zoneid>
    <description>VM-a4d03771-7267-4281-b615-d5cbae6c6e39 allocated (ServiceOffering:
231) (Template: 203)</description>
    <usage>24 Hrs</usage>
    <usagetype>2</usagetype>
    <rawusage>24</rawusage>
    <virtualmachineid>a4d03771-7267-4281-b615-d5cbae6c6e39</virtualmachineid>
    <name>VM-a4d03771-7267-4281-b615-d5cbae6c6e39</name>
    <offeringid>5248afa9-f896-4608-bf3b-316262c21b9d</offeringid>
    <templateid>3a8dfd95-96c1-4d86-8365-9645a9ea7996</templateid>
    <usageid>a4d03771-7267-4281-b615-d5cbae6c6e39</usageid>
    <type>KVM</type>
    <cpunumber>2</cpunumber>
    <cpuspeed>2400</cpuspeed>
    <memory>8192</memory>
    <startdate>2017-10-30'T'00:00:00+00:00</startdate>
    <enddate>2017-10-30'T'23:59:59+00:00</enddate>
  </usagerecord>
</listusagerecordsresponse>
}}

Could I provide with more information that would help to find and fix the issue? I'd be glad
to!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message