[bug] Unable to use ceph-connectivity validation, Manager not up2date after upgrade

scoopex commented 2 days ago

OSISM release version

8.0.0

What's the problem?

I tried to use validate-ceph-connectivity.yml) to check the correctness of my network configuration using the osism validate ceph-connectivity command.

That does not work, because this validation not seems to be in the list known validations:

$ osism validate ceph-connectivity
usage: osism validate [-h] [--format [{script,log}]] [--environment ENVIRONMENT] [--timeout TIMEOUT] [--no-wait]
                      {barbican-config,blazar-config,designate-config,keystone-config,glance-config,heat-config,octavia-config,nova-config,neutron-config,placement-config,aodh-config,ceilometer-config,cloudkitty-config,ironic-config,manila-config,senlin-config,ceph-config,ceph-mgrs,ceph-mons,ceph-osds,container-status,kernel-version,mysql-open-files-limit,refstack,system-encoding,ulimits,mariadb-backup,mariadb-recovery}
                      ...
osism validate: error: argument validator: invalid choice: 'ceph-connectivity' (choose from 'barbican-config', 'blazar-config', 'designate-config', 'keystone-config', 'glance-config', 'heat-config', 'octavia-config', 'nova-config', 'neutron-config', 'placement-config', 'aodh-config', 'ceilometer-config', 'cloudkitty-config', 'ironic-config', 'manila-config', 'senlin-config', 'ceph-config', 'ceph-mgrs', 'ceph-mons', 'ceph-osds', 'container-status', 'kernel-version', 'mysql-open-files-limit', 'refstack', 'system-encoding', 'ulimits', 'mariadb-backup', 'mariadb-recovery')

I am using the the following branch for the 8.0.0 upgrade: https://github.com/SovereignCloudStack/hardware-landscape/tree/openstack_install_8.0.0

References to existing reports

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

Severity

low

Urgency

low

scoopex commented 2 days ago

Of course, I upgraded the manager, but received the following error messages:

$ osism update manager
....
Starting collection install process
Installing 'osism.manager:999.0.0' to '/home/dragon/.ansible/collections/ansible_collections/osism/manager'
Created collection for osism.manager:999.0.0 at /home/dragon/.ansible/collections/ansible_collections/osism/manager
osism.manager:999.0.0 was installed successfully
[WARNING]:  * Failed to parse /opt/configuration/inventory/10-custom with yaml plugin: Attempting to decrypt but no vault secrets found
[WARNING]:  * Failed to parse /opt/configuration/inventory/10-custom with ini plugin: Attempting to decrypt but no vault secrets found
[WARNING]: Unable to parse /opt/configuration/inventory/10-custom as an inventory source
[WARNING]:  * Failed to parse /opt/configuration/inventory/20-roles with yaml plugin: Attempting to decrypt but no vault secrets found
[WARNING]:  * Failed to parse /opt/configuration/inventory/20-roles with ini plugin: Attempting to decrypt but no vault secrets found
[WARNING]: Unable to parse /opt/configuration/inventory/20-roles as an inventory source
[WARNING]:  * Failed to parse /opt/configuration/inventory/99-overwrite with yaml plugin: Attempting to decrypt but no vault secrets found
[WARNING]:  * Failed to parse /opt/configuration/inventory/99-overwrite with ini plugin: Attempting to decrypt but no vault secrets found
[WARNING]: Unable to parse /opt/configuration/inventory/99-overwrite as an inventory source
[WARNING]: Unable to parse /opt/configuration/inventory as an inventory source
[WARNING]: No inventory was parsed, only implicit localhost is available
ERROR! Attempting to decrypt but no vault secrets found
2024-09-16 08:06:39 | INFO     | Task 6e2b4c84-6fe8-49aa-bb0f-2054f8953a27 is running in background. Output coming soon.
2024-09-16 08:06:55 | INFO     | Writing 050-kolla-ceph-rgw-hosts.yml with ceph_rgw_hosts

When i enter the osism-ansible container then I notice the following points:

A Container version is displayed which is different from the installed release

$ docker exec -ti osism-ansible /bin/bash
.
...
Ansible version: 2.16.6
Container version: 7.0.5

The referenced yml file is not deployed:

$ docker exec -ti osism-ansible find /playbooks -path "*/ceph/*.yml"
/playbooks/playbooks/ceph/validate-ceph-rgws.yml
/playbooks/playbooks/ceph/validate-ceph-osds.yml
/playbooks/playbooks/ceph/validate-ceph-mgrs.yml
/playbooks/playbooks/ceph/validate-ceph-mons.yml

Version v0.20240904.0 is linked in the Manager's “run.sh”. According to the tag, it should actually be at the available. (https://github.com/osism/ansible-playbooks/blob/v0.20240904.0/playbooks/ceph/validate-ceph-connectivity.yml)

artificial-intelligence commented 2 days ago

in the correct container the playbook is included:

 ~  docker run -it quay.io/osism/osism-ansible:8.0.0 bash                                                                                                                                                     1 ✘  took 22s  at 10:47:22 

 _____  ___  ____  ___  __  __
(  _  )/ __)(_  _)/ __)(  \/  )
 )(_)( \__ \ _)(_ \__ \ )    (
(_____)(___/(____)(___/(_/\/\_)

Ansible version: 2.17.4
Container version: 8.0.0

dragon@021c6e04ce96:~$ find /playbooks -path "*/ceph/*.yml"
/playbooks/playbooks/ceph/validate-ceph-connectivity.yml
/playbooks/playbooks/ceph/validate-ceph-mgrs.yml
/playbooks/playbooks/ceph/validate-ceph-mons.yml
/playbooks/playbooks/ceph/validate-ceph-osds.yml
/playbooks/playbooks/ceph/validate-ceph-rgws.yml

The question now is: Why do you have the 7.0.5 Container there? Did you somehow pin it/Did a debug Test with this older release?

I can look into the manager update code, but I highly doubt that there is a bug, can you please check your environment?

What happens if you try to manually pull the 8.0.0 container?

maliblatt commented 2 days ago

ERROR! Attempting to decrypt but no vault secrets found

I think you should provide the vault password!? we do it like this: osism update manager --ask-vault-pass

scoopex commented 2 days ago

Releated to https://github.com/osism/issues/issues/1131

scoopex commented 2 days ago

ERROR! Attempting to decrypt but no vault secrets found

I think you should provide the vault password!? we do it like this: osism update manager --ask-vault-pass

Yes, but the documentation describes: If Ansible Vault was used to encrypt environments/manager/secrets.yml, the parameter --ask-vault-pass is also appended. From OSISM >= 7.0.5 this is no longer necessary.

scoopex commented 1 day ago

Problem solved. Fix already in place.

osism / issues