root@compute01:~# file /etc/kolla/nova-libvirt/secrets/9d4dacc6-9c75-49cb-bda2-c2e5e14f8e95.base64
/etc/kolla/nova-libvirt/secrets/9d4dacc6-9c75-49cb-bda2-c2e5e14f8e95.base64: ASCII text, with CR line terminators
On the production cluster this command shows only `ASCII text`, without any kind of line terminators.
I removed the line endings in earlier trials, which resulted in a working `base64 -d`, but libvirtd still complained about the invalid bas64.
For now I'm just leaving it as it is.
When I open the file with vi and copy the string inside (without the line ending) I can successfully decode it again.
Yesterday I ran `kolla-ansible destroy`, `git pull` on kolla-ansible, `kolla-ansible pull` and deployed the whole cluster again to restart fresh.
Currently running `base64 -d` inside the container fails:
(nova-libvirt) [root@compute01 /]# base64 -d /etc/libvirt/ secrets/ 9d4dacc6- 9c75-49cb- bda2-c2e5e14f8e 95.base64
vq=^ ~4
чbase64: invalid input
Checking the file contents of that file I get:
root@compute01:~# file /etc/kolla/ nova-libvirt/ secrets/ 9d4dacc6- 9c75-49cb- bda2-c2e5e14f8e 95.base64 nova-libvirt/ secrets/ 9d4dacc6- 9c75-49cb- bda2-c2e5e14f8e 95.base64: ASCII text, with CR line terminators
/etc/kolla/
On the production cluster this command shows only `ASCII text`, without any kind of line terminators.
I removed the line endings in earlier trials, which resulted in a working `base64 -d`, but libvirtd still complained about the invalid bas64.
For now I'm just leaving it as it is.
When I open the file with vi and copy the string inside (without the line ending) I can successfully decode it again.
root@compute01:~# vi /etc/kolla/ nova-libvirt/ secrets/ 9d4dacc6- 9c75-49cb- bda2-c2e5e14f8e 95.base64 AAfqCQkjSdB5ocs ICE4tGH2g= =" |base64 -d
root@compute01:~# echo "AQB2cT1eAAAAAB
vq=^ ~4
чroot@compute01:~#
So, maybe the line endings are a problem?