Tranquil IT Forum

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.

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.

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

guigeek wrote: ↑March 3, 2023 - 9:16 AM 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

Hello,

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

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.

guigeek wrote: ↑March 3, 2023 - 2:44 PM 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.

jdziadek wrote: ↑March 6, 2023 - 12:48

guigeek wrote: ↑March 3, 2023 - 2:44 PM 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

guigeek wrote: ↑March 3, 2023 - 2:44 PM 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?

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!