Task Deployement Computer Actor/Static group package

[EC2311]

Bug reporting acknowledgment

Yes, I read it

Professional support

None

Describe the bug

File not copied to the target computer set in static group (linked to package) but copied to the actor computer !!!
Cmd not executed on the target computer set in static group (linked to package)

To reproduce

1. I create a task to deploy .msi (glpi-agent1.15, for instance)
2. I create a static group with 1 computer
3. In _upload : I put a file
4. I create a deployement task : cible : the package. Actor : the GLPI server (not the computer in static group)

When agent runs on GLPI server : the deploiement task runs.
The copy is done from glpiserver TO glpiserver (in fact actor, I think) and not to Target Computer (the one set in package group!)

I think the command will be executed on actor computer (and not the computer set in package group

Expected behavior

I think the deploiement task must take care of Group computer defined in package and not the one defined as Actor.
I think the actor is the one to execute the actions to the computers defined in package

Operating system

Windows

GLPI Agent version

v1.15

GLPI version

10.0.18

GLPIInventory plugin or other plugin version

No response

Additional context

No response

[EC2311]

I think I have understood the way it runs
So perhaps it's not a bug, but it runs not really like 'collect' :

In the actors we have to define the group inventory and not glpi server...
I tought the glpiserver was actor to send the package, but no

[EC2311]

When we look at the target computer (in glpi) in "deploiement package" : we can see : no package to download. why not...I suppose it's linked to the tasks (deploiement) for which the computer is defined ? But adding a new package on the task : always 'no package to download'...

but how can we get the inventory of packages downloaded ?

[g-bougard]

Hi @EC2311

you clearly misunderstood the way things run: actors are glpi-agent running on computer.

The "no package to download" may mean the package has still been downloaded and it cached locally.

Also, don't try to install glpi-agent this way without knowing what you're doing: if you install glpi-agent while running the task, it will be aborted as the installer will require to stop the service. The only way to upgrade glpi-agent using glpi-agent deploy task is to copy the installer, and schedule a windows job which will run the installer after the task is finished.

[EC2311]

hi @g-bougard
thanks for your reply and advice

How do you explain deploiement task runs at every inventory of the target computer ? we don't have to install software at every inventory, but only if the package hadn't been installed successfully ?
Do we have to test (value and so on) in the package itself ?

If we take the example (to push glpi-agent with a task to isntall it) : does the package have to contain task to test if it is already isntalled in fact ?

Does the deploiement run through proxy fonction too?
Thanks

[g-bougard]

Hi @EC2311

when glpi-agent runs all its tasks, it just asks server if each task has to be run. This includes inventory task but also all enabled tasks, including deploy.

In glpi-inventory-plugin, you may have to create a dynamic group with criteria to check glpi-agent version: for example, if glpi-agent version doesn't contain 1.15, it can gives you the group of computers requiring the installation of glpi-agent v1.15. So if glpi-agent is still 1.15, when it will ask glpi server if it has to run deploy task, the server won't include this task.

Or you can also check yourself in the task script if the upgrade have to be run. This way, the task will be run each time, but will finish quickly if agent is up-to-date. You can even use the official vbs which always makes this check: https://glpi-agent.readthedocs.io/en/latest/installation/index.html#large-installations

Actually, only inventory runs via glpi-agent proxy. If you use a http proxy, this should work.

[EC2311]

About proxy, I talked about proxy definition set in glpi-agent : will the package defined in glpi-server will be sent through the proxy glpi-agent ?
A great thanks for your replies and your job !

[g-bougard]

I think I still answered:

Actually, only inventory runs via glpi-agent proxy.