pulp installer is failing on database config for some hosts

[suhastm19]

The latest release has a database config task where it will check for existence of __pulp_db_fields_key_path on all hosts but vcenter which is one of the host need not be checked for and its default appliance shell is not compatible with ansible and the playbook is failing for vcenter

IS there a way to avoid this.

[suhastm19]

The latest release has a database config task where it will check for existence of __pulp_db_fields_key_path on all hosts but vcenter which is one of the host need not be checked for and its default appliance shell is not compatible with ansible and the playbook is failing for vcenter

IS there a way to avoid this.

Any thing from my side that i could do to avoid this ??

[DaveDrupsteen]

I had the exact same issue, the workaround i used was a new inventory file with only 1 pulp host.
It was the only way I could continue the playbook.

[suhastm19]

@DaveDrupsteen i cannot do that though, so for now i used previous ansible pulp_installer (3.18.3) to install and configure pulp.

[Raptus1]

Also having issues with this as it goes through all hosts in my dynamic inventory, some hosts with a different cred/vault set causing the playbook to fail..

Not aware of any simple way to build a one-host inventory for this running this playbook only.

[mikedep333]

So the cause of the problem is that the role pulp_database_config checks the existence of pulp on all other hosts, not just the hosts that the role is run against. And it cannot check these other hosts.

I think the best thing to do is for me to just ignore_errors: true or failed_when: false on the task.

Are either acceptable to you all?

EDIT: I decided to not check for the existence of pulp (more specifically, the database fields encryption key) on all other hosts. This is reflected in the PR.

[Raptus1]

I like the changes you proposed as alternative for groups all.

[mikedep333]

@suhastm19 @DaveDrupsteen @Raptus1 I am releasing 3.19.4 with the fix right now. It should be on Ansible Galaxy within the hour.