Comment 4 for bug 1493390

Confirmed issue with repositories.

Reproduced in system tests *after* a deploy was successfully finished.

When 'apt-get update' was executed on one of the nodes, webserver where repository is located suddenly returned HTTP error 404.

Time when it was happened: 12:30 UTC.

Looks like some hidden actions are performed on the mirrors with repositories, and this lead to unavailability or inconsistency of repositories from time to time.

================================
DevopsCalledProcessError: Command 'apt-get clean all && apt-get update > /dev/null' returned non-zero exit status 100
W: GPG error: http://mirror.fuel-infra.org mos7.0-holdback Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY CA2B20483E301371

W: GPG error: http://mirror.fuel-infra.org mos7.0-security Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY CA2B20483E301371

W: GPG error: http://mirror.fuel-infra.org mos7.0-updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY CA2B20483E301371

W: Failed to fetch http://mirror.fuel-infra.org/mos-repos/ubuntu/7.0/dists/mos7.0-updates/main/binary-amd64/Packages 404 Not Found [IP: 208.78.244.194 80]

W: Failed to fetch http://mirror.fuel-infra.org/mos-repos/ubuntu/7.0/dists/mos7.0-updates/restricted/binary-amd64/Packages 404 Not Found [IP: 208.78.244.194 80]

E: Some index files failed to download. They have been ignored, or old ones used instead.
==========================