Project

Profile

Help

Issue #9286

Issue #9291: [Epic] pulp_installer upcoming issues

Check failed during installation when using vault encrypted variable

Added by beenje about 2 months ago. Updated about 2 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
CentOS 7
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

I tried installing pulp using the Pulp 3 Ansible Installer playbook:

---
collections:
  - name: pulp.pulp_installer
    version: 3.14.4

I encrypted the pulp_default_admin_password and secret_key in my inventory (using ansible-vault encrypt_string -n pulp_default_admin_password xxxxxx). When running the playbook, 2 tasks failed:

ASK [pulp.pulp_installer.pulp_common : Check if required variables are set] ************************************************************************************
ok: [w-v-pulp-0] => (item=pulp_settings.content_origin) => {
    "__pulp_common_req_var": "pulp_settings.content_origin",
    "ansible_loop_var": "__pulp_common_req_var",
    "changed": false,
    "msg": "All assertions passed"
}
fatal: [w-v-pulp-0]: FAILED! => {"msg": "The conditional check 'pulp_settings.secret_key | default('', true) | length > 0' failed. The error was: Unexpected templating type error occurred on ({% if pulp_settings.secret_key | default('', true) | length > 0 %} True {% else %} False {% endif %}): object of type 'AnsibleVaultEncryptedUnicode' has no len()"}

TASK [pulp.pulp_installer.pulp_database_config : Check if required variables are set] ***************************************************************************
fatal: [w-v-pulp-0]: FAILED! => {"msg": "The conditional check 'pulp_default_admin_password | default('', true) | length > 0' failed. The error was: Unexpected templating type error occurred on ({% if pulp_default_admin_password | default('', true) | length > 0 %} True {% else %} False {% endif %}): object of type 'AnsibleVaultEncryptedUnicode' has no len()"}

I had to use plain strings to run the playbook. It should be possible to use encrypted strings.

History

#1 Updated by mdepaulo@redhat.com about 2 months ago

  • Parent task set to #9291
  • Triaged changed from No to Yes

Please register to edit this issue

Also available in: Atom PDF