[SOLVED] wapt agent and repo_rules

[guigeek]

Hello,
I'm setting up secondary repositories on all sites.
Everything works with the secondary repositories themselves.
However, in the agent configuration, `use_repo_rules` is always set to `false`.

I've regenerated the agent several times, checking the "Use repository access rules" option, but it doesn't change anything.

Have I missed something?

Thanks!

PS: I'm on version 2.3 on a Debian Buster server.

[jdziadek]

Hello, if I'm not mistaken, the agent configuration will only apply to future installations. If you want to modify existing installations, you need to edit the wapt-conf-policy package.

[guigeek]

Yes, but I pushed the waptupgrade package to all machines and it didn't change the use_repo_rules variable

[jdziadek]

Yes, but I pushed the waptupgrade package to all machines and it didn't change the use_repo_rules variable.

It's not the waptupgrade, it's the "tis-wapt-conf-policy" package

[sfonteneau]

Hello,

could you please specify whether you are using the enterprise version of wapt (licensed version), or the discovery version?

[guigeek]

In the enterprise version, but indeed, by retrieving the wapt-conf-policy package and adapting it for my needs, I was able to set the use_repo_rules variable to False everywhere.

Now I don't understand why my agents are finding 0 available packages on the remote repositories even though the rules are configured and synchronization is complete.

[jdziadek]

in the enterprise version, but indeed, by retrieving the wapt-conf-policy package and adapting it for my needs, I was able to set the use_repo_rules variable to False everywhere.

Now I don't understand why my agents are finding 0 available packages on the remote repositories even though the rules are configured and the synchronization is also in place.

I don't know if this will help, but I had a problem with my rules.
For example, if I used the IP address 192.168.0.1/13 to retrieve all IP addresses in the 192.168.XX range, it didn't work, but using 192.168.0.0/13 worked immediately.

[sfonteneau]

in the enterprise version, but indeed, by retrieving the wapt-conf-policy package and adapting it for my needs, I was able to set the use_repo_rules variable to False everywhere.

Now I don't understand why my agents are finding 0 available packages on the remote repositories even though the rules are configured and the synchronization is also in place.

I don't know if this will help, but I had a problem with my rules.
For example, if I used the IP address 192.168.0.1/13 to retrieve all IP addresses in the 192.168.XX range, it didn't work, but using 192.168.0.0/13 worked immediately.

That's normal then: https://mxtoolbox.com/subnetcalculator.aspx

for 192.168.0.1/13 192.168.0.1 is not valid

[sfonteneau]

in the enterprise version, but indeed, by retrieving the wapt-conf-policy package and adapting it for my needs, I was able to set the use_repo_rules variable to False everywhere.

Now I don't understand why my agents are finding 0 available packages on the remote repositories even though the rules are configured and the synchronization is also in place.

In the agent's repository tab, is the correct repository appearing?

[guigeek]

Yes, it's definitely the right repo!
And in the tasks, we can clearly see that it's searching the correct repo and finding a significant number of packages to examine... but it doesn't see any packages to update, even though there are some!