executando o apt-get update em um host que está apontando para o meu espelho local retorna os seguintes avisos e erros ...
W: The repository 'https://apt.devita.co/puppet xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://apt.devita.co/ubuntu xenial-backports Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://apt.devita.co/ubuntu xenial-security Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://apt.devita.co/ubuntu xenial-updates Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://apt.devita.co/ubuntu xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://apt.devita.co/puppet/dists/xenial/PC1/binary-amd64/Packages
E: Failed to fetch https://apt.devita.co/ubuntu/dists/xenial-backports/main/binary-amd64/Packages
E: Failed to fetch https://apt.devita.co/ubuntu/dists/xenial-security/main/binary-amd64/Packages
E: Failed to fetch https://apt.devita.co/ubuntu/dists/xenial-updates/main/binary-amd64/Packages
E: Failed to fetch https://apt.devita.co/ubuntu/dists/xenial/main/binary-amd64/Packages
E: Some index files failed to download. They have been ignored, or old ones used instead.
você pode ver capturas de tela do repositório local aqui e o repo está publicamente disponível temporariamente enquanto eu resolvo o problema.
my sources.list.d se parece com isso
# This file is managed by Puppet. DO NOT EDIT.
# puppetlabs-pc1
deb https://apt.devita.co/puppet xenial PC1 main
# This file is managed by Puppet. DO NOT EDIT.
# xenial-backports
deb https://apt.devita.co/ubuntu/ xenial-backports main restricted universe multiverse
# This file is managed by Puppet. DO NOT EDIT.
# xenial
deb https://apt.devita.co/ubuntu/ xenial main restricted universe multiverse
# This file is managed by Puppet. DO NOT EDIT.
# xenial-security
deb https://apt.devita.co/ubuntu/ xenial-security main restricted universe multiverse
# This file is managed by Puppet. DO NOT EDIT.
# xenial-updates
deb https://apt.devita.co/ubuntu/ xenial-updates main restricted universe multiverse
e o /var/www dir é links simbólicos para os locais do espelho apt como
Estamos discutindo isso no IRC em #ubuntu-server . Até agora parece que uma CA adicionada a /etc/ssl/certs quebrou os certificados update-ca, por isso /etc/ssl/certs/ca-certificates.crt estava quebrado ou apenas vazio, então apt-transport-https não estava funcionando.
Depurado usando: apt-get -o Debug::Acquire::https=1 update