Project

General

Profile

Actions

Bug #15487

closed

Openvz/Virtuozzo virtual machine detected as Physical

Added by Victor Héry over 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Web - Nodes & inventories
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
27
Name check:
To do
Fix check:
To do
Regression:

Description

Hello!

I use rudder agent v5.0.12, all hosts are debian 9

I have noticed a problem with virtuozzo container detected as physical machine, despite the inventory state they are Virtuozzo guest.

I have the problem on 5 containers, while 16 others are correctly detected as Virtual

For correct and incorrect hosts, rudder agent inventory -v return:

verbose: This appears to be an OpenVZ/Virtuozzo/Parallels Cloud Server guest system.

But for incorrect hosts, final inventory contains

<VMSYSTEM>Physical</VMSYSTEM>

While correct hosts contains

<VMSYSTEM>Virtuozzo</VMSYSTEM>

I am unsure of the reason, reseach of same problem on the bugtracker seems to have been solved long time ago.

Both containers are identical, same RAM, same CPU, same uers, etc. I failed to find a links between incorrect hosts, the only difference I see in inventory is the field <UUID> which is missing in the "Physical host" inventory in the <HARDWARE> section.

Full hardware section for incorrect host:

    <HARDWARE>
      <ARCHNAME>x86_64-linux-gnu-thread-multi</ARCHNAME>
      <CHECKSUM>131071</CHECKSUM>
      <DATELASTLOGGEDUSER>Fri Aug 16 10:55</DATELASTLOGGEDUSER>
      <DEFAULTGATEWAY>xxx.xxx.xxx.xxx</DEFAULTGATEWAY>
      <DNS>xxx.xxx.xxx.xxx</DNS>
      <ETIME>2</ETIME>
      <IPADDR>xxx.xxx.xxx.xxx</IPADDR>
      <LASTLOGGEDUSER>root</LASTLOGGEDUSER>
      <MEMORY>1512</MEMORY>
      <NAME>mail-server</NAME>
      <OSCOMMENTS>#1 SMP Fri Jan 5 21:20:16 MSK 2018</OSCOMMENTS>
      <OSNAME>Debian GNU/Linux 9.9 (stretch)</OSNAME>
      <OSVERSION>3.10.0-693.11.6.vz7.40.4</OSVERSION>
      <PROCESSORN>1</PROCESSORN>
      <PROCESSORS>3400</PROCESSORS>
      <PROCESSORT>Intel(R) Pentium(R) CPU G3450 @ 3.40GHz</PROCESSORT>
      <USERID>root</USERID>
      <VMSYSTEM>Physical</VMSYSTEM>
      <WORKGROUP>xxxx</WORKGROUP>
    </HARDWARE>

And for correct host:

    <HARDWARE>
      <ARCHNAME>x86_64-linux-gnu-thread-multi</ARCHNAME>
      <CHECKSUM>131071</CHECKSUM>
      <DATELASTLOGGEDUSER>Fri Aug 16 10:34</DATELASTLOGGEDUSER>
      <DEFAULTGATEWAY>xxx.xxx.xxx.xxx</DEFAULTGATEWAY>
      <DNS>xxx.xxx.xxx.xxx</DNS>
      <ETIME>3</ETIME>
      <IPADDR>xxx.xxx.xxx.xxx</IPADDR>
      <LASTLOGGEDUSER>root</LASTLOGGEDUSER>
      <MEMORY>1024</MEMORY>
      <NAME>monitoring</NAME>
      <OSCOMMENTS>#1 SMP Fri Jan 5 21:20:16 MSK 2018</OSCOMMENTS>
      <OSNAME>Debian GNU/Linux 9.9 (stretch)</OSNAME>
      <OSVERSION>4.9.0</OSVERSION>
      <PROCESSORN>1</PROCESSORN>
      <PROCESSORS>2670</PROCESSORS>
      <PROCESSORT>Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz</PROCESSORT>
      <USERID>root</USERID>
      <UUID>-8</UUID>
      <VMSYSTEM>Virtuozzo</VMSYSTEM>
      <WORKGROUP>xxxx</WORKGROUP>
    </HARDWARE>

If you have any idea it would be very appreciated!

I am available to answer any question if you need more details

Thanks you!


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #15492: rudder agent on Virtuozzo/openvz hypervisors uses broken vzpsResolvedActions
Actions #1

Updated by Alexis Mousset over 4 years ago

  • Related to Bug #15492: rudder agent on Virtuozzo/openvz hypervisors uses broken vzps added
Actions #2

Updated by Alexis Mousset over 4 years ago

  • Description updated (diff)
  • Category set to Web - Nodes & inventories
  • Target version set to 5.0.13
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 32
Actions #3

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions #4

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.14 to 5.0.15
Actions #5

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
  • Priority changed from 32 to 31
Actions #6

Updated by Alexis Mousset about 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
  • Priority changed from 31 to 30
Actions #7

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
  • Priority changed from 30 to 29
Actions #8

Updated by François ARMAND almost 4 years ago

  • Priority changed from 29 to 28

Was it corrected with the upstream solution in openvz posted in #15492 ?

Actions #9

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
  • Priority changed from 28 to 27
Actions #10

Updated by Nicolas CHARLES over 3 years ago

Hi Victor

To debug this issue, we'd need ideally the full inventory, or if you can't at least the BIOS part, and also the content of

/proc/self/status
, to check if there are lines envID:sth with sth>0

Also, do they both have virsh and/or vzlist in path?

Thank you in advance

Actions #11

Updated by Victor Héry over 3 years ago

Hi Nicolas, François,

I am sorry, it seems I missed the notifications regarding your questions!

I have rechecked my hosts, since the start of the ticket I migrate everything to rudder 6.0 and all openvz container are correctly reporting Virtual now.

I am unsure if this is because the 6.0 or the https://issues.rudder.io/issues/15492 but I guess if the 15492 solved it, I would have closed the ticket at the time as I am also the reporter of 15492 ^^"

Unfortunately I have no physical server available to test a full Virtuozzo reinstall and test on rudder 5, sorry. But I think is may be closed as the problem has disappear in rudder 6?

If you still need the information you ask for Nicolas, tell me I'll extract it.

Hope it helps, again sorry for the delay.

Regards,

Actions #12

Updated by François ARMAND over 3 years ago

  • Status changed from New to Resolved

Yes, I think we can close it: 5.0 is not supported anymore and 6.0 fix it => it's fixed :)

Thanks for having taken the time to tell us it is now OK.

Actions

Also available in: Atom PDF