After taking two ramdisks one working and another not, stripping out everything I think is irrelevant (inode numbers, timestamps etc..), the only difference I'm left with that I think is relevant is that the "/" directory has the permissions 700 in the non working ramdisk and 775 working ramdisk.
If this turns out to be the problem, I suspect that the umask has changed recently with a newer version of something (centos or ansible maybe).
I've confirmed this locally but CI appears to be having other problems at the moment
After taking two ramdisks one working and another not, stripping out everything I think is irrelevant (inode numbers, timestamps etc..), the only difference I'm left with that I think is relevant is that the "/" directory has the permissions 700 in the non working ramdisk and 775 working ramdisk.
If this turns out to be the problem, I suspect that the umask has changed recently with a newer version of something (centos or ansible maybe).
I've confirmed this locally but CI appears to be having other problems at the moment