Page MenuHomePhabricator

apt-get update fails in fresh deployment-prep VM
Closed, ResolvedPublic

Description

  1. Create a VM in deployment-prep using the debian-11.0-bullseye or debian-12.0-bookworm image.
  2. Wait for puppet to finish (about 2 minutes).
  3. ssh into the VM
  4. Run sudo apt-get update. See:
$ sudo apt-get update
...usual stuff...
E: Failed to fetch http://deployment-deploy04.deployment-prep.eqiad1.wikimedia.cloud/repo/dists/bullseye-deployment-prep/main/binary-amd64/Packages  404  Not Found [IP: 172.16.1.63 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
$ echo $?
100

Event Timeline

I fired deployment-deploy03 back up to see how it was set up. Looks like it has a /srv/deployment/repo symlink pointing to /srv/packages/public/. This link does not exist on deployment-deploy04. That needs to be puppetized but I'm not sure where to do that yet.

On deployment-deploy03, /srv/packages/public holds old scap debs, something we do not use anymore.

Mentioned in SAL (#wikimedia-releng) [2024-08-21T19:32:25Z] <dancy> Removed role::aptly::client from deployment-prep project Puppet (T373051)

In case it's helpful. Previously, there was a CI job in jenkins that built the deb for scap and deployed. See beta-publish-deb.

Since deployment-deploy04 is no longer a source for deb packages in deployment-prep, I removed the role::aptly::client class from deployment-prep project puppet. Existing VMS that still have references to deployment-deploy04 in their apt config can be cleaned up by removing the following files:

/etc/apt/preferences.d/project_aptly.pref
/etc/apt/sources.list.d/project-aptly.list
/etc/apt/apt.conf.d/52unattended-upgrades-aptly
dancy triaged this task as Medium priority.