cconard96
commented
2 years ago I believe you are looking for Administration > Rules > Rules for assigning an item to an entity to control which entity an asset is added to when imported.
Closed VanAxl closed 2 years ago
cconard96
commented
2 years ago I believe you are looking for Administration > Rules > Rules for assigning an item to an entity to control which entity an asset is added to when imported.
VanAxl
commented
2 years ago Thanks for your reply. Well in fact there is no rules that can match this manual filing. My computers have just been put in some sub-entity "by hand". I just want them to stay where they are with that new GLPI-Agent . Here is the log in History tab of the asset, showing that the glpi-agent inventory has moved my computer :
Mika64
commented
2 years ago Same here for many hosts
trasher
commented
2 years ago Does issue occurs on migration, or when a new inventory occurs?
Mika64
commented
2 years ago That's happens on a new inventory. Old items (with no recent inventory) are not impacted.
trasher
commented
2 years ago Ok, then the issue title is wrong. The entities_id field should have been locked, since it's been edited by user.
2 solutions: an issue on plugin migration, or an issue on locking fields.
If you change by hand the entity on a computer; and run a new inventory on it, do you have the same behavior?
VanAxl
commented
2 years ago "If you change by hand the entity on a computer; and run a new inventory on it, do you have the same behavior?" => I've tried that, and it stays on the correct entity. I confirm that the migration has no impact for old devices : It will only move back the asset to the root entity when a new inventory (from the new glpi agent) is received for this asset.
Mika64
commented
2 years ago Here, we still use fusioninventory-agent
VanAxl
commented
2 years ago Maybe a workaround would be to force the entity_id to be locked for all assets (placed manually in a entity) before doing the migration, or at least before receiving any new GLpi-Agent inventory ? I'm not sure how to do this.
trasher
commented
2 years ago Agent is not relevant. This is an issue migrating from fi plugin. Have you installed and migrated to glpi-inventory-plugin? If so, there is something wrong in its migration.
If you did not activate the new plugin, nothing gets migrated; but you can add a global lock on entities_id field.
trasher
commented
2 years ago BTW, adding a global lock is certainly the way to go in your case; this will ensure inventory will never try to update the field. This feature is available since 10.0.1
VanAxl
commented
2 years ago Agent is not relevant. This is an issue migrating from fi plugin. Have you installed and migrated to glpi-inventory-plugin? If so, there is something wrong in its migration. If you did not activate the new plugin, nothing gets migrated; but you can add a global lock on
entities_idfield.
Yes for my tests, I used a computer that was linked to the production GLPI environnement (in 9.5). on that computer I've used the vbs script (glpi-agent-deployment.vbs) to uninstall and install the new glpi-agent , and point this agent to my test environment where I have the Migrated GLPI server (10.0.1) by the server= command argument.
I will try to test now with keeping the FI agent , and only change the server to report the inventory. I will see if it keeps my asset to the good entity. I'll keep you posted.
trasher
commented
2 years ago As I've already said, agent is not relevant
VanAxl
commented
2 years ago Ok you are right. Same result even when keeping the fusion inventory agent. Do know what I missed in the GLPI migration process. The glpi plugin has not really be "installed" in glpi, as it seems to be part of the system now, from my understanding. I just delete the old fusion inventory plugin from the Setup>plugins page.
Can you point me to the right direction to set that global Lock of the entity of my assets ? I can't find where to set this on, on my own.
trasher
commented
2 years ago There is a button in the inventory configuration page
VanAxl
commented
2 years ago There is a button in the inventory configuration page
ok thanks for that. I've found that page. But I didn't find the computer entity on the dropdown list, when trying to add a global lock
I 'm thinking about doing that in a different way. All my computers/assets have a user reported from the inventory (User field of the asset). Is it possible to create some kind of rule that will put the computer in the same entity as where the user is ? Cause my users are still in good entities.
trasher
commented
2 years ago Indeed, entity field is not available for global locks. As a workaround, you can try to insert directly in database:
INSERT INTO `glpi_lockedfields` (`itemtype`, `items_id`, `field`, `value`, `is_global`) VALUES
('Computer', 0, 'entities_id', NULL, 1);entities_id fields available on global locks. Initial issue can only be fixed with a migration of locked fields from fusioninventory plugin with glpiinventory plugin.trasher
commented
2 years ago In facts, glpi-inventory plugin already takes care of migrating locked fields; but was not taking care of old global locks. This will be fixed as of https://github.com/glpi-project/glpi-inventory-plugin/pull/128
cablop
commented
2 months ago We still see this issue in 10.0.12 with GLPI Inventory 1.3.5. We didn't have Fusion Inventory before. We locked the Entity field individualy for a test computer, and then globaly with the SQL mentioned above. And the inventory update just doesn't respect the locked field and just updates it.
In fact, it does not only change the entity field, but also changes the values in the soundcard and harddrives fields. Changing 7 to 0, and those are the ids of the entities too.
cedric-anne
commented
2 months ago @cablop Please open a new issue and give all requested information.
Code of Conduct
Is there an existing issue for this?
Version
10.0.1
Bug description
Hi, I've testing the migration from glpi 9.x to the version 10.0.1. Everything is working fine so far. So I did create a group policy to run the vbs script to install the GLPI agent 1.2 (with the option to uninstall the Fusion Inventory agent first). That works too.
But my computers are put in sub entity when they are created, I mean manually by the technician when he setup the computer for the first time, before providing it to the final user.. There is no rules for auto assignment.
And with this new GLPI agent, it moves automatically the computer to the root entity (we have such entity change in the history of the computer). That is very annoying cause we do have several hundred of computers in GLPI. So I would like to avoid to move again manually all my computer.
Is it a bug, or is there any settings to keep computer on their current entity ?
Thanks Nicolas
Relevant log output
No response
Page URL
No response
Steps To reproduce
Migrate GPI 9.5 to GLPI 10.0.1 update the GLPI agent on a test computer from FusionInventory to glpi agent 1.2 Run the agent on the computer, so it sends the inventory to the GLPI 10.0.1.
Then computer is changed to root entity.
Your GLPI setup information
Information about system installation and configuration
Server
Operating system: Linux Intranet 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64 PHP 8.0.19 apache2handler (Core, FFI, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, apache2handler, apcu, bz2, calendar, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, intl, json, ldap, libxml, mbstring, mysqli, mysqlnd, oci8, openssl, pcre, pdo_mysql, posix, readline, session, shmop, soap, sockets, sodium, standard, sysvmsg, sysvsem, sysvshm, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib) Setup: max_execution_time="30" memory_limit="64M" post_max_size="8M" safe_mode="" session.save_handler="files" upload_max_filesize="2M" Software: Apache/2.4.53 (Debian) (Apache/2.4.53 (Debian) Server at glpi.valve-precision.com Port 443 ) Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.5 Safari/605.1.15 Server Software: Debian 11 Server Version: 10.5.12-MariaDB-0+deb11u1 Server SQL Mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION Parameters: glpi@euvpfsql.euvpf.valve-precision.fr/glpiTmp Host info: euvpfsql.euvpf.valve-precision.fr via TCP/IP PHP version (8.0.19) is supported. Sessions configuration is OK. Allocated memory is sufficient. mysqli extension is installed. Following extensions are installed: dom, fileinfo, json, simplexml. curl extension is installed. gd extension is installed. intl extension is installed. libxml extension is installed. zlib extension is installed. The constant SODIUM_CRYPTO_AEAD_XCHACHA20POLY1305_IETF_NPUBBYTES is present. Database engine version (10.5.12) is supported. The log file has been created successfully. Write access to /usr/share/glpi/files/_cache has been validated. Write access to /usr/share/glpi/config has been validated. Write access to /usr/share/glpi/files/_cron has been validated. Write access to /usr/share/glpi/files has been validated. Write access to /usr/share/glpi/files/_dumps has been validated. Write access to /usr/share/glpi/files/_graphs has been validated. Write access to /usr/share/glpi/files/_lock has been validated. Write access to /usr/share/glpi/files/_pictures has been validated. Write access to /usr/share/glpi/files/_plugins has been validated. Write access to /usr/share/glpi/files/_rss has been validated. Write access to /usr/share/glpi/files/_sessions has been validated. Write access to /usr/share/glpi/files/_tmp has been validated. Write access to /usr/share/glpi/files/_uploads has been validated. Web access to the files directory should not be allowed but this cannot be checked automatically on this instance. Make sure access to error log file (/files/_log/php-errors.log) is forbidden; otherwise review .htaccess file and web server configuration. exif extension is installed. ldap extension is installed. openssl extension is installed. zip extension is installed. bz2 extension is installed. Zend OPcache extension is installed. Following extensions are installed: ctype, iconv, mbstring, sodium. Write access to /usr/share/glpi/marketplace has been validated. Timezones seems loaded in database.GLPI constants
Libraries
LDAP directories
SQL replicas
Notifications
Plugins list
fields Name: Additionnal fields Version: 1.8.2 State: Not installed archires Name: Architectures réseau Version: 2.6.0 State: Not installed datainjection Name: Data injection Version: 2.11.1 State: Enabled consumables Name: Demande de consommables Version: 1.6.0 State: Not installed formcreator Name: Form Creator Version: 2.12.2 State: Installed / not activated fusioninventory Name: FusionInventory Version: 9.5+3.0 State: Installed / not activated resources Name: Human Resources Version: 3.0.0 State: Enabled mreporting Name: More Reporting Version: 1.8.0 State: Enabled oauthimap Name: Oauth IMAP Version: 1.4.0 State: Enabled genericobject Name: Objects management Version: 2.11.0 State: Not installed order Name: Orders management Version: 2.9.0 State: Enabled reports Name: Rapports Version: 1.14.1 State: Installed / not activated manufacturersimports Name: Suppliers imports Version: 3.0.1 State: Enabled dashboard Name: Tableau de bord Version: 0.9.8 State: Not installedAnything else?
No response