Duplicate entries or no inventory

[GuidoWilden]

Bug reporting acknowledgment

Yes, I read it

Professional support

None

Describe the bug

We are again troubled by the duplicate entry issue. The moment I change something (let's say the hostname) in the inventory I get a second entry on the next inventory run. I got around this by adjusting the rules but as a result those machines are now being ignored on inventory.

To reproduce

Disable Computer Import (by name) and run an inventory.

Expected behavior

Inventory should still be collected.

Operating system

Linux

GLPI Agent version

Nightly build (git version in additional context below)

GLPI version

Other (Details in additional context below)

GLPIInventory plugin or other plugin version

Other (Details in additional context below)

Additional context

GLPI v11.0.1, GLPI inventory plugin 1.6, GLPI agent v1.16-gitd4dff6bd

[Rico29]

Hello,
Having the same problem, already reported in https://forum.glpi-project.org/viewtopic.php?id=293276 but no response

Regards

[GuidoWilden]

@Rico29 did you ever get a response? Very unusual. On here I always got a response within a couple of hours.

[Rico29]

Hi @GuidoWilden
I get some responses on https://forum.glpi-project.org/viewtopic.php?id=293276

Regards
Cédric

[g-bougard]

Hi,

sorry for the late response, but I was busy on a new feature and professional support.

I also read your forum thread and here I have some comments as first this issue report is wrongly defined:

• you said the problem occurs because of a changing import rule in GLPI and I see in the forum thread you played a lot with update and import rules. As far I understand, by now, you have totally broken the update and import rules order. This is critical: you should definitively reset the rules order as part of your problem is there and we won't be able to help you if you have a broken rules order.
• I saw in the forum thread the problem may also be related to VM and you don't speak about that here and even worse, you don't say what kind of virtualization you're using. This may be part of the problem too. Please clarify.

To show you the rules order is critical, it seems you prioritized the "Update computer (by uuid)" and "Update computer (by name)" rule against the others. It means for example if an inventory comes with an UUID still found in GLPI, it will update the computer: this rule means name will be overrided, if a computer is found with a serial in GLPI but the inventory don't have a serial, the serial will be removed, if the found computer don't have a serial but the inventory has one, the serial will be set.

Also it seems you enable the "Create computer for virtual machines" option, this may be a big part of your problem: it means computers will be created for all VMs when importing host computer inventory. It means also GLPI emulates a computer inventory which may not have all required datas to be imported or updated the same way it would be if an agent runs inside... So this may create some trouble with update and import rules for computers updated and imported at the same time from the host VM inventory and from a running glpi-agent.

I understand why you enabled the option but before changing update and import rules, you have to study what happen for the first case you reported:

• check what is seen between name, uuid and serial in the reported virtualmachine in the host inventory
• check what is seen for name, uuid and serial when agent is run in it.

If your original problem is more the name is reset for a computer which doesn't have an agent running, check what data is seen from virtualmachine host inventory.

[g-bougard]

Also, does #1035 related to this issue ?

[GuidoWilden]

Hi @g-bougard, I assumed that you were busy.
My problem is a little different as I am seeing it only with bare metal machines (not VMs). I will have to take another look at the rules once more. It's been so long that I forgot what it actually was. Luckily I still have a switched off vanilla GLPI instance that has all the default rules still intact so I have something to compare it to.
Saying that, is there a way in GLPI to reset all the rules to default? Would be good to have. Even better if it as possible per category (Computers, Monitors etc.)

[g-bougard]

Hi @GuidoWilden

I didn't understood you also had such a problem. If the context is different, please open another issue.

About resetting rules, a button exists for that at the bottom of the page, just on the left of the "Test rules engine" button (it may be masked partially in GLPI v11, see glpi-project/glpi#22108). I think it resets all rules. You can also export/import rules, so make a backup before resetting and even before changing any ordre.

[GuidoWilden]

I do not seem to see this button. Also tried Debug mode but no reset button.

[GuidoWilden]

Oh and I opened this issue initially.

[g-bougard]

Oh and I opened this issue initially.

Oh, I saw Rico29 message as last one and though he was the author, my bad. And then I mixed his case and yours in my head and I literally freeze my mind, my second bad: Rico29 problem is than better #1035 and in the forum.

About your screenshot, I see the button is missing, maybe a role is missing in your profile.
Also about your screenshot, to me, it seems it leaks few information and I think you can remove it now.

[Rico29]

@GuidoWilden sorry for your issue hijacking, wasn't my goal.
@g-bougard I've reset the import rules. But I still don't understand how is it possible, with default import rules, to have two hosts with same "name" and same "uuid".

Problem appears on VMs that have glpi-agent running on it.
I'll try to debug more this week.
Regards

[g-bougard]

Hi @Rico29,
is your own issue related to #1035 or not ? If yes, we will better continue there or we will continue in another.

[Rico29]

Nope, it's a different issue

[Rico29]

Found something, maybe related. Let me explain.

On some of my proxmox servers, I changed the name on some VMs (in proxmox, and on the VM OS itself). old name is "OLDNAME" and new name is "NEWNAME".

There's not any occurences of "OLDNAME", neither on proxmox, neither on the VM itself.
When running glpi-agent on the VM, it updates the computer named "NEWNAME".
When running glpi-agent on the proxmox supporting the vm, it updates the computer named "OLDNAME".

Both computers in GLPI have the same UUID, but different names.
=> glpi-agent get the VMs name by listing host processes. So until the VM has not been stop / start in proxmox, the old name is still used by the inventory task ran on proxmox server.

I think it would be more consistent to use proxmox tools to get VM ids / name when running proxmox virtualization.

For now I'll stop / start the VMs on which I changed the name to see if it helps.

Regards,
Cédric