eatmydata package can't be located

Bug #2048751 reported by Nicolas Formichella
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
New
Undecided
Unassigned

Bug Description

Running `openstack-ansible setup-hosts.yml` (git rev c3142a91a397d039b44fc02fbae3d364075cdc47) on (both dev and target are) Ubuntu 22.04 Jammy fails at `Ensure that the LXC cache has been prepared`

```
fatal: [infra1]: FAILED! => {"ansible_job_id": "j42483756826.77090", "attempts": 1, "changed": true, "cmd": "chroot /var/lib/machines/ubuntu-22-amd64 /opt/cache-prep-commands.sh > /var/log/lxc-cache-prep-commands.log 2>&1", "delta": "0:00:00.048102", "end": "2024-01-09 08:11:19.575951", "finished": 1, "msg": "non-zero return code", "rc": 100, "results_file": "/root/.ansible_async/j42483756826.77090", "start": "2024-01-09 08:11:19.527849", "started": 1, "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}
```

LXC sources.list (same as node) : https://paste.ubuntu.com/p/gnMD6mdRrF/

Package is definitely available on the infra1 node, and nothing indicates it failed the `apt update` stage :

```
$ apt-cache policy eatmydata

eatmydata:
  Installed: 130-2build1
  Candidate: 130-2build1
  Version table:
 *** 130-2build1 500
        500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status
```

Revision history for this message
Nicolas Formichella (signed) wrote :
Revision history for this message
Dmitriy Rabotyagov (noonedeadpunk) wrote :

Hi, Nicolas

This actually looks to me like a consequence of previously reported bug: https://bugs.launchpad.net/openstack-ansible/+bug/2048659

Since file:/cdrom seems still to be present in repos of container as it's present in attached logfile.

Once you remove cdrom source from the infra node, you might need to rebuild the LXC image by re-running

openstack-ansible playbooks/lxc-hosts-setup.yml -e lxc_image_cache_refresh=true

Revision history for this message
Dmitriy Rabotyagov (noonedeadpunk) wrote :

Unless you've assigned wrong file to this bug report, ofc :)

FWIW, you can join us on IRC in #openstack-ansible channel on OFTC network for raising questions regarding deployment process.

Revision history for this message
Nicolas Formichella (signed) wrote :

Sorry, that's the wrong log I joined

This is the right one

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.