Description of problem: ----------------------- Used the existing NBDE playbook to setup NBDE. The execution of the playbook failed to bind to tang server. Version-Release number of selected component (if applicable): --------------------------------------------------------------- clevis-luks-13-3.el8.x86_64 clevis-dracut-13-3.el8.x86_64 clevis-13-3.el8.x86_64 clevis-systemd-13-3.el8.x86_64 gluster-ansible-infra-1.0.4-15.el8rhgs.noarch How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Edit the NBDE playbook (/etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/luks_tang_inventory.yml) as per the requirement 2. Run the playbook Actual results: --------------- Fails to bind to tang server Expected results: ----------------- Success in binding to tang server Additional info: ----------------- [root@rhsqa-grafton10-nic2 hc-ansible-deployment]# cat -A /etc/root_key "redhat123\n"$ --- Additional comment from SATHEESARAN on 2020-11-09 12:16:54 UTC --- This bug is a blocker as the NBDE feature is broken
1. Fix is required in gluster-ansible-infra package 2. File that should edited is - /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/bind_tang_server.yml 3. Block to be edited in this file <snip> - name: Create key root file no_log: true copy: dest: "/etc/root_key" content: | {{ rootpassphrase }} when: gluster_infra_tangservers is defined <snip> Fix: <snip> - name: Create key root file no_log: true copy: dest: "/etc/root_key" content: "{{ rootpassphrase }}" when: gluster_infra_tangservers is defined </snip> This makes sure that /etc/root_key doesn't include newline. I have tested with the same and it works
Upstream PR: https://github.com/gluster/gluster-ansible-infra/pull/112
Tested with gluster-ansible-infra-1.0.4-16.el8rhgs NBDE deployment is successful
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (gluster-ansible bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:5220