For some reason this isn't failing for me. I wonder if it comes down to a difference in clients used? Note the Ubuntu Rocky clients won't work with the --file CLI argument due to: https://bugs.launchpad.net/bugs/1799776
So I've used pip-installed clients from pypi. The following paste is against a py3 Rocky deployment. Note the debug logging added to barbican and the path taken in barbican (no encoding of data because id_rsa.pub is already base64 encoded): https://paste.ubuntu.com/p/pvmPCPrrHz/
I have a bionic-rocky barbican version building in the following PPA with the same debug that I used above. Could you run with that and report the barbican-api.log details with CCB prefixes? It may also be worth ensuring the id_rsa.pub is not corrupt, though still that should be a bug, but maybe it's partially b64encoded or something?
For some reason this isn't failing for me. I wonder if it comes down to a difference in clients used? Note the Ubuntu Rocky clients won't work with the --file CLI argument due to: https:/ /bugs.launchpad .net/bugs/ 1799776
So I've used pip-installed clients from pypi. The following paste is against a py3 Rocky deployment. Note the debug logging added to barbican and the path taken in barbican (no encoding of data because id_rsa.pub is already base64 encoded): https:/ /paste. ubuntu. com/p/pvmPCPrrH z/
I have a bionic-rocky barbican version building in the following PPA with the same debug that I used above. Could you run with that and report the barbican-api.log details with CCB prefixes? It may also be worth ensuring the id_rsa.pub is not corrupt, though still that should be a bug, but maybe it's partially b64encoded or something?