Page 1 of 1
[SOLVED] Agent maturities=PREPROD
Published: September 14, 2022 - 12:25 PM
by Information Service
Server version: wapt 2.2.1.11957
Agent version: wapt 2.2.1
Hello,
I have an agent (TEST) with the option maturities=PREPROD.
I have packages with a PREPROD maturity level;
the packages are assigned to it but are not visible in the list of packages to install.
If I change the agent's maturity level to PROD, all the packages are visible.
Any idea what my configuration might be wrong with?
Re: Agent maturities=PREPROD
Published: September 19, 2022 - 2:56 PM
by Information Service
Quick update: the DEV maturity is working well, but not the PREPROD.
Have a good day.
Re: Agent maturities=PREPROD
Published: September 19, 2022 - 4:09 PM
by dcardon
I didn't quite understand the problem. Maturity matching is simply string matching. You just need to be careful because the accepted maturities are those listed in `maturities`. If you want PREPROD and PROD, you need to specify them
Sincerely,
Denis
Re: Agent maturities=PREPROD
Published: September 20, 2022 - 11:14 AM
by Information Service
Version: 2.2.1.11957
Hello,
I know, nothing complicated.
Server:
package: Add fr local in PREPROD and applied to my machine.
Agent:
maturity option: PREPROD then service reboot.
I refreshed the agent but the pending package doesn't appear in the console.
I do the same thing in DEV maturity => OK
and I just tested with version 2.2.2.12388, same result.
Re: Agent maturities=PREPROD
Published: September 20, 2022 - 5:10 PM
by sfonteneau
Re: Agent maturities=PREPROD
Published: September 22, 2022 - 2:05 PM
by Information Service
Back again.
Apparently the problem was on my test machine. A complete reinstallation of the agent, including the removal of residual files, and everything is working fine.
Thank you.