You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 4, 2024. It is now read-only.
Whatever asset imported inside GLPI by FI4G (a computer, a network device, a network printer, etc.) has associated a XML file under the files/_plugins/fusioninventory/xml directory that contains information (information that is sent by FIA) about it. This is an example of files/_plugins/fusioninventory/xml for three assets.
As I commented in issue Asset import XML file is not deleted when the asset is delete permanently(#2549), this tree structure is true for new FI4G installations (v9.2+2.0 and above). If your system is the result of successive update processes then you probably have a more similar structure to this one, with XML files without .xml extension.
Even if issues #2549 and #2034 are resolved there is another one regarding XML files without .xml extension. Let's assume the following case in a recently system updated to GLPI v9.2.3 and FI4G v9.2+2.2.
The files/_plugins/fusioninventory/xml/computer/0/1 file is the import XML file of computer with Id=0, which has not yet been inventoried with the new system. When the computer is re-inventoried the following happens.
Computer with Id=0 is linked with files/_plugins/fusioninventory/xml/computer/0/1.xml and files/_plugins/fusioninventory/xml/computer/0/1 remains orphaned.
FI4G should remove the current (old) import XML file before to import (and to create) the new one. In this case, the files/_plugins/fusioninventory/xml/computer/0/1 file should have been deleted.
Regards,
The text was updated successfully, but these errors were encountered:
The environment
This is the information about system installation and configuration.
The issue
Whatever asset imported inside GLPI by FI4G (a computer, a network device, a network printer, etc.) has associated a XML file under the
files/_plugins/fusioninventory/xml
directory that contains information (information that is sent by FIA) about it. This is an example offiles/_plugins/fusioninventory/xml
for three assets.[root@ilab glpi]# tree files/_plugins/fusioninventory/xml/ files/_plugins/fusioninventory/xml/ ├── computer │ └── 0 │ └── 1.xml ├── networkequipment │ └── 1 │ └── 17.xml └── printer └── 2 └── 23.xml
As I commented in issue Asset import XML file is not deleted when the asset is delete permanently(#2549), this tree structure is true for new FI4G installations (v9.2+2.0 and above). If your system is the result of successive update processes then you probably have a more similar structure to this one, with XML files without
.xml
extension.Even if issues #2549 and #2034 are resolved there is another one regarding XML files without
.xml
extension. Let's assume the following case in a recently system updated to GLPI v9.2.3 and FI4G v9.2+2.2.The
files/_plugins/fusioninventory/xml/computer/0/1
file is the import XML file of computer with Id=0, which has not yet been inventoried with the new system. When the computer is re-inventoried the following happens.Computer with Id=0 is linked with
files/_plugins/fusioninventory/xml/computer/0/1.xml
andfiles/_plugins/fusioninventory/xml/computer/0/1
remains orphaned.FI4G should remove the current (old) import XML file before to import (and to create) the new one. In this case, the
files/_plugins/fusioninventory/xml/computer/0/1
file should have been deleted.Regards,
The text was updated successfully, but these errors were encountered: