[bug] osism update manager is not successful (7.0.4 - 8.0.2)

[Nils98Ar]

OSISM release version

7.0.4

What's the problem?

Not sure if the WARNINGS / ERRORs are related to each other:

[...]

[WARNING]: Collection osism.manager does not support Ansible version 2.14.9
[WARNING]: running playbook inside collection osism.manager
[WARNING]: Collection osism.services does not support Ansible version 2.14.9

PLAY [Apply role manager] 

[...]

TASK [osism.services.manager : Include service tasks] ************************************************************************************************************************************************************************************************************************************************************************************************************
ERROR! couldn't resolve module/action 'community.docker.docker_compose_v2_pull'. This often indicates a misspelling, missing collection, or incorrect module path.

The error appears to be in '/home/dragon/.ansible/collections/ansible_collections/osism/services/roles/manager/tasks/service.yml': line 41, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

- name: Pull container images
  ^ here
2024-11-06 08:54:25 | INFO     | Task 1aebdc49-75e1-431c-bd61-1ad7f8705466 is running in background. Output coming soon.
2024-11-06 07:54:28 | INFO     | Writing 050-kolla-ceph-rgw-hosts.yml with ceph_rgw_hosts
2024-11-06 07:54:28 | INFO     | Writing 050-infrastructure-cephclient-mons.yml with cephclient_mons
2024-11-06 07:54:28 | INFO     | Writing 050-ceph-cluster-fsid.yml with ceph_cluster_fsid
ERROR! Unable to write to destination file (/inventory.merge/hosts.yml): [Errno 13] Permission denied: b'/inventory.merge/hosts.yml'

References to existing reports

References to existing bug reports, mailing lists, ...

Severity

low

Urgency

low

[berendt]

Remove the .venv directory in /opt/configuration/environments/manager & /home/dragon/.ansible to re-install Ansible + all Ansible collections.

[WARNING]: Collection osism.manager does not support Ansible version 2.14.9
[WARNING]: running playbook inside collection osism.manager
[WARNING]: Collection osism.services does not support Ansible version 2.14.9

[Nils98Ar]

We only deleted the ~/.env dir. After deleting the two other directorys it looks better. Should the deletion be included in the /usr/local/bin/osism-update-manager script? Otherwise the old versions will probably remain forever?

We now see these permission errors at the end of osism update manager:

rsync: [generator] delete_file: unlink(clustershell/ansible.yaml) failed: Permission denied (13)
rsync: [generator] delete_file: unlink(ansible/ansible.cfg) failed: Permission denied (13)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.3.0]

[berendt]

We only deleted the ~/.env dir. Should the deletion be included in the /usr/local/bin/osism-update-manager script? Otherwise the old versions will probably remain forever?

This makes no sense, you do not want to always re-install the Ansible & Ansible collection. But I can add a parameter to make this doable with the osism-update-manager script.

We now see these permission errors at the end of osism update manager:

rsync: [generator] delete_file: unlink(clustershell/ansible.yaml) failed: Permission denied (13)
rsync: [generator] delete_file: unlink(ansible/ansible.cfg) failed: Permission denied (13)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.3.0]

This is not related. You normally have this problem when you did some manual changes inside the inventory reconciler container in the past. I think the only way to resolve this issue is to stop the manager service, to remove the manager_inventory_reconciler volume and the manager-inventory_reconciler-1 container and to start the manager service again.

[Nils98Ar]

We only deleted the ~/.env dir. Should the deletion be included in the /usr/local/bin/osism-update-manager script? Otherwise the old versions will probably remain forever?

This makes no sense, you do not want to always re-install the Ansible & Ansible collection. But I can add a parameter to make this doable with the osism-update-manager script.

Or maybe a hint in the manager upgrade guide?

[berendt]

We only deleted the ~/.env dir. Should the deletion be included in the /usr/local/bin/osism-update-manager script? Otherwise the old versions will probably remain forever?

This makes no sense, you do not want to always re-install the Ansible & Ansible collection. But I can add a parameter to make this doable with the osism-update-manager script.

Or maybe a note in the manager upgrade guide?

Feel free to add a note @ https://osism.tech/docs/guides/upgrade-guide/manager. I think it makes sense to reinstall Ansible & Ansible collections when you do an major upgrade (7 -> 8).

[Nils98Ar]

Does deleting ~/.env makes sense in this context?

[berendt]

Does deleting ~/.env makes sense in this context?

I do not have this directory on my manager node in my testbed neither on our production manager.

[Nils98Ar]

Maybe it was an old leftover...