After some small talk with Max, he convinced me that we should not use any generic link to repository - instead we should use one specific snapshot for mos-repos sources.
Why it's better? For example:
1. apt-get update is run on one node
2. in the meantime /mos-repos/ is updated (every 15 minutes)
3. apt-get install will fail because some packages does not exists anymore
Obviously there are also other scenerios which may fail.
The same thing goes for /pkgs/ mirror (update every day). The failure possibility is much, much smaller but it still exists.
/pkgs/ mirror also have snapshot file (was suggested by build-team) http://mirror.seed-cz1.fuel-infra.org/pkgs/ubuntu-latest.htm which is formated in a bit different way but the functionality stays the same. It would be much more reliable to also use it instead of generic path.
I believe these two things may improve stability of these failing jobs.
After some small talk with Max, he convinced me that we should not use any generic link to repository - instead we should use one specific snapshot for mos-repos sources.
Why it's better? For example:
1. apt-get update is run on one node
2. in the meantime /mos-repos/ is updated (every 15 minutes)
3. apt-get install will fail because some packages does not exists anymore
Obviously there are also other scenerios which may fail.
So file http:// mirror. fuel-infra. org/mos- repos/ubuntu/ 8.0.target. txt (version 8.0 example) should be read first and jobs should use only this snapshot.
The same thing goes for /pkgs/ mirror (update every day). The failure possibility is much, much smaller but it still exists.
/pkgs/ mirror also have snapshot file (was suggested by build-team) http:// mirror. seed-cz1. fuel-infra. org/pkgs/ ubuntu- latest. htm which is formated in a bit different way but the functionality stays the same. It would be much more reliable to also use it instead of generic path.
I believe these two things may improve stability of these failing jobs.