Comment 1 for bug 2062941

I understand that spaces in profile names are unusual and can cause problems, but they are allowed - and as you can see, they get used "in the wild".

This also means that software that reads /sys/kernel/security/apparmor/profiles or /proc/*/attr/apparmor/current should be able to handle such unusual profile names.

I know that it's probably not what you want to hear, but the best solution would be a bugreport for cephadm so that it gets a more robust parsing.