Multi-repository operation for remote sites
Published: April 6, 2018 - 9:28 AM
Hello,
I updated my server to version 1.5.1.21 along with my three remote site repositories. Synchronization via Rsync works.
Everything seems to be working correctly except for the remote repositories.
The agent was deployed to all machines via a login script.
I then manually modified some remote site machines to use the local site repository configuration instead of the main site repository, based on the
wapt-get.ini file: adapting it to the local context:
[global]
repo_url=https://site1.mydomain.lan/wapt
waptserver=https://mainrepo.mydomain.lan
[wapt-host]
repo_url=https://mainrepo.mydomain.lan/wapt-host
When I assign a package to a remote machine via the console, it considers its configuration to be up-to-date. The same happens when I force a manual synchronization of the repositories, and also when I restart the remote machine.
What step do you think I missed?
Thank you in advance for your ideas...
Best regards,
I updated my server to version 1.5.1.21 along with my three remote site repositories. Synchronization via Rsync works.
Everything seems to be working correctly except for the remote repositories.
The agent was deployed to all machines via a login script.
I then manually modified some remote site machines to use the local site repository configuration instead of the main site repository, based on the
wapt-get.ini file: adapting it to the local context:
[global]
repo_url=https://site1.mydomain.lan/wapt
waptserver=https://mainrepo.mydomain.lan
[wapt-host]
repo_url=https://mainrepo.mydomain.lan/wapt-host
When I assign a package to a remote machine via the console, it considers its configuration to be up-to-date. The same happens when I force a manual synchronization of the repositories, and also when I restart the remote machine.
What step do you think I missed?
Thank you in advance for your ideas...
Best regards,