Bug #10265
closedRedhat Openstack Nova compute QEMU virtual machines are seen as physical
Description
Hi,
I have virtual machines on Redhat Openstack Nova compute considered as physical.
Regards
Files
Updated by I C almost 8 years ago
Updated by Benoît PECCATTE almost 8 years ago
- Found in version (s) 4.1.0~beta3 added
Updated by Benoît PECCATTE almost 8 years ago
- Found in version(s) old deleted (
4.1.0.beta3)
Updated by Nicolas CHARLES almost 8 years ago
Hello Ilan,
This looks a lot like http://www.rudder-project.org/redmine/issues/9052
Can you upload the inventory (it may contain sensitive information, so I understand if it's not possible)?
To debug this issue, do you have a file /var/log/dmesg, with any relevant content in it (actually, the content of dmesg), or simply "(Nothing has been logged yet.)" ?
In the inventory, what is the content of BIOS/SMANUFACTURER entry ?
Kind regards,
Nicolas
Updated by I C almost 8 years ago
Hello Nicolas,
Here is the Bios part of inventory :
<BIOS>
<ASSETTAG /> <BDATE>04/01/2014</BDATE>
<BMANUFACTURER>SeaBIOS</BMANUFACTURER>
<BVERSION>1.9.1-5.el7</BVERSION>
<MMANUFACTURER /> <MMODEL /> <MSN /> <SKUNUMBER /> <SMANUFACTURER>Red Hat</SMANUFACTURER>
<SMODEL>OpenStack Compute</SMODEL>
<SSN>e1622fe8-eb7d-44d0-a2d5-7ce6991b2120</SSN>
</BIOS>
Dmesg is already in attachment to this issue, maybe is not what you expect ?
Thansk
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 4.1.0~rc1 to 4.1.0
Updated by Nicolas CHARLES almost 8 years ago
Hello Ilan,
For dmesg, I need to be sure if you have actual content in file /var/log/dmesg, or if it's an empty file, because based on the dmesg you sent, it should be correctly detected as QEMU/KVM
Kind regards
Updated by François ARMAND almost 8 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Getting started - demo | first install | level 1 Techniques
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.0 to 4.1.1
Updated by Nicolas CHARLES over 7 years ago
Ilan,
I fail to reproduce it - it may have been fixed by https://www.rudder-project.org/redmine/issues/9763
Could you check with an agent in version 4.1 final to see if it still happen ?
Kind regards,
Nicolas
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.1 to 4.1.2
- Priority changed from 35 to 34
Updated by I C over 7 years ago
Hi Nicolas,
I have checked with agent 4.1.1 and it is the same problem.
Machine type is "physical"
Best regards,
Ilan
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.2 to 4.1.3
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.3 to 4.1.4
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.4 to 4.1.5
- Priority changed from 34 to 33
Updated by Alexis Mousset over 7 years ago
- Target version changed from 4.1.5 to 4.1.6
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.6 to 4.1.7
- Priority changed from 48 to 47
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.7 to 4.1.8
- Priority changed from 47 to 46
Updated by I C over 7 years ago
- File rudder-agent1-5573be84-d36e-4d98-b72f-17abe3963d33.ocs rudder-agent1-5573be84-d36e-4d98-b72f-17abe3963d33.ocs added
Hi,
More information,
Debian 8 detected as Physical Machine with Rudder agent 4.1.6-jessie0 (CFEngine Core 3.10.0)
And all other are detected as Virtual Machine :
Centos 7Rudder agent 4.1.6.release (CFEngine Core 3.10.0)
Ubuntu 16.04 Rudder agent 4.1.6-xenial0 (CFEngine Core 3.10.0)
Debian 9 Rudder agent 4.1.8~rc1~git201709050155-stretch0 (CFEngine Core 3.10.2)
You can look at the debian 8 inventory in attachment.
Thanks
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.8 to 4.1.9
- Priority changed from 46 to 45
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.9 to 4.1.10
- Priority changed from 45 to 44
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.10 to 4.1.11
- Priority changed from 44 to 42
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.11 to 4.1.12
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.12 to 4.1.13
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.13 to 4.1.14
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.1.14 to 4.1.15
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.15 to 4.1.16
Updated by Benoît PECCATTE about 6 years ago
- Translation missing: en.field_tag_list set to Sponsored
- Priority changed from 42 to 69
Updated by François ARMAND about 6 years ago
- Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
- Priority changed from 69 to 85
I'm requalifying that as major, because it breaks the configuration of hardware-based groups, and there is no workaround.
Updated by François ARMAND about 6 years ago
- Assignee set to Nicolas CHARLES
We will try to reproduce on site.
Updated by Nicolas CHARLES about 6 years ago
File /var/log/dmesg is empty on debian 8 - causing invalid detection
see https://github.com/fusioninventory/fusioninventory-agent/pull/594
Updated by Nicolas CHARLES about 6 years ago
- Status changed from New to In progress
Updated by Nicolas CHARLES about 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/1702
Updated by Nicolas CHARLES about 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|4c93473a87dfd52d70441c31d98eb7e64ed663f7.
Updated by Vincent MEMBRÉ about 6 years ago
- Status changed from Pending release to Released